is wifi-driver developed anymore?

Paul Fertser fercerpav at
Thu Aug 13 10:54:35 CEST 2009

"arne anka" <openmoko at> writes:
>>> mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage
>>> org.freesmartphone.Usage.SetResourcePolicy WiFi enabled
>> Unnecessary and in this particular case harmful. I thought the page
>> implies that clearly enough. :(
> no. absolutely not.

I'm sorry but i can't really see how it's not :(

>>> next, where does one get fsoraw from (the ticket links to the sources,  
>>> but
>>> i never actually saw a binary, let alone a package somewhere)?
>> SHR feeds already have that. Can't say about OM2009 -- ask Angus or
>> other guys interested.
> no shr or anything oe based, plain debian.

You can simply download the .opk from SHR feeds [1] and "ar x" it,
then "tar xf data.tar.gz", and move the binary to /usr/local/bin. Not
exactly Debian way but for a proper package you'd need to ask Debian

At least that's what i did: downloaded the binary and installed it ad

>>> last but not least: if that fsoraw thing indeed is some kind of
>>> workaround, it should be easy to include it into fso by default ...
>> FSO is not a distro anymore and fsoraw is a convenience tool, not
>> necessary for the framework to function. So it's up to the distro
>> maintainers to include or not include it by default.
> i don't see what fso not being a distribution anymore has to do with it.
> - fsoraw makes use of fso functionality to handly wifi.

Not only wifi but any fso "resource"

> - the fso way of retrieving the resource is discouraged

Hm, no? fsoraw does exactly that: manages access to resources the fso

> looks to me pretty much like fso should do something about that (imho the  
> need for fsoraw shows a lack of functionality in fso anyway, but that's  
> another matter).

I can't see how you came to this (imho wrong) conclusion.

> another question: how good and reliable does that work when doing it  
> repeatedly? and how does one stop wifi?
> killing fsoraw would power off wifi again -- how is that different from  
> requesting and releasing the resource the fso way (i use  
> openmoko-panel-plugin and it seems natural to click one icon and choose  
> "enable" or "disable")?

You just kill fsoraw or wpa_supplicant and the wifi module gets
unpowered and the driver unloaded. This works automatically and every
time. That way even if the firmware was crashed it will be reloaded
without any additional actions from you side. Also by using it the way
i propose you do not trigger ifconfig up/down bug.

> "Especially recommended for WiFi since due to the bugs in the firmware and  
> the driver full power-cycle of the module is often advantageous."
> i am not quite sure, what to make from that sentence.

That knowing current situation i recommend the method i propose ;)

Be free, use free ( software!
mailto:fercerpav at

More information about the community mailing list