Testing the Wireless driver changes

[Ricardo Carrano]

Indeed we had this airplane mode discussion two weeks ago:
Why don't we?
-----------

To completely silence the radio:

#!/bin/bash
rmmod usb8xxx
mv /lib/firmaware/usb8883.bin /lib/firmaware/usb8883.bin.quiet

It will survive reboots.

-----------

To bring it back:

#!/bin/bash
mv /lib/firmaware/usb8883.bin.quiet /lib/firmaware/usb8883.bin
rmmod usb8xxx; sleep1; modprobe usb8xxx

No reboot necessary.

-----------
Tested in build 684,
Do I miss something?

On Jan 17, 2008 4:30 PM, Michail Bletsas <mbletsas at laptop.org> wrote:

> Hal Murray <hmurray at megapathdsl.net> wrote on 01/17/2008 12:55:47 PM:
>
> >
> > > When it comes to our radio - we *designed it* to start forward frames
> > > soon after you initialize it and keep doing it regardless of what the
> > > host interface does.
> >
> > In the context of making the radio safe to use on airplanes...
> >
> > Does the firmware turn the radio on at boot time?
> >
> > Does your "initialize" above mean firmware level or OS level?
> >
> >
> >
> Initialize means loading the wireless firmware on the radio's ARM core and
> start running it.
>
> If you want to make sure that the radio never transmits a single bit, then
> preventing that (loading the wireless firmware) is what you need right
> now. There is explicit  mesh start/stop in the plans (already implemented
> in the firmware but not in place yet since the driver people didn't like
> it).
>
> M.
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080117/83d86711/attachment.html>