From: reinette chatre <reinette.chatre@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
Jay Sternberg <jay.e.sternberg@linux.intel.com>
Subject: Re: [PATCH v2.6.30 and w-t] iwlwifi: update 5000 ucode support to version 2 of API
Date: Tue, 19 May 2009 16:05:19 -0700 [thread overview]
Message-ID: <1242774319.32358.851.camel@rc-desk> (raw)
In-Reply-To: <20090519223535.GA4635@tuxdriver.com>
Hi John,
On Tue, 2009-05-19 at 15:35 -0700, John W. Linville wrote:
> On Tue, May 19, 2009 at 02:56:36PM -0700, Reinette Chatre wrote:
> > From: Jay Sternberg <jay.e.sternberg@linux.intel.com>
> >
> > enable iwl driver to support 5000 ucode having version 2 of API
> >
> > Signed-off-by: Jay Sternberg <jay.e.sternberg@linux.intel.com>
> > Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> > ---
> > This ucode indicates an API change. The backward compatibility support
> > can already be found in 2.6.30 and wireless-testing in commit
> > 964c32bdc88b3d15dce34bb9ed0903e78e95fd57 "iwlwifi: correct API command
> > overlap"
> >
> > Announcement of ucode availability to follow shortly.
>
> Does this fix a bug? What about it merits inclusion for 2.6.30?
Sorry for not including this information in original submit. The big fix
that people are waiting on is the fix for the "wrong command queue"
problem that shows up irregularly. This is tracked in
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1946 and
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1963 (marked
as duplicates). We used to have a bug for this in kernel.org bugzilla
(http://bugzilla.kernel.org/show_bug.cgi?id=12819 ) but it has been
closed as unreproducible.
Another big fix is an issue that the calibration was run in wrong
order ... one calibration needed information from another run, but it
was run before the one it depended on. This resulted in poor
performance. Unfortunately we do not have a bug report for this.
The other fixes in this firmware are "nice to have".
Reinette
prev parent reply other threads:[~2009-05-19 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 21:56 [PATCH v2.6.30 and w-t] iwlwifi: update 5000 ucode support to version 2 of API Reinette Chatre
2009-05-19 22:35 ` John W. Linville
2009-05-19 23:05 ` reinette chatre [this message]
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=1242774319.32358.851.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jay.e.sternberg@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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