From: Michael Buesch <mb@bu3sch.de>
To: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Alexey Zaytsev" <zaytsev.a@protei.ru>,
"Greg KH" <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: bcm43xx regression in 2.6.24 (with patch)
Date: Sat, 23 Feb 2008 23:20:58 +0100 [thread overview]
Message-ID: <200802232320.58562.mb@bu3sch.de> (raw)
In-Reply-To: <f19298770802231332x79c0395fl5519e79ae75da0aa@mail.gmail.com>
On Saturday 23 February 2008 22:32:46 Alexey Zaytsev wrote:
> > The insults being? A few quotes, please.
> If you really want to know, the
> "Because the new driver works, if you just set it up right."
> for me was clearly a hint that I'm just an other imcompetent
> user, who can't even follow the instructions from linuxwireless.org.
Well. That's 99% of all bugreports I receive. You will understand
that I won't explain the same crap that's written on linuxwireless.org
over and over 20 times each day to random people.
And yes, you belong to the group of my "random people", as I don't
remember your name from the top of my head.
So in 99% of the cases the user did something wrong.
But I still don't see the insult.
> And you knew that the new driver did no work with the bcm4311
> chips, which is the sad thing.
That is not true. It doesn't work with exactly _one_ revision
of the bcm4311 card. And that is already fixed in 2.6.25.
I'd like to have that in .24-stable, too, but I guess it's too big.
It changes some parts of the DMA engine code.
> Not true at all. I my first and second emails, there was not a single word
> about who broke the driver. There were only the fix, and the explanation,
> why the fix is needed. I really appreciate the work done on the b43 driver,
> and I'd emmediately switch to it, if only it worked for me*.
Yeah. But I don't like that patch. Then people came and said stuff like
I _have_ to accept it because it fixes stuff I broke. Excuse me, but
nobody can force me to sign off a patch that I am not completely
convinced of. _Even_ if it turns out that a commit made by me
broke something. Especially, if there's already another fix for the
situation queued up in the development kernel.
> I'm the one person who investigated the problem, wrote a
> patch and sent it to the lkml. After lurking in #bcm-users
> for a day, I saw quite a few users asking why the b43 driver
> did not work for them, and the best answer they got, was
> got read the linuxwireless.org. Are you sure they all were
> just unable to upgrade the firmware?
Yeah. Experience shows that. Read the archives.
> And by the way, the bcm4311 and b44 combination is not
> something I assembled just to piss you off. It's what HP puts
> in their HP Compaq nx7300 laptops. They were like the
> cheapest Core Duo laptops a year ago, and I'm sure they were
> not exclusively made.
So be it. And you guess what? We already sent a fix for those
people upstream a long time ago. It is in 2.6.25.
> > So let's
> > apply a questionable fix for it that we don't understand. Hopefully
> > that fixes it and doesn't break it again for somebody else... .
> >
> > I provided an alternative fix. In my very first email.
>
> Sorry, your fix does not work for my hardware. And you know it.
Did you _ever_ even try it?
http://linuxwireless.org/en/users/Download
--
Greetings Michael.
next prev parent reply other threads:[~2008-02-23 22:21 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 11:17 bcm43xx regression in 2.6.24 (with patch) Alexey Zaytsev
2008-02-22 14:13 ` Michael Buesch
2008-02-22 17:51 ` Gabriel C
2008-02-22 17:56 ` Michael Buesch
2008-02-22 22:10 ` Greg KH
2008-02-22 18:10 ` Alexey Zaytsev
2008-02-22 17:48 ` Michael Buesch
2008-02-22 20:06 ` Alexey Zaytsev
2008-02-22 20:12 ` Michael Buesch
2008-02-22 20:38 ` Alexey Zaytsev
2008-02-22 22:12 ` Greg KH
2008-02-22 22:45 ` Alexey Zaytsev
2008-02-23 5:48 ` Michael Buesch
2008-02-23 11:07 ` Ingo Molnar
2008-02-23 11:18 ` Pekka Enberg
2008-02-23 11:24 ` Ingo Molnar
2008-02-23 11:32 ` Alexey Zaytsev
2008-02-23 11:37 ` Pekka Enberg
2008-02-23 11:51 ` Alexey Zaytsev
2008-02-23 11:57 ` Pekka J Enberg
2008-02-23 12:17 ` Alexey Zaytsev
2008-02-23 12:23 ` Pekka Enberg
2008-02-24 14:29 ` Michael Buesch
2008-02-24 16:39 ` Alexey Zaytsev
2008-02-24 17:16 ` Michael Buesch
2008-02-25 6:16 ` Pekka J Enberg
2008-02-25 6:49 ` Greg KH
2008-02-25 6:54 ` Pekka J Enberg
2008-02-25 9:54 ` Michael Buesch
2008-02-25 12:11 ` Pekka Enberg
2008-02-25 12:19 ` Michael Buesch
2008-02-25 12:25 ` Pekka J Enberg
2008-02-25 13:00 ` Alexey Zaytsev
2008-02-25 10:23 ` Alexey Zaytsev
2008-02-25 10:38 ` Michael Buesch
2008-02-25 10:49 ` Xavier Bestel
2008-02-25 10:54 ` Michael Buesch
2008-02-23 16:05 ` Michael Buesch
2008-02-23 16:27 ` Michael Buesch
2008-02-23 16:44 ` Ingo Molnar
2008-02-23 16:50 ` Michael Buesch
2008-02-23 21:32 ` Alexey Zaytsev
2008-02-23 22:20 ` Michael Buesch [this message]
2008-02-26 20:20 ` John W. Linville
2008-02-26 21:38 ` Alexey Zaytsev
2008-02-26 22:04 ` Michael Buesch
2008-02-26 22:12 ` Alexey Zaytsev
2008-02-26 22:41 ` Michael Buesch
2008-02-28 22:03 ` Michael Buesch
2008-02-28 22:48 ` Alexey Zaytsev
2008-02-28 23:12 ` Stefan Lippers-Hollmann
2008-02-29 23:22 ` Alexey Zaytsev
2008-02-28 23:14 ` Michael Buesch
2008-02-26 22:47 ` John W. Linville
2008-02-26 23:12 ` Michael Buesch
2008-02-27 0:23 ` Alexey Zaytsev
2008-02-27 0:27 ` Michael Buesch
2008-02-27 0:32 ` Alexey Zaytsev
2008-02-27 0:43 ` Michael Buesch
2008-02-27 0:53 ` Alexey Zaytsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802232320.58562.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=alexey.zaytsev@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zaytsev.a@protei.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.