From: Zhu Yi <yi.zhu@intel.com>
To: Nico -telmich- Schottelius <nico-linux-iwlwifi5100@schottelius.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.28-rc4: iwlagn / 5100 state
Date: Mon, 17 Nov 2008 11:58:19 +0800 [thread overview]
Message-ID: <1226894299.2548.19.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20081114150508.GC4877@denkbrett.schottelius.org>
On Fri, 2008-11-14 at 23:05 +0800, Nico -telmich- Schottelius wrote:
> - loading the firmware "freezes" the system for a few seconds
> - setting the link up of wlan0 "freezes" the system for a few
> seconds
We use a wait_event_interruptible_timeout in mac80211 start callback to
make sure firmware is loading OK before 'ifconfig wlan0 up' returns.
This prevents the EREADY error some wireless configuration commands
immediately followed by link up (usually in some scripts). The timeout
is 4 seconds, but usually firmware responses in less than 500ms. Did you
see the "freeze" in a failure case?
> - connecting to 802.11b/g works (802.11a is untested)
> - roaming does *NOT* work -> just looses the AP, does not connect
> to other AP with same essid
This needs to be addressed in user level (i.e. NM).
> - connecting to a ap sometimes does not work, though essid is set
> -> sometimes it helps to specify "ap <addr>"
This is not required with recent mac80211.
> -> sometimes setting down and up the link helps
> -> with earlier kernels one sometimes needed to rmmod and insmod
> the module again, so there is some progress :-)
These are unexpected behaviours. Please report bugs to
http://bughost.org.
Thanks,
-yi
prev parent reply other threads:[~2008-11-17 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 15:05 2.6.28-rc4: iwlagn / 5100 state Nico -telmich- Schottelius
2008-11-15 23:22 ` Rafael J. Wysocki
2008-11-17 3:58 ` Zhu Yi [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=1226894299.2548.19.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-linux-iwlwifi5100@schottelius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox