From: Marcel Holtmann <holtmann@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: reinette chatre <reinette.chatre@linux.intel.com>,
Tomas Winkler <tomasw@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: New iwlwifi 3945 uCode available
Date: Wed, 22 Oct 2008 09:56:25 +0200 [thread overview]
Message-ID: <1224662185.9386.131.camel@californication> (raw)
In-Reply-To: <1224660449.28639.22.camel@johannes.berg>
Hi Johannes,
> > I do not believe our request is unreasonable. If a user runs a new
> > kernel the log will print a message that the firmware is incorrect ...
> > all the user needs to do is go to
> > http://intellinuxwireless.org/?n=Downloads and download the latest
> > firmware.
>
> And that exactly _is_ a problem, the user may be relying on wireless
> connectivity. And they won't know up-front they need new firmware. Since
> firmware is loaded from userspace, you're breaking userspace/kernel ABI,
> it's pretty simple really.
I talked to David Woodhouse and we plan to add a big warning to
modules_install when MODULE_FIRMWARE is not present on the filesystem.
> I really don't know why we let you get away with this and bitch
> endlessly when b43 does such a change, to the point where we finally
> cave in and support both versions. Why should a community-supported
> driver be held to higher standards?
If in any way possible, we should support both versions of the firmware.
Regards
Marcel
next prev parent reply other threads:[~2008-10-22 7:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 18:27 New iwlwifi 3945 uCode available reinette chatre
2008-10-21 21:25 ` Johannes Berg
2008-10-21 21:33 ` Tomas Winkler
2008-10-21 21:34 ` Johannes Berg
2008-10-21 21:38 ` John W. Linville
2008-10-21 21:53 ` Tomas Winkler
2008-10-21 22:13 ` Marcel Holtmann
2008-10-21 22:23 ` Tomas Winkler
2008-10-21 23:01 ` Marcel Holtmann
2008-10-21 23:09 ` Luis R. Rodriguez
2008-10-21 23:11 ` Marcel Holtmann
2008-10-21 23:27 ` Luis R. Rodriguez
2008-10-21 23:31 ` Marcel Holtmann
2008-10-21 23:34 ` Luis R. Rodriguez
2008-10-21 22:28 ` reinette chatre
2008-10-21 23:06 ` Marcel Holtmann
2008-10-21 23:34 ` Tomas Winkler
2008-10-22 1:03 ` Marcel Holtmann
2008-10-22 7:27 ` Johannes Berg
2008-10-22 7:56 ` Marcel Holtmann [this message]
2008-10-22 7:57 ` Johannes Berg
2008-10-22 20:30 ` reinette chatre
2008-10-22 22:59 ` Marcel Holtmann
2008-10-22 23:14 ` reinette chatre
2008-10-22 23:39 ` John W. Linville
2008-10-23 1:12 ` Marcel Holtmann
2008-10-23 7:22 ` Johannes Berg
2008-10-22 9:10 ` Tomas Winkler
2008-10-22 9:14 ` Johannes Berg
2008-10-22 9:23 ` Tomas Winkler
2008-10-22 10:07 ` Christoph Hellwig
2008-10-22 12:28 ` Tomas Winkler
2008-10-22 18:25 ` Marcel Holtmann
2008-10-24 12:45 ` Florian Mickler
2008-10-21 21:59 ` reinette chatre
-- strict thread matches above, loose matches on Subject: below --
2009-04-28 20:52 new " reinette chatre
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=1224662185.9386.131.camel@californication \
--to=holtmann@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@linux.intel.com \
--cc=tomasw@gmail.com \
/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).