From: Christian Lamparter <chunkeey@web.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
John W Linville <linville@tuxdriver.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Pavel Roskin <proski@gnu.org>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH 3/4] p54: protect against sudden firmware file changes
Date: Sat, 15 Nov 2008 00:54:29 +0100 [thread overview]
Message-ID: <200811150054.30113.chunkeey@web.de> (raw)
In-Reply-To: <1226700028.4120.28.camel@johannes.berg>
On Friday 14 November 2008 23:00:28 Johannes Berg wrote:
> On Fri, 2008-11-14 at 19:41 +0100, Christian Lamparter wrote:
> > Thanks to "p54: introduce new names for device firmwares"
> > (325ca16910a380c...) people are now migrating away from the buggy firmwares.
> > Of course this is a very good idea, but no one told them to unload the driver first.
>
> that seems weird. Doesn't the driver pretty much have to cache the
> firmware anyway for suspend/resume?
well, that's odd. No one complained about this bug yet?!
Even better, this bug/quirk is even present in the initial p54pci version that made it
into the kernel. In fact it looks like its even present in the fullmac driver! Luis?
I guess, I have to leave it that way to provide "bug-to-bug" compatibility! ;-)
Regards,
Chr
next prev parent reply other threads:[~2008-11-14 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:41 [PATCH 3/4] p54: protect against sudden firmware file changes Christian Lamparter
2008-11-14 22:00 ` Johannes Berg
2008-11-14 23:54 ` Christian Lamparter [this message]
2008-11-15 0:02 ` Johannes Berg
2008-11-15 0:42 ` [PATCH 3/4] p54pci: cache firmware for suspend/resume Christian Lamparter
2008-11-15 18:30 ` [PATCH 3/4] p54pci: cache firmware for suspend/resume v2 Christian Lamparter
2008-11-16 11:20 ` [PATCH 3/4] p54pci: cache firmware for suspend/resume v2.1 Christian Lamparter
2008-11-16 15:35 ` Larry Finger
2008-11-16 15:36 ` Johannes Berg
2008-11-15 0:35 ` [PATCH 3/4] p54: protect against sudden firmware file changes Luis R. Rodriguez
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=200811150054.30113.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=proski@gnu.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).