Somebody in the thread at some point said:
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?
No, Openmoko won't have anything to do with in-kernel binary blobs.
There is binary firmware in it in flash though.
It's not very kernel style C:
http://git.openmoko.org/?p=kernel.git;a=tree;f=drivers/ar6000;h=ab7abd9222054919a3cd0ce6ecbec64b6057cbed;hb=andy-tracking
-Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
