From: Michael Buesch <mb@bu3sch.de>
To: Andy Green <andy@warmcat.com>
Cc: Werner Almesberger <werner@openmoko.org>, linux-wireless@vger.kernel.org
Subject: Re: AR6k: to rfkill
Date: Thu, 18 Dec 2008 23:37:55 +0100 [thread overview]
Message-ID: <200812182337.56050.mb@bu3sch.de> (raw)
In-Reply-To: <494ACE9B.8010709@warmcat.com>
On Thursday 18 December 2008 23:28:43 Andy Green wrote:
> Somebody in the thread at some point said:
>
> > In Openmoko, we're wondering whether we should make the Atheros AR6k
>
> Let me put that simpler for you Werner :-)
>
> "In Openmoko" we already use the nice rfkill interface to turn our USB
> bluetooth device on and off... it certainly stops RF emissions from it.
>
> Now we plan to do the same for our AR6001 implementation... it has no
> switched power to the module, it is "always on". It seems the only way
> to get it to a low power state is an IOCTL that currently needs to be
> set by a userspace app.
>
> In the same manner as we switch bluetooth, I have asked Werner to write
> a patch that will use rfkill to issue the IOCTL to switch the AR6001
> into low power / no RF mode.
>
> Does that raise any eyebrows?
Is the wireless kernel driver a binary blob?
--
Greetings, Michael.
next prev parent reply other threads:[~2008-12-18 22:42 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
2008-12-18 22:28 ` AR6k: to rfkill Andy Green
2008-12-18 22:37 ` Michael Buesch [this message]
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=200812182337.56050.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=andy@warmcat.com \
--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 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).