From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Meenakshi Venkataraman <meenakshi.venkataraman@intel.com>
Subject: Re: [PATCH 4/4] iwlwifi: split the drivers for agn and legacy devices 3945/4965
Date: Sat, 23 Apr 2011 14:35:17 +0300 [thread overview]
Message-ID: <1303558517.8537.7.camel@maxim-laptop> (raw)
In-Reply-To: <1298315209-17986-5-git-send-email-wey-yi.w.guy@intel.com>
On Mon, 2011-02-21 at 11:06 -0800, Wey-Yi Guy wrote:
> From: Meenakshi Venkataraman <meenakshi.venkataraman@intel.com>
>
> Intel WiFi devices 3945 and 4965 now have their own driver in the folder
>
> drivers/net/wireless/iwlegacy
>
> Add support to build these drivers independently of the driver for
> AGN devices. Selecting the 3945 builds iwl3945.ko and iwl_legacy.ko,
> and selecting the 4965 builds iwl4965.ko and iwl_legacy.ko. iwl-legacy.ko
> contains code shared between both devices.
>
> The 3945 is an ABG/BG device, with no support for 802.11n. The 4965 is a 2x3
> ABGN device.
This one came to me as a surprise, I updated the kernel, and whoops, the
wireless led, blinks all the time!
It turns out that in splitted driver iwl3945 doesn't have any led
support, and indeed the light on my notebook doesn't change state often.
It ether doesn't light up at all, or just blinks at constant rate.
I have iwl3945.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2011-04-23 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 19:06 [PATCH 0/4] update for 2.6.39 Wey-Yi Guy
2011-02-21 19:06 ` [PATCH 1/4] iwlwifi: Limit number of firmware reload Wey-Yi Guy
2011-02-21 19:06 ` [PATCH 2/4] iwlwifi: Loading correct uCode again when fail to load Wey-Yi Guy
2011-02-21 19:06 ` [PATCH 3/4] iwlwifi: enable 2-wire bt coex support for non-combo device Wey-Yi Guy
2011-02-21 19:06 ` [PATCH 4/4] iwlwifi: split the drivers for agn and legacy devices 3945/4965 Wey-Yi Guy
2011-04-23 11:35 ` Maxim Levitsky [this message]
2011-04-23 12:40 ` Maxim Levitsky
2011-04-23 16:03 ` wwguy
2011-04-24 8:13 ` Johannes Berg
2011-04-24 9:46 ` Maxim Levitsky
2011-04-24 10:28 ` Johannes Berg
2011-02-21 19:09 ` [PATCH 0/4] update for 2.6.39 Guy, Wey-Yi
2011-02-21 19:27 ` John W. Linville
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=1303558517.8537.7.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meenakshi.venkataraman@intel.com \
--cc=wey-yi.w.guy@intel.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).