From: Michael Buesch <mb@bu3sch.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"John W. Linville" <linville@tuxdriver.com>,
"David S. Miller" <davem@davemloft.net>,
wireless <linux-wireless@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Make b43 driver fall back gracefully to PIO mode after fatal DMA errors
Date: Sat, 27 Feb 2010 15:44:42 +0100 [thread overview]
Message-ID: <201002271544.43164.mb@bu3sch.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1002261239070.4513@localhost.localdomain>
On Friday 26 February 2010 21:42:29 Linus Torvalds wrote:
>
> On Fri, 26 Feb 2010, Linus Torvalds wrote:
> >
> > So send me a patch. I'll try it. But I have no hardware docs, nor any
> > information about how that SSB bridge is supposed to work, or why DMA
> > might be failing.
>
> Btw, I also object to your argument that
>
> "Well, my original plan was to get rid of controller_restart and not add
> yet another user of it, because it is extremely broken and racy. The
> locking in the whole driver is completely braindead due to the mere
> existence of this function."
>
> is a reason to not apply the patch.
Blah, I never said that. I just said what my original plan was and that
the workaround is not as sound as it looks like. In fact, it kind of depends
on luck that it works at all. The controller_restart _never_ worked correctly,
because it does not notify the stack about the restart. So your code implicitly
relies on getting a DMA error before the stack does any significant negotiation
with the AP. (Or that the stack detects the device fuckup and starts over again).
> The fact that the driver locking is odd is _not_ a reason to not fix other
> issues that are totally unrelated to locking.
To say it again: I _never_ said that.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-02-27 14:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.1002261034140.4513@localhost.localdomain>
2010-02-26 19:09 ` Make b43 driver fall back gracefully to PIO mode after fatal DMA errors Larry Finger
2010-02-26 19:13 ` Linus Torvalds
2010-02-26 20:06 ` Linus Torvalds
2010-02-26 20:09 ` Gábor Stefanik
2010-02-26 20:50 ` Linus Torvalds
2010-02-26 21:01 ` Larry Finger
2010-02-26 21:45 ` Linus Torvalds
2010-02-26 21:50 ` Linus Torvalds
2010-02-26 22:08 ` Gábor Stefanik
2010-02-26 22:46 ` Linus Torvalds
2010-02-26 22:54 ` Gábor Stefanik
2010-02-27 15:04 ` Michael Buesch
2010-02-27 14:59 ` Michael Buesch
2010-02-27 18:31 ` Linus Torvalds
2010-02-27 18:51 ` Michael Buesch
2010-02-26 19:59 ` Michael Buesch
2010-02-26 20:07 ` Linus Torvalds
2010-02-26 20:20 ` Michael Buesch
2010-02-26 20:33 ` Linus Torvalds
2010-02-26 20:42 ` Linus Torvalds
2010-02-27 14:44 ` Michael Buesch [this message]
2010-02-27 14:49 ` Michael Buesch
2010-02-27 17:36 ` Michael Buesch
2010-02-27 20:12 ` Nathan Schulte
2010-02-27 21:08 ` Linus Torvalds
2010-02-27 21:43 ` Michael Buesch
2010-02-27 22:12 ` Linus Torvalds
2010-02-26 20:46 Nathan Schulte
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=201002271544.43164.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).