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 returns failure then the other will get a chance. > > > [ 10.013632] b43-phy0: Broadcom 4312 WLAN found (core revision 15) > > [ 10.344469] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5, Revision 1) > > [ 10.344829] b43: probe of ssb0:0 failed with error -95 > > [ 10.344888] Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] > > 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 versions. > > It may be that you need to run "depmod -a" to complete installation of > > broadcom-sta. > > Can't test right now, but I re-ran update-initramfs after the installation, > so I guess broadcom-sta is included in the device ID list. No, update-initramfs has nothing to do with depmod. > Anyway, I wonder if it makes sense to declare support for that PCI ID if it > isn't actually present -- the probe function will always fail until support > for LP-PHY is implemented. I wouldn't expect the different PHYs to be distinguishable by PCI id. Ben. -- Ben Hutchings When you say `I wrote a program that crashed Windows', people just stare ... and say `Hey, I got those with the system, *for free*'. - Linus Torvalds
Attachment:
signature.asc
Description: Digital signature