From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
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: Sun, 24 Apr 2011 12:28:11 +0200 [thread overview]
Message-ID: <1303640891.30421.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1303638394.14128.1.camel@maxim-laptop> (sfid-20110424_114700_368075_72827394)
On Sun, 2011-04-24 at 12:46 +0300, Maxim Levitsky wrote:
> > > I wonder how such bug could escape unnoticed.
> > > Nobody uses linux these days I guess.... :-(
> >
> > Wow, so you're one of the people who think the LED blinking is the most
> > important thing... good job...
> Good job to you for insulting peoples.
You're right I guess, that was uncalled for, sorry. Do you really
believe nobody uses Linux? :-)
> > Anyhow this was intentional, it's supposed to blink in that mode
> > according to the product documentation. If you don't like it, you can
> > now override it in sysfs.
> You mean, led is supposed to constantly blink while there is no traffic?
> You are kidding aren't you?
> At least led doesn't behave like that on any other wireless card, nor it
> does in windows
No, I'm not kidding, I know that I looked this up in the product
documentation when I wrote the patch that Wey-Yi referred to. I didn't
look at the 3945/4965, but the second generation AGN (5000+, 6000+ etc)
hw is supposed to behave that way, and later (1000+ or so?) are supposed
to just have on/off with the radio (by default).
Anyhow, I don't much care what happens to iwlegacy.
johannes
next prev parent reply other threads:[~2011-04-24 10:28 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
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 [this message]
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=1303640891.30421.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@gmail.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).