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

Michael Buesch
2007-05-26T15:37:17Z

On Saturday 26 May 2007 12:40:54 Uwe Bugla wrote:
> Yes! This sort of mistakes is completely impossible, as I use to work with
> aliases rather than IP adresses. The machine I tried to ping (i. e. my
> router) is called Jerry (as a reminiscence to Mr. "Captan Trips" from
> Grateful Dead), and thus "ping jerry" returned the following:
>
> "destination host unreachable"
>
> Above that, I state for the second time now that I reverted your patches in
> 2.6.22-rc2-mm1 with the effect that everything worked perfectly!
> Maxi said something at least similar. So how many proofs do you need, Mister
> Buesch, to finally pick up patchworking now??

How about you stopping with your fucking aggressive wording??

> > Try it again, please.
>
> NO!
>
> > And please try with current wireless-dev tree.
>
> A. I do not know where to download that wireless-dev tree.
> B. I do not know how to implement it into mm or mainline
> C. I have given enough sophisticated proof that your stuff in mm-tree is
> highly incomplete / buggy.

Ok,

D. As you are not going to help me debugging, I am not going to fix.

> >
> > And I simply do not get it why you suddenly get a good IRQ number, like
> > everybody else does, without fixing The Bug (tm).
>
> That consequence I already explained:
> But it's a pleasure for me to repeat it once more:
>
> When you are saying Y to "EISA, VLB, PCI and on board controllers"
>
> you simply do get not only completely different interrupts for the b4401
> device, but you get also completely different module dependencies.

That is EXPECTED and I already explained that.
It is a feature. Not a bug.

--
Greetings Michael.