From: Dave <kilroyd@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org
Subject: Re: [Orinoco-devel] Agere PCMCIA sometimes takes very long time to associate with 9.48 FW
Date: Sun, 16 Nov 2008 10:01:45 +0000 [thread overview]
Message-ID: <491FEF89.3040100@gmail.com> (raw)
In-Reply-To: <20081115145655.GB31553@tuxdriver.com>
John W. Linville wrote:
> On Sat, Nov 15, 2008 at 11:15:47AM +0300, Andrey Borzenkov wrote:
>
>> - we should not be doing it in ->open. It is technically legal to set
>> wireless parameters before "icfonfig up" and we lose all of them. I will
>> try next week with similar patch in orinoco_stop().
>
> That seems wrong...
>
>> - I am still not even sure we should do it at all. What is sematic of
>> ifconfig up/down w.r.t. wireless parameters? I.e. is "ifconfig down"
>> expected to clean all device state and start from scratch?
>
> No. Unfortunately, it is mostly a matter of opinion as to what
> wireless extensions expects.
Agreed with all the above. I'll discard the driver patch.
There are two other things I can think of:
1. make sure wpa_supplicant is shut down before ifconfig ethX down, and
restart it on resume.
>From the data you've provided it looks like your distribution brings the
device down, but may leave wpa_supplicant running. I've noticed that
every time wpa_supplicant shuts down it removes most configuration
settings. Or has that changed?
2. Does the driver need to send a dissociation event (or something) to
userspace on ifconfig down?
Dave.
next prev parent reply other threads:[~2008-11-16 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810191436.13298.arvidjaar@mail.ru>
[not found] ` <491349BC.8090606@gmail.com>
[not found] ` <49134F66.4020608@gmail.com>
2008-11-15 8:15 ` [Orinoco-devel] Agere PCMCIA sometimes takes very long time to associate with 9.48 FW Andrey Borzenkov
2008-11-15 14:56 ` John W. Linville
2008-11-16 10:01 ` Dave [this message]
2008-11-17 15:50 ` Dan Williams
2008-11-17 19:37 ` Dave
2008-11-17 19:29 ` Andrey Borzenkov
2008-11-17 20:37 ` Dave
2008-11-22 7:56 ` Andrey Borzenkov
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=491FEF89.3040100@gmail.com \
--to=kilroyd@googlemail.com \
--cc=arvidjaar@mail.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=orinoco-devel@lists.sourceforge.net \
/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.