From: "Ondřej Kučera" <ondrej.kucera@centrum.cz>
To: Marcos Barbosa <marcosestevesbarbosa@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
jikos@suse.cz, yi.zhu@intel.com, reinette.chatre@intel.com,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] PROBLEM: Led for wifi blinking all the time
Date: Tue, 04 Nov 2008 02:58:19 +0100 [thread overview]
Message-ID: <490FAC3B.6030205@centrum.cz> (raw)
In-Reply-To: <42bbb5c30810311159v50785ac7jfc8ef8eb3e32ea9b@mail.gmail.com>
Hi,
Marcos Barbosa wrote:
> Traffic exists all the time, because the commands to control
> connection. To cancel all traffic, down the wireless interface.
OK, let me rephrase. It may by true that from a low-level point of view=
=20
there exists some traffic all the time. But let's see it from user's=20
point of view. With 2.6.26 I connected to network during which the led=20
was blinking. After the connection was established, it stopped blinking=
=20
and was just on. Then when I started downloading something (wget=20
http://server.com/foo.bar), it started blinking and shortly after the=20
download was completed, it stopped to be just "on" again. I consider=20
this a very reasonable behavior. With 2.6.27 it is blinking really all=20
the time, whether the user is consciously downloading/uploading some=20
data or not. The main problem is that such periodic non-stop blinking i=
s=20
very eye catching and it draws your attention away from the things you=20
are actually doing. So I really believe this is a regression. One more=20
reason, even though I'm not sure if I should even bring it up - on MS=20
Windows it behaves more or less in a similar manner as with 2.6.26=20
kernel. Now I'm far from saying that things should work the way they=20
work on Windows but in this case I think they actually have it right.
Ond=F8ej
--=20
Cheers,
Ond=F8ej Ku=E8era
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-04 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 1:19 PROBLEM: Led for wifi blinking all the time Ondřej Kučera
2008-10-31 14:54 ` John W. Linville
2008-10-31 18:59 ` [ipw3945-devel] " Marcos Barbosa
2008-11-04 1:58 ` Ondřej Kučera [this message]
2008-11-04 17:35 ` reinette chatre
2008-11-03 20:14 ` Tino Keitel
2008-11-04 19:03 ` Tino Keitel
2008-11-05 0:58 ` Tomas Winkler
2008-11-05 1:04 ` Tomas Winkler
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=490FAC3B.6030205@centrum.cz \
--to=ondrej.kucera@centrum.cz \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jikos@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcosestevesbarbosa@gmail.com \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@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 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.