Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)

[Michael Buesch <mb@bu3sch.de>]

On Saturday 26 May 2007 20:58:37 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 20:41 schrieben Sie:
> > On 5/26/07, Michael Buesch <mb@bu3sch.de> wrote:
> > > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > > clear enough in the sense of being distinctive enough, just clear and
> > > > comprehensive.
> > >
> > > Why don't you simply submit a patch to change the helptext then?
> >
> > Is that ok ?
> >
> > Discourage people from deselecting B44_PCI
> >
> > Signed-off-by: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
> >
> > --- kernel.orig/drivers/net/Kconfig	2007-05-26 20:38:02.000000000 +0200
> > +++ kernel/drivers/net/Kconfig	2007-05-26 20:38:15.000000000 +0200
> > @@ -1449,7 +1449,7 @@
> >  	help
> >  	  Support for b44 PCI devices.
> >
> > -	  Say Y
> > +	  Unless you know what you are doing, say Y here.
> >
> >  config FORCEDETH
> >  	tristate "nForce Ethernet support"
> 
> No, That is NOT OK! That's nothing but a joke, and if it is a joke : )
> it hits well in Mister Buesches direction. In so far it's 
> well-done : ) : ) : )

See what I meant, Benoit?

> To be honest:
> 
> I expect at least TWO explained cases:
> 
> A. The case in which the b44 module is a PCI module (onboard, additional PCI 
> card etc.).
> 
> B. At least one well described case in which the b44 module is a bus 
> independent one.

You still didn't get it, right?
b44-ssb is a SSB device driver. No PCI, nothing. To get this working
on PCI you need to enable the PCI glue. Which is enabled by default.
It even includes the comment "Say Y". If you say N nevertheless it's
your fault.
What's so hard to understand about this? We have LOTS of drivers in the
kernel that work _exactly_ the same way. There is a base module to drive
the hardware and several glue drivers. If you de-select the glue driver
it doesn't work.
If you use your old config and do not DISABLE some option you will
not experience a regression (at least regarding to the kconfig stuff.
There's still your transmission bug left).

> Apart from that, it is Michael's task to explain the what and why, not mine 
> and not yours! It is him that wants his stuff being pulled into mainline, and 

My task is _nothing_. This is opensource. If you don't like
something about it, go and fix it. But don't say it's the _task_ of others
to fix things you don't like. I am not payed to do this for you.
Though, I'd like to resolve it.

> in so far he very well can do the "dirty work" of documentation, explanation.

I explained it several times now. I'm not sure what else I should
say about it.

-- 
Greetings Michael.
-
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/