On Sun, Feb 24, 2008 at 5:29 PM, Michael Buesch <mb@bu3sch.de> wrote:
quoted text
> On Saturday 23 February 2008 12:32:50 Alexey Zaytsev wrote:
>  > The problem is not with enabling both b43 and bcm43xx (will, whis won't work
>  > anyway, and there is no chance fixing it). The problem is with enabling the
>  > bcm43xx wifi driver and the b44 Ethernet driver. The ethernet driver then
>  > wrongly autosolects some config options that prevent the bcm43xx
>  > driver from loading, so I'm left with either no wifi or no ethenet.
>
>  Ok, so I just tested this on a machine and it is _not_ true.
>  It works just fine to run b44/ssb with bcm43xx in parallel.
>
>  Can you please stop fooling me and spreading this FUD?
>

The ony way I see this was possible, you manually changed the
module loading order, so that the b43xx module was loaded prior
to the ssb and b44 modules. Right? Or the b43xx driver was built
statically and the b44 and the ssb as modules.

Looks like this, kind of, ruins my statement that is is impossible to get
working wifi in 2.6.24. Sorry, it was not intensinal. ;)

But there still are lots of valid combinations where the b43xx driver
silently won't work. E.g. when either the ssb or the b44 modules are
loaded prior to it, or when either of them are built statically (building
the b43xx driver staticaly won't help here). And my patch fixes them.

So, my statement goes, the bug stays. Agreed?
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/