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
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 firmwar
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
__
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.o
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
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
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
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
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
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/
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 t
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 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
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: /us
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.fre
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.fre
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
or
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.freesma
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
> >
"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
> 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 th
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 pow
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."
> >>
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/
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 i
>> 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 nev
> 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/han
> 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
"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
>> 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
"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 ca
> 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
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, Vinze
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 (
"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 di
> 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
> 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
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 ab
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 understan
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 ha
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 l
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 t
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 wif
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
> ap
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 fle
45 matches
Mail list logo
