From: Greg KH <greg@kroah.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: stable@kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [stable] Making Intel WiFi Link 1000 usable in 2.6.31
Date: Wed, 30 Sep 2009 14:24:47 -0700 [thread overview]
Message-ID: <20090930212447.GB30093@kroah.com> (raw)
In-Reply-To: <1254339259.26521.1645.camel@rc-desk>
On Wed, Sep 30, 2009 at 12:34:19PM -0700, reinette chatre wrote:
> Hi,
>
> A few distributions would like to enable the new 1000 series Intel
> wireless hardware (Intel WiFi Link 1000BGN) in their next releases that
> are based on 2.6.31. This hardware is not usable in 2.6.31, but it can
> be enabled in this kernel with the addition of five patches.
>
> Until now we have been providing the distributions with this list of
> patches to do their own backporting.
>
> Since this seems to be a general problem for distributions and users
> alike, is it possible to consider these enabling patches for inclusion
> into 2.6.31?
>
> Here is the list:
>
> commit cc0f555d511a5fe9d4519334c8f674a1dbab9e3a
> Author: Jay Sternberg <jay.e.sternberg@intel.com>
> Date: Fri Jul 17 09:30:16 2009 -0700
>
> iwlwifi: Handle new firmware file with ucode build number in header
>
> commit cce53aa347c1e023d967b1cb1aa393c725aedba5
> Author: Jay Sternberg <jay.e.sternberg@intel.com>
> Date: Fri Jul 17 09:30:22 2009 -0700
>
> iwlwifi: update 1000 series API version to match firmware
>
> commit 02c06e4abc0680afd31bf481a803541556757fb6
> Author: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> Date: Fri Jul 17 09:30:14 2009 -0700
>
> iwlagn: modify digital SVR for 1000
>
> commit 415e49936b4b29b34c2fb561eeab867d41fc43a6
> Author: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> Date: Thu Aug 13 13:30:54 2009 -0700
>
> iwlwifi: traverse linklist to find the valid OTP block
>
> commit f7ea097d9b4e61a816c041c92548aad7c7ed7915
> Author: Reinette Chatre <reinette.chatre@intel.com>
> Date: Fri Jul 24 11:13:12 2009 -0700
>
> iwlagn: fix null pointer access during ucode load on 1000
>
> Thank you very much
Is this the order in which they should be applied?
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-30 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 19:34 Making Intel WiFi Link 1000 usable in 2.6.31 reinette chatre
2009-09-30 21:24 ` Greg KH [this message]
2009-09-30 21:53 ` [stable] " reinette chatre
2009-09-30 22:36 ` reinette chatre
2009-10-01 22:44 ` Greg KH
2009-10-01 23:16 ` reinette chatre
2009-10-01 22:46 ` patch iwlwifi-traverse-linklist-to-find-the-valid-otp-block.patch added to 2.6.31-stable tree gregkh
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=20090930212447.GB30093@kroah.com \
--to=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=stable@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.