From: reinette chatre <reinette.chatre@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: New iwlwifi 3945 uCode available
Date: Tue, 21 Oct 2008 14:59:52 -0700 [thread overview]
Message-ID: <1224626392.10863.92.camel@rc-desk> (raw)
In-Reply-To: <1224624899.28639.17.camel@johannes.berg>
On Tue, 2008-10-21 at 14:34 -0700, Johannes Berg wrote:
> On Tue, 2008-10-21 at 23:33 +0200, Tomas Winkler wrote:
> > On Tue, Oct 21, 2008 at 11:25 PM, Johannes Berg
> > <johannes@sipsolutions.net> wrote:
> > > On Tue, 2008-10-21 at 11:27 -0700, reinette chatre wrote:
> > >> Two new versions of 3945 uCode is now available for download from
> > >> http://intellinuxwireless.org/?n=Downloads. Two versions are available
> > >> as we have updated the API version of the uCode and included pending
> > >> fixes in both API versions.
> > >>
> > >> Version 15.28.1.8 supports API v1 and can be used with most current 3945
> > >> drivers. Version 15.28.2.8 (API v2) is required when you start using the
> > >> latest 3945 driver from wireless-testing at the time it includes the
> > >> patch "iwl3945 : Fix a-band association for passive channels".
> > >
> > > Can you make the driver work with the old ucode? We even do that for
> > > drivers where we don't control the ucode like b43...
> >
> > What for?
>
> Well, so that installing a new kernel doesn't suddenly break your
> network connection and ability to download the firmware, for instance.
> If you want more arguments you can go read all the "b43 sucks" threads
> about it.
Using the new driver (with patch
http://marc.info/?l=linux-wireless&m=122401294318415&w=2 ) on current
(v1 API) uCode will cause a firmware error. The log message should be
clear that a newer ucode is required.
Reinette
next prev parent reply other threads:[~2008-10-21 21:59 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
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 [this message]
-- 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=1224626392.10863.92.camel@rc-desk \
--to=reinette.chatre@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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