From: Michael Buesch <mb@bu3sch.de>
To: Werner Almesberger <werner@openmoko.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: AR6k: to rfkill or not to rfkill ?
Date: Fri, 19 Dec 2008 10:54:11 +0100 [thread overview]
Message-ID: <200812191054.11532.mb@bu3sch.de> (raw)
In-Reply-To: <20081218235916.GS5020@almesberger.net>
On Friday 19 December 2008 00:59:16 Werner Almesberger wrote:
> Michael Buesch wrote:
> > I think you should probably implement it.
>
> Okay, thanks for the explanation !
>
> > Rfkill is supposed to stop TX _immediately_.
> > So no MAC cleanup, etc...
>
> Hmm, I'll have to measure how quick this really gets. All this happens
> in the "black box" that is the firmware. A few ms for sure, already
> for SDIO communication. Hopefully faster than hundreds of milliseconds.
Yeah, it doesn't really matter, if it's within, say 100-200ms.
I just wanted to say, you should not _generate_ new traffic (disassoc, etc..)
if you get a kill signal. Instead you should immediately drop any connection
and kill the radio.
> > Note that current rfkill subsystem implementation is not that nice and you
> > might get some headache from it. ;)
>
> Ah, that'll be the least of my worries :-)
My head is still burning for over the last couple of months. ;)
--
Greetings, Michael.
next prev parent reply other threads:[~2008-12-19 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:22 AR6k: to rfkill or not to rfkill ? Werner Almesberger
2008-12-18 22:20 ` Michael Buesch
2008-12-18 23:59 ` Werner Almesberger
2008-12-19 9:54 ` Michael Buesch [this message]
2008-12-18 22:28 ` AR6k: to rfkill Andy Green
2008-12-18 22:37 ` Michael Buesch
2008-12-18 22:44 ` Andy Green
2008-12-18 22:43 ` Michael Buesch
2008-12-18 22:49 ` Andy Green
2008-12-20 20:15 ` AR6k: to rfkill or not to rfkill ? Henrique de Moraes Holschuh
2008-12-22 19:50 ` Werner Almesberger
2008-12-22 23:59 ` Henrique de Moraes Holschuh
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=200812191054.11532.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=werner@openmoko.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 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.