Bug#535131: closed by maximilian attems (Re: Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device)

2010-02-14 Thread Simon Richter
Hi, On Sat, Feb 13, 2010 at 11:21:51PM +0100, Bastian Blank wrote: > The b43 driver does not claim devices it does not know. Not anymore. It did at the time of the original bug report. Simon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe

Bug#535131: closed by maximilian attems (Re: Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device)

2010-02-13 Thread Bastian Blank
On Sat, Feb 13, 2010 at 09:38:01PM +0100, Simon Richter wrote: > > also this seems just user error just blacklist said module > I disagree. It is not a "user error" if a kernel module is loaded for a > piece of hardware because it declares support for the hardware in its > device table, and subsequ

Bug#535131: closed by maximilian attems (Re: Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device)

2010-02-13 Thread Simon Richter
Hi, apparently the driver has gained actual support for LP-PHY based devices since, so not reopening bug. > also this seems just user error just blacklist said module I disagree. It is not a "user error" if a kernel module is loaded for a piece of hardware because it declares support for the har

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-07-01 Thread Simon Richter
Hi, On Wed, Jul 01, 2009 at 11:30:42AM +0200, Bastian Blank wrote: > And why is it a bug in the kernel if an external module fails to load? The bug is declaring support for an unsupported device. > Please show the following information: Will do when I'm back at that machine. > > Autoload work

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-07-01 Thread Bastian Blank
On Wed, Jul 01, 2009 at 10:44:18AM +0200, Simon Richter wrote: > On Wed, Jul 01, 2009 at 09:27:59AM +0100, Ben Hutchings wrote: > > modprobe will load them both, regardless of whether probe succeeds or > > fails. That is, if they have both been indexed by depmod. > I just tried, and no, the "wl" m

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-07-01 Thread Simon Richter
Hi, On Wed, Jul 01, 2009 at 09:27:59AM +0100, Ben Hutchings wrote: > modprobe will load them both, regardless of whether probe succeeds or > fails. That is, if they have both been indexed by depmod. I just tried, and no, the "wl" module is not autoloaded even after rerunning depmod -a explicitl

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-07-01 Thread Ben Hutchings
On Tue, 2009-06-30 at 21:15 +0200, Simon Richter wrote: > Hi, > > On Tue, Jun 30, 2009 at 07:03:18PM +0100, Ben Hutchings wrote: > > > > Sure that this is actually communicated to userspace? It appears that the > > > module is still loaded, with no devices bound. > > > In Linux 2.6 probe failure

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-30 Thread Bastian Blank
On Tue, Jun 30, 2009 at 09:15:11PM +0200, Simon Richter wrote: > > I wouldn't expect the different PHYs to be distinguishable by PCI id. > >From what I read on the web, they use different PCI IDs (that's why a 4312 > has an id of 0x4315). The whole bcm43xx chips are SSB, not PCI-devices. What you

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-30 Thread Simon Richter
Hi, On Tue, Jun 30, 2009 at 07:03:18PM +0100, Ben Hutchings wrote: > > Sure that this is actually communicated to userspace? It appears that the > > module is still loaded, with no devices bound. > In Linux 2.6 probe failure doesn't mean load failure. Forget everything > you know from earlier v

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-30 Thread Ben Hutchings
On Tue, 2009-06-30 at 14:37 +0200, Simon Richter wrote: > Hi, > > On Tue, Jun 30, 2009 at 01:09:10AM +0100, Ben Hutchings wrote: > > > That's not how module loading works. If there are two modules that > > handle the same device id they will both be loaded. If the first probe > > function retur

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-30 Thread Bastian Blank
On Tue, Jun 30, 2009 at 02:37:58PM +0200, Simon Richter wrote: > On Tue, Jun 30, 2009 at 01:09:10AM +0100, Ben Hutchings wrote: > > That's not how module loading works. If there are two modules that > > handle the same device id they will both be loaded. If the first probe > > function returns fa

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-30 Thread Simon Richter
Hi, On Tue, Jun 30, 2009 at 01:09:10AM +0100, Ben Hutchings wrote: > That's not how module loading works. If there are two modules that > handle the same device id they will both be loaded. If the first probe > function returns failure then the other will get a chance. > [ 10.013632] b43-phy

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-29 Thread Ben Hutchings
On Tue, 2009-06-30 at 01:19 +0200, Simon Richter wrote: > Package: linux-image-2.6.30-1-686 > Version: 2.6.30-1 > Severity: normal > > Hi, > > starting with 2.6.30, the b43 driver is autoloaded for the bcm4312 with > LP-PHY, identified by PCI Product ID 0x4315; the driver then complains that > th

Bug#535131: linux-image-2.6.30-1-686: b43 driver claims support for unsupported device

2009-06-29 Thread Simon Richter
Package: linux-image-2.6.30-1-686 Version: 2.6.30-1 Severity: normal Hi, starting with 2.6.30, the b43 driver is autoloaded for the bcm4312 with LP-PHY, identified by PCI Product ID 0x4315; the driver then complains that the device is unsupported. This shadows the declaration by the non-free bro