Re: is wifi-driver developed anymore?
Ben Thompson writes: > On Wed, Aug 26, 2009 at 09:46:38AM +0400, Paul Fertser wrote: >> >> I tell you the most nasty bugs are in firmware. Which we don't have >> >> sources for and don't know a way to update anyway. Blame Atheros. >> > >> > please may you elaborate a bit more? >> > How kernel ops are related to ar6000 firmware bugs? >> >> It's hard to be motivated to basically rewrite the driver if you know >> that the nastiest bugs will still be there. BTW, i have a "fix" for >> the bind/unbind problem, but not for the "ioctls to the device which >> is down". >> >> The driver was bad and now it's even in worse condition because of all >> the tweaking. Solving one race condition results in exposing >> another. The addition of rfkill support multiplied the possibilities >> even further... >> >> Currently (great thanks to Harald!) we're waiting another answer from >> Atheros but do not hold your breath. > > Does anyone know whether an answer to this ever came back from > Atheros? Basically, Luis told several times he's trying to push it internally but it looks like he got nowhere. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 26, 2009 at 09:46:38AM +0400, Paul Fertser wrote: > >> I tell you the most nasty bugs are in firmware. Which we don't have > >> sources for and don't know a way to update anyway. Blame Atheros. > > > > please may you elaborate a bit more? > > How kernel ops are related to ar6000 firmware bugs? > > It's hard to be motivated to basically rewrite the driver if you know > that the nastiest bugs will still be there. BTW, i have a "fix" for > the bind/unbind problem, but not for the "ioctls to the device which > is down". > > The driver was bad and now it's even in worse condition because of all > the tweaking. Solving one race condition results in exposing > another. The addition of rfkill support multiplied the possibilities > even further... > > Currently (great thanks to Harald!) we're waiting another answer from > Atheros but do not hold your breath. Hi Does anyone know whether an answer to this ever came back from Atheros? Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 26, 2009 at 3:19 PM, Paul Fertser wrote: [...] >> Sure! may you point me to the correct kernel branch to checkout? > > andy-tracking of course :) Thanks! I was out for holidays so just to be sure ;) I'll report back asap! regards and thanks for your effort! Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 26, 2009 at 03:14:24PM +0200, Nicola Mfb wrote: > On Wed, Aug 26, 2009 at 3:01 PM, Paul Fertser wrote: > [...] > > Can you give me a list of regressions with the latest driver version > > with the patch i've sent to the kernel ML applied? > > > > I know only about http://docs.openmoko.org/trac/ticket//2277 but that > > can be workarounded by not touching eth0 when it's down. > > Sure! may you point me to the correct kernel branch to checkout? andy-tracking of course :) HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 26, 2009 at 3:01 PM, Paul Fertser wrote: [...] > Can you give me a list of regressions with the latest driver version > with the patch i've sent to the kernel ML applied? > > I know only about http://docs.openmoko.org/trac/ticket//2277 but that > can be workarounded by not touching eth0 when it's down. Sure! may you point me to the correct kernel branch to checkout? Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Nicola Mfb writes: > I'd like to see a form of "acceptable" stability, when my system > crashes due to wifi in the 99% of cases even the "reboot" command > segfaults and I have to remove the battery. With old kernels I got > "wow interrupts" and other forms of instability but at least the > device continues to work. Can you give me a list of regressions with the latest driver version with the patch i've sent to the kernel ML applied? I know only about http://docs.openmoko.org/trac/ticket//2277 but that can be workarounded by not touching eth0 when it's down. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 26, 2009 at 7:46 AM, Paul Fertser wrote: [...] > It's hard to be motivated to basically rewrite the driver if you know > that the nastiest bugs will still be there. BTW, i have a "fix" for > the bind/unbind problem, but not for the "ioctls to the device which > is down". > > The driver was bad and now it's even in worse condition because of all > the tweaking. Solving one race condition results in exposing > another. The addition of rfkill support multiplied the possibilities > even further... Umh, I understand and feel very frustrated :(, the lack of UMTS may be accepted only with a reliable WiFi. I'd like to see a form of "acceptable" stability, when my system crashes due to wifi in the 99% of cases even the "reboot" command segfaults and I have to remove the battery. With old kernels I got "wow interrupts" and other forms of instability but at least the device continues to work. If possibile please revert to some old driver or fix the current even if the firmware may cause problems. I started a proof-of-concept work on a wifi manager some months ago, it works quite well with 2.6.28, added support for static ip, complex wpa enterprise configuration, vibration on connect, popup messages and so on, but I'm losing the enthusiasm to further develop it and as of your words I'm beginning to think I should look for a device replacement :( > Currently (great thanks to Harald!) we're waiting another answer from > Atheros but do not hold your breath. Thanks Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Hi, Nicola Mfb writes: > On Wed, Aug 12, 2009 at 9:51 PM, Paul Fertser wrote: >>> then please help me someone to learn the necessary-things about >>> kernel-hacking >>> (i know, it's a lot of work!) to fix this bugs in wifi? >> >> I tell you the most nasty bugs are in firmware. Which we don't have >> sources for and don't know a way to update anyway. Blame Atheros. > > please may you elaborate a bit more? > How kernel ops are related to ar6000 firmware bugs? It's hard to be motivated to basically rewrite the driver if you know that the nastiest bugs will still be there. BTW, i have a "fix" for the bind/unbind problem, but not for the "ioctls to the device which is down". The driver was bad and now it's even in worse condition because of all the tweaking. Solving one race condition results in exposing another. The addition of rfkill support multiplied the possibilities even further... Currently (great thanks to Harald!) we're waiting another answer from Atheros but do not hold your breath. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Wed, Aug 12, 2009 at 9:51 PM, Paul Fertser wrote: [...] >> then please help me someone to learn the necessary-things about >> kernel-hacking >> (i know, it's a lot of work!) to fix this bugs in wifi? > > I tell you the most nasty bugs are in firmware. Which we don't have > sources for and don't know a way to update anyway. Blame Atheros. Hi Paul! please may you elaborate a bit more? How kernel ops are related to ar6000 firmware bugs? Thanks Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FSO resources (Was: is wifi-driver developed anymore?)
On Thu, Aug 13, 2009 at 10:58:54AM -0400, Warren Baird wrote: > On Thu, Aug 13, 2009 at 10:56 AM, Warren Baird > wrote: > > > I believe that "fsoraw -r RESOURCE myprogram" is approximately like writing > > a script like: >#!/bin/sh >mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy RESOURCE enabled >myprogram >mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy RESOURCE disabled No, SetResourcePolicy does something entirely different than fsoraw (RequestResource). Why do you not try it both ways? You can use "sleep 20" for "myprogram" and "GPS" for "RESOURCE" and with both, try to see if you can get TangoGPS or some such gpsd user to work afterwards. Reboot before each attempt so you start from a known working state. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FSO resources, GPS-TTFF example (Was: is wifi-driver developed anymore?)
On 8/14/09, arne anka wrote:
>> If the app doesn't have FSO support, use fsoraw to request the resource.
>
> _now_ i am confused.
> in my understanding
> - "resources" are an fso concept -- thus, no fso support, no resource
> - fsoraw uses fso calls to utilize the resource -- no resource, no way to
> use fsoraw
>
>>> why using fsoraw, why isn't fso sufficient?
>>
>>You are confused. Fsoraw uses FSO.
>
>
> sorry, but imo _you_ are confused. i never denied, fsoraw using fso.
>
> what i always tried to find out, and i understand now even less than
> before: what is the rationale for fsoraw?
>
> if it does nothing but requesting the resource, a dbus call would do
> exactly the same w/o need of an additional app (and second one to release
> afterwards, of course).
> if it does soemthing a dbus call won't be able to deliver, why isn't fso
> extended to include that functionality?
fsoraw == dbus calls arround starting application. That's you who is
confused here :P
Little C wrapper which do dbus calls is just more practical than bash
script which uses mdbus or dbus-send. And using Request/Release method
isn't possible with dbus-send and mdbus, as they quit just after
calling dbus method, so resource is released immediately after
requesting.
fsoraw is only small wrapper which do something like
"dbus.call_request_resource(); system('run-app').
dbus.call_release_resource()". Nothing else (maybe except command line
parsing :P). App itself can do exactly the same (and should), but
patching every possible app which can run on Freerunner is insane, so
that's why fsoraw is usable.
--
Sebastian Krzyszkowiak
dos
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: FSO resources, GPS-TTFF example (Was: is wifi-driver developed anymore?)
On Fri, 2009-08-14 at 14:15 +0200, arne anka wrote: > > If the app doesn't have FSO support, use fsoraw to request the resource. > > _now_ i am confused. > in my understanding ... > what i always tried to find out, and i understand now even less than > before: what is the rationale for fsoraw? > > if it does nothing but requesting the resource, a dbus call would do > exactly the same w/o need of an additional app (and second one to release > afterwards, of course). > if it does soemthing a dbus call won't be able to deliver, why isn't fso > extended to include that functionality? > fsoraw, mdbus and dbus-send all allow management of resources. mdbus is slow - very slow - its was apparently a test tool that proved useful. An advantage that it does have is that it can request some resources and they stay requested until you specifically request them to be released. I was never able to use dbus-send reliably though it was reccomended as a replacement for mdbus. fsoraw is fast - thats its main advantage, plus when it requests a resource, it releases it on exit - so when the app called by fsoraw exits, fsoraw then also exits and the resource is automaticly released. All fsoraw seems to be is a program that calls the dbus libraries directly, hence its speed. BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FSO resources, GPS-TTFF example (Was: is wifi-driver developed anymore?)
> If the app doesn't have FSO support, use fsoraw to request the resource. _now_ i am confused. in my understanding - "resources" are an fso concept -- thus, no fso support, no resource - fsoraw uses fso calls to utilize the resource -- no resource, no way to use fsoraw >> why using fsoraw, why isn't fso sufficient? > >You are confused. Fsoraw uses FSO. sorry, but imo _you_ are confused. i never denied, fsoraw using fso. what i always tried to find out, and i understand now even less than before: what is the rationale for fsoraw? if it does nothing but requesting the resource, a dbus call would do exactly the same w/o need of an additional app (and second one to release afterwards, of course). if it does soemthing a dbus call won't be able to deliver, why isn't fso extended to include that functionality? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fsoraw (Was: is wifi-driver developed anymore?)
On Wed, Aug 12, 2009 at 10:31:13PM +0200, arne anka wrote: > > 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)? IIRC, I found it on the mokomaze site. $ dpkg-query --search $(which fsoraw) fsoraw: /usr/bin/fsoraw $ dpkg-query --status fsoraw Package: fsoraw Status: install ok installed Priority: optional Section: utils Maintainer: ANT Architecture: armel Source: fsoraw Version: 0.01a+svn13-r1 Depends: libdbus-1-3 Description: FSO Resource Allocation Wrapper. You may use it to prevent suspending or light dimming. Homepage: http://noko.svn.sourceforge.net/viewvc/noko/trunk/fsoraw/ -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FSO resources, GPS-TTFF example (Was: is wifi-driver developed anymore?)
On Thu, Aug 13, 2009 at 11:15:31AM +0200, arne anka wrote:
>
> >> - the fso way of retrieving the resource is discouraged
> >
> > Hm, no? fsoraw does exactly that: manages access to resources the fso
> > way.
>
> it's not that i know all these fso dbus commands by heart, but
>
> mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage
> org.freesmartphone.Usage.SetResourcePolicy WiFi enabled
>
> which you called "in this particular case harmful", looks pretty much like
> the fso way to me. am i wrong?
Yes. :-( You should not use SetResourcePolicy if you can at all avoid
it. If an app needs a resource, it should call RequestResource instead.
If the app doesn't have FSO support, use fsoraw to request the resource.
There is a bit of trickery in using fsoraw with a shell script. You can
either make the script call itself with fsoraw except if given a command
line option such as --no-fsoraw, or use a here-document. Example of the
latter:
#!/bin/sh
# GPS-TTFF - Find GPS time to first fix using all the important buzz-words
# such as D-bus, Gypsy, freedesktop.org and freesmartphone.org.
# Destinations and paths are listed in /etc/dbus-1/system.d/*.
# Interfaces are "documented" at http://docs.freesmartphone.org/>.
fsoraw -r GPS -- sh <<"__end_of_script"
DBUSCALL_='dbus-send --print-reply=undocumented --system --type=method_call
--dest='
if [ "--coldstart" = "$1" ]; then
rm -f /var/lib/freesmartphone/ogpsd.pickle
fi
START=$(date +%s)
# Where is the first return value from GetPosition documented?
while ${DBUSCALL_}org.freedesktop.Gypsy /org/freedesktop/Gypsy
org.freedesktop.Gypsy.Position.GetPosition \
| head -n 1 | grep -q -v -F -e 'int32 15' -e 'int32 7'; do
sleep 1
done
FINISH=$(date +%s)
echo "Time to first fix: $((${FINISH} - ${START})) s"
${DBUSCALL_}org.freedesktop.Gypsy /org/freedesktop/Gypsy
org.freedesktop.Gypsy.Position.GetPosition
__end_of_script
Please compare with how it should not be done, by a clueless newbie:
https://lists.openmoko.org/pipermail/community/2009-July/050629.html
> why is simply requesting the resource like openmoko-panel-plugin does,
> sufficient?
Requesting the resource tells FSO that an app wants to use the resource.
If the policy permits, FSO will arrange for the resource to be available.
> which is the rationale for fsoraw here?
To request resources for apps that don't have FSO support themselves.
> why using fsoraw, why isn't fso sufficient?
You are confused. Fsoraw uses FSO.
--
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On 8/13/09, Warren Baird wrote: > Whoops - hit send too early... the shell script should have looked like > this: > >#!/bin/sh >mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy RESOURCE enabled >myprogram >mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy RESOURCE disabled > > except that with the shell script approach, if the script itself is killed, > the resource isn't released. > > I believe Paul's point is that fsoraw is a perfectly legitimate and > "FSO-like" way of holding a resource while a program is running... > > Warren > > > On Thu, Aug 13, 2009 at 10:56 AM, Warren Baird > wrote: > >> Hi Arne, >> >> From my understanding of things - fsoraw is just a short-cut to hold an >> FSO >> resource while a program runs. >> >> I believe that "fsoraw -r RESOURCE myprogram" is approximately like >> writing >> a script like: >>#!/bin/sh >>mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage >> org.freesmartphone.Usage.SetResourcePolicy Bluetooth enabled >> >> >> >> On Thu, Aug 13, 2009 at 5:34 AM, arne anka wrote: >> >>> > I'm afraid yes. To me it looks like you haven't really read the page >>> >>> ah, that's the easy way out. you wrote the page, i assume ... >>> >>> well, i am still convinced, fso should do something about that instead of >>> relying on some 3d party app. As discussed on IRC - no. It doesn't do refcounting. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Whoops - hit send too early... the shell script should have looked like this: #!/bin/sh mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy RESOURCE enabled myprogram mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy RESOURCE disabled except that with the shell script approach, if the script itself is killed, the resource isn't released. I believe Paul's point is that fsoraw is a perfectly legitimate and "FSO-like" way of holding a resource while a program is running... Warren On Thu, Aug 13, 2009 at 10:56 AM, Warren Baird wrote: > Hi Arne, > > From my understanding of things - fsoraw is just a short-cut to hold an FSO > resource while a program runs. > > I believe that "fsoraw -r RESOURCE myprogram" is approximately like writing > a script like: >#!/bin/sh >mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy Bluetooth enabled > > > > On Thu, Aug 13, 2009 at 5:34 AM, arne anka wrote: > >> > I'm afraid yes. To me it looks like you haven't really read the page >> >> ah, that's the easy way out. you wrote the page, i assume ... >> >> well, i am still convinced, fso should do something about that instead of >> relying on some 3d party app. >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> > > > > -- > Warren Baird - Photographer and Digital Artist > http://www.synergisticimages.ca > -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Hi Arne, >From my understanding of things - fsoraw is just a short-cut to hold an FSO resource while a program runs. I believe that "fsoraw -r RESOURCE myprogram" is approximately like writing a script like: #!/bin/sh mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy Bluetooth enabled On Thu, Aug 13, 2009 at 5:34 AM, arne anka wrote: > > I'm afraid yes. To me it looks like you haven't really read the page > > ah, that's the easy way out. you wrote the page, i assume ... > > well, i am still convinced, fso should do something about that instead of > relying on some 3d party app. > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 14:59:13 Paul Fertser wrote: > "arne anka" writes: > >> Keeping the module loaded and just request/release it via FSO (I have a > >> little > >> GUI for this) should be pretty safe? > > > > according to > > > > "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." > > > > the module should get unloaded when not used anymore. > > Sorry, i wasn't precise enough. In fact the module is not unloaded but > is bound/unbound. The effect is the same, according to Werner. FYI: http://lwn.net/Articles/143397/ > > >> I just have to avoid suspend though. > > Are you sure? For me suspend didn't harm wifi usage. Had not tried it in a while - but it worked once now :) - so I will not release WiFi before my next suspends and see what happens. Thanks for this hint. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
"arne anka" writes: >> Keeping the module loaded and just request/release it via FSO (I have a >> little >> GUI for this) should be pretty safe? > > according to > > "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." > > the module should get unloaded when not used anymore. Sorry, i wasn't precise enough. In fact the module is not unloaded but is bound/unbound. The effect is the same, according to Werner. >> I just have to avoid suspend though. Are you sure? For me suspend didn't harm wifi usage. > but when the module is unloaded according to the quote, it should be > simply reloaded the next time and thus be reset -- even after > suspend/resume? Essentially when the device is suspended, the wifi module is unpowered, so every time the device is resumed, the driver is "restarted" and so is the module. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> Keeping the module loaded and just request/release it via FSO (I have a > little > GUI for this) should be pretty safe? according to "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." the module should get unloaded when not used anymore. > I just have to avoid suspend though. 'tis pity. but when the module is unloaded according to the quote, it should be simply reloaded the next time and thus be reset -- even after suspend/resume? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 14:17:23 David Fokkema wrote: > On Thu, 2009-08-13 at 16:06 +0400, Paul Fertser wrote: > > David Fokkema writes: > > > On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: > > >> "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. > > > > > > Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this > > > will probably kill the module? > > > > Powercycling the module can't kill it :D > > Ah, no, you're right, :-P However, IIRC, there were some posts and bug > comments somewhere that show that unloading/reloading the module can > cause severe breakage and render wifi unusable. > > David To summarise this for me: Keeping the module loaded and just request/release it via FSO (I have a little GUI for this) should be pretty safe? I am currently using it this way and wpa_supplicant's roaming capabilities with some minor modifications to the network scripts and it's quite reliable - I just have to avoid suspend though. FYI: the roaming is the same setup as on Debian on my notebook - just on my SHR-U Freerunner. Christian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 at 16:06 +0400, Paul Fertser wrote: > David Fokkema writes: > > On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: > >> "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. > > > > Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this will > > probably kill the module? > > Powercycling the module can't kill it :D Ah, no, you're right, :-P However, IIRC, there were some posts and bug comments somewhere that show that unloading/reloading the module can cause severe breakage and render wifi unusable. David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
David Fokkema writes: > On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: >> "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. > > Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this will > probably kill the module? Powercycling the module can't kill it :D -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: > "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. Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this will probably kill the module? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
>> well, i am still convinced, fso should do something about that instead >> of >> relying on some 3d party app. > > I think this is really getting OT... i am not quite sure. somehow i got the feeling that there a lot of people out there not still sure, what to do with wifi, but leaving it nevertheless alone for most of the time (as i do with frinst bluetooth) because it is not that crucial. it is pretty much possible that i am to dense to undertsnad that wiki page, but both for statistical reasons and judging my self-esteem i am convinced, that i am far from being the only one being confused by that wiki page. so, getting some light in the darkness around wifi, fso, fsoraw is probably a good thing ... and if it leads to some questions reaching further than just wifi, so be it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> well, i am still convinced, fso should do something about that instead of > relying on some 3d party app. I think this is really getting OT...but still I want to put my head. I think what you mean here that fsoraw should be a part of FSO in the same sense as mdbus is. Both are just reference/handy/easy-to-use/make-life-easy apps which are using the services provided by the framework (like resource management, etc) I think its a debate is about what all should be included in linux distribution (~FSO) which has apps (~mdbus, fsoraw) and kernel (~framework) --Vikas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> I'm afraid yes. To me it looks like you haven't really read the page ah, that's the easy way out. you wrote the page, i assume ... well, i am still convinced, fso should do something about that instead of relying on some 3d party app. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
"arne anka" writes: >>> - the fso way of retrieving the resource is discouraged >> >> Hm, no? fsoraw does exactly that: manages access to resources the fso >> way. > > it's not that i know all these fso dbus commands by heart, but > > mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage > org.freesmartphone.Usage.SetResourcePolicy WiFi enabled > > which you called "in this particular case harmful", looks pretty much like > the fso way to me. am i wrong? I'm afraid yes. To me it looks like you haven't really read the page and/or misunderstood the "resources" concept, sorry. >>> 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. > > why is simply requesting the resource like openmoko-panel-plugin does, > sufficient? which is the rationale for fsoraw here? Automatic resource management. > why using fsoraw, why isn't fso sufficient? fsoraw uses fso. It's a wrapper for apps that do not (and shouldn't) support fso resources "natively". >>> 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. > > how is that different from plain fso? > i recently tried > - enable via openmoko-panel-plugin (opp) > - run wpa_supplicant > - got associated to my ap > the something went wrong, so i disabled via opp and re-enabled, but no > good -- wpa_supplicant did not get any association and disabling wifi > again and attempting to unload ar6000 the console just got stuck. Well, probably you hit some kernel or opp or firmware bug, hard to say which exactly. > since opp uses the official fso way to enable/disable resources and i > still got those issues, apparently fsoraw does something different. Yes, fsoraw doesn't enable/disable resources and it makes little sense to do that. It requests resources and they got released as soon as they're not needed anymore. > when the way fsoraw does things, is ok with fso and furthermore, at least > for wifi, is the only sane way to get wifi working, it _should_ be done in > fso itself, since it apparently signifies a shortcoming in fso. It _is_ done in fso itself. Just wpa_supplicant needs a wrapper because it's not supposed to request the resource itself. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
>> 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" of course, but we're speaking of wifi here. >> - the fso way of retrieving the resource is discouraged > > Hm, no? fsoraw does exactly that: manages access to resources the fso > way. it's not that i know all these fso dbus commands by heart, but mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled which you called "in this particular case harmful", looks pretty much like the fso way to me. am i wrong? >> 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. why is simply requesting the resource like openmoko-panel-plugin does, sufficient? which is the rationale for fsoraw here? why using fsoraw, why isn't fso sufficient? >> 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. how is that different from plain fso? i recently tried - enable via openmoko-panel-plugin (opp) - run wpa_supplicant - got associated to my ap the something went wrong, so i disabled via opp and re-enabled, but no good -- wpa_supplicant did not get any association and disabling wifi again and attempting to unload ar6000 the console just got stuck. since opp uses the official fso way to enable/disable resources and i still got those issues, apparently fsoraw does something different. when the way fsoraw does things, is ok with fso and furthermore, at least for wifi, is the only sane way to get wifi working, it _should_ be done in fso itself, since it apparently signifies a shortcoming in fso. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
"arne anka" 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 maintainers. At least that's what i did: downloaded the binary and installed it ad hoc. >>> 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 way. > 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 (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> Here's a quote from the page you mentioned: > > " > Especially recommended for WiFi since due to the bugs in the firmware > and the driver full power-cycle of the module is often advantageous. > > Example command (works for open, WEP and WPA/WPA2 networks, > automatically determining the network it can connect to, just add all > the networks you use to the config): > > fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext > -c/etc/wpa_supplicant/wpa_supplicant.conf > " still doesn't say "workaround" to me, but ok. >> 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. >> 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. >> 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. - the fso way of retrieving the resource is discouraged 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). 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")? "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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Am Mittwoch, 12. August 2009 23.01:51 schrieben Sie: > I really wonder how omitting the list from CC can help you prepare a > petition. > normaly it send answered mails from the list also back to the list... don't know why it does that by your mail > On Wed, Aug 12, 2009 at 10:52:24PM +0200, Vinzenz Hersche wrote: > > Am Mittwoch, 12. August 2009 22.38:30 schrieben Sie: > > > On Wed, Aug 12, 2009 at 10:27:21PM +0200, Vinzenz Hersche wrote: > > > > argh... :s > > > > mmh, i think, it could work, if more then the half community would > > > > join this and wrote a letter (with real paper, for this, there isn't > > > > a spamfilter...:) ) > > > > > > Did something like that ever worked? :( > > > > yeah. principe of petition, works in switzerland as democratic action and > > sometimes also on companis > > I can't see how it can work on atheros here. I'd prefer finding inside > contacts to understand what's going on about it and how much it would cost > for them to do anything. > i think, if we are "loud" enough, it could work (also with press.. or do you belive, atheros wants a image-damage for bad quality?), but also a inside- contact would be great. why not both? > > > > and one more technicaly idea; i read about the driver from openwrt. > > > > it works realy good, as i know... > > > > > > It's the same driver without any tweaks AFAIK. > > > > mmh, i just shortly read about it and i think, it must works good > > (because it's a router-sw), but may it's because of kernel 2.6.30... > > I guess it's exactly the same. .30 doesn't change anything about it. > ok, so may i'm wrong. i like hope.. :) > > > > as last of ideas: how much are about 100-200 pieces of a > > > > openmoko-compatible wlan-chip with a good quality? > > > > > > I'm yet to find any. > > > > cool. may it's could be a communitywork... which are the criterias? > > Well, it depends. If you want a ready-to-use module probably it's just > impossible. If you're ready to design PCB for some chip among with RF > components, then SDIO support and low power and size would be the main > requirements. > phu, ok, i must learn there something.. but it's good to know.. > > and at the end; may someone could build extensions with chips from > > gizmoforyou as example... > > I'm not an appropriate person to answer this qustion, you should have CC'd > the list. yeah, i just say this for future.. because of no edge-support.. with these open components from openmoko, we could integrate new components.. but this is also on movement, i think (openhw-alliance..) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Vikas Saurabh writes: >> 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)? > > Its available in SHR-U repo... And mrmoku just confirmed it'll be included in the image by default. :) -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
"arne anka" writes: >> to use the method described at FSO_Resources wiki page, then the bug >> doesn't surface. > > at least the page mentioned (http://wiki.openmoko.org/wiki/FSO_Resources, > i guess, but due to the plethora of wikis out there, "wiki page" might > refer to soemthing totally different) does not mention wifi issues or > "workaround" in any way. I assume default wiki is wiki.openmoko.org, sorry for being unclear. Here's a quote from the page you mentioned: " Especially recommended for WiFi since due to the bugs in the firmware and the driver full power-cycle of the module is often advantageous. Example command (works for open, WEP and WPA/WPA2 networks, automatically determining the network it can connect to, just add all the networks you use to the config): fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf " > 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. :( > 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. > 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. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> 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)? Its available in SHR-U repo...And since the bitbake is already there in the svn[1], I think the distributions should go ahead and include it...iirc, FSO is no longer in distribution business --Vikas 1 - http://noko.svn.sourceforge.net/viewvc/noko/trunk/fsoraw/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
> to use the method described at FSO_Resources wiki page, then the bug > doesn't surface. that sentence has been repeated several times now, and yet -- i don't really understand what exactly it means. at least the page mentioned (http://wiki.openmoko.org/wiki/FSO_Resources, i guess, but due to the plethora of wikis out there, "wiki page" might refer to soemthing totally different) does not mention wifi issues or "workaround" in any way. are you speaking about mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf 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)? 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 ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Vinzenz Hersche writes: > ok, them may we should write all mails, or better real letters to atheros.. > they made the chip, so they should fix these fucking things. if they sell > something, they have to make it working! Well, imagine they sold about 20k modules to OM. Do you think they care about it?.. I wished they did. You might not know about it but Werner's already contacted them and they even confirmed some firmware bugs. No action from their side followed and unlikely to follow. Probably if you have some inside contacts it can work out but otherwise i can't see any chances. > 2.6.29 kernel workaround > On OM 2.6.29 kernels wifi is broken, software putting down the interface > (e.g. > wpa supplicant in some cases) will break ar6000 module. A workaround has to > be > implemented and activable in the configuration file. It's not yet fixed but i hope it'll be fixed soon. The workaround is to use the method described at FSO_Resources wiki page, then the bug doesn't surface. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Am Mittwoch, 12. August 2009 21.51:04 schrieben Sie: > Vinzenz Hersche writes: > > Am Mittwoch, 12. August 2009 10.53:43 schrieb Paul Fertser: > >> Yogiz writes: > >> > I hope it is. I'd really want to finally see the wifi driver > >> > supporting Master mode (Access point). As far as I understand, it's > >> > fully possible to implement it. > >> > >> You might have as well looked at the commit log and loose all the > >> hope. If you're talking about ar6000 driver then there're no chances > >> it will support master (or monitor) mode ever. I don't see why you > >> think it might be possible. > > > > then please help me someone to learn the necessary-things about > > kernel-hacking (i know, it's a lot of work!) to fix this bugs in > > wifi? > > I tell you the most nasty bugs are in firmware. Which we don't have > sources for and don't know a way to update anyway. Blame Atheros. > > > i hope, the kernel-hackers who written the driver wakes up and fix > > this soon. > > Unlikely. Originally written by Atheros. > > > bad from fic... > > Openmoko Inc. is not FIC! And OM can't be held responsible for > Atheros's fuck ups. ok, them may we should write all mails, or better real letters to atheros.. they made the chip, so they should fix these fucking things. if they sell something, they have to make it working! but i also find something from the nwa-article in openmoko-wiki... 2.6.29 kernel workaround On OM 2.6.29 kernels wifi is broken, software putting down the interface (e.g. wpa supplicant in some cases) will break ar6000 module. A workaround has to be implemented and activable in the configuration file. is this now up2date-thing or are there workarounds? because if not, how it works with kernel 2.6.30? who would help to write atheros? hope, i'm not alone with the wish of a working wireless.. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Vinzenz Hersche writes: > Am Mittwoch, 12. August 2009 10.53:43 schrieb Paul Fertser: >> Yogiz writes: >> > I hope it is. I'd really want to finally see the wifi driver supporting >> > Master mode (Access point). As far as I understand, it's fully possible >> > to implement it. >> >> You might have as well looked at the commit log and loose all the >> hope. If you're talking about ar6000 driver then there're no chances >> it will support master (or monitor) mode ever. I don't see why you >> think it might be possible. > > then please help me someone to learn the necessary-things about > kernel-hacking > (i know, it's a lot of work!) to fix this bugs in wifi? I tell you the most nasty bugs are in firmware. Which we don't have sources for and don't know a way to update anyway. Blame Atheros. > i hope, the kernel-hackers who written the driver wakes up and fix > this soon. Unlikely. Originally written by Atheros. > bad from fic... Openmoko Inc. is not FIC! And OM can't be held responsible for Atheros's fuck ups. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Am Mittwoch, 12. August 2009 10.53:43 schrieb Paul Fertser: > Yogiz writes: > > I hope it is. I'd really want to finally see the wifi driver supporting > > Master mode (Access point). As far as I understand, it's fully possible > > to implement it. > > You might have as well looked at the commit log and loose all the > hope. If you're talking about ar6000 driver then there're no chances > it will support master (or monitor) mode ever. I don't see why you > think it might be possible. then please help me someone to learn the necessary-things about kernel-hacking (i know, it's a lot of work!) to fix this bugs in wifi? i hope, the kernel-hackers who written the driver wakes up and fix this soon. but as it seem, they like it more to sleep :( bad from fic... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Yogiz writes: > I hope it is. I'd really want to finally see the wifi driver supporting > Master mode (Access point). As far as I understand, it's fully possible > to implement it. You might have as well looked at the commit log and loose all the hope. If you're talking about ar6000 driver then there're no chances it will support master (or monitor) mode ever. I don't see why you think it might be possible. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
I hope it is. I'd really want to finally see the wifi driver supporting Master mode (Access point). As far as I understand, it's fully possible to implement it. On Wed, 12 Aug 2009 00:42:57 +0200 Vinzenz Hersche wrote: > hello list, > > i just want to ask if we could hope for a good working wifi-driver... > i use it many times and sometimes it does work, sometimes not. i > think, if this would working, it's a great step forward, because > there are applications to connect, browser, sync-tools, etc, but this > isn't very flexible, if we have to connect over usb i think. > > i read in a post, it works great in the openwrt-distro. is it > possible to merge it? > > if someone gave me a instruction, i would try it self, but i never > developed somethi > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
Am Mittwoch, 12. August 2009 00.42:57 schrieb Vinzenz Hersche: > hello list, > > i just want to ask if we could hope for a good working wifi-driver... > i use it many times and sometimes it does work, sometimes not. i think, if > this would working, it's a great step forward, because there are > applications to connect, browser, sync-tools, etc, but this isn't very > flexible, if we have to connect over usb i think. > > i read in a post, it works great in the openwrt-distro. is it possible to > merge it? > > if someone gave me a instruction, i would try it self, but i never > developed somethi > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community something in the kernel.. so i don't know how.. would be great, if there would be a moving. and i'm sorry for the strange mail, i was pressing send without reconize.. :s greets ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
is wifi-driver developed anymore?
hello list, i just want to ask if we could hope for a good working wifi-driver... i use it many times and sometimes it does work, sometimes not. i think, if this would working, it's a great step forward, because there are applications to connect, browser, sync-tools, etc, but this isn't very flexible, if we have to connect over usb i think. i read in a post, it works great in the openwrt-distro. is it possible to merge it? if someone gave me a instruction, i would try it self, but i never developed somethi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
