gta02a5 prototype #30 brief review

Michael 'Mickey' Lauer mickey at
Wed Feb 27 16:10:09 CET 2008

On Wednesday 27 February 2008 16:02:10 Andy Green wrote:
> >>> * Wifi module works ok, but has some quirks. First, reception was not
> >>> that good, second, there are some driver problems with the wireless
> >>> extensions not being fully supported. you can't set the channel in
> >>> ad-hoc mode, link quality has bogus values (x/y, x >= y), when you scan
> >>> and there is nothing found, iwlist eth0 scan hangs with:
> >>>     eth0      Failed to read scan data : Resource temporarily
> >>> unavailable kernel says:
> >>>   AR6000 scan complete: 0
> >>>   ar6000_ioctl_giwscan(): data length 0
> >>>   [repeated 20 times]
> >>
> >> You must have the "89" firmware on your module for good operation.
> >
> > Which I have.
> Hum I was earlier today doing a scan OK, I saw Willie do a scan OK, I
> don't think it is epidemic whatever it is.

Well, please read again, apart from the bogus link quality and channel setting 
problem, iwlist eth0 scan only starts with that "ar6000_ioctl_giwscan(): data 
length 0" when there is no network found at all.

> On the previous firmware I 
> was able to associate well to my WPA network at home, although after
> some 10MB of transfer it blew chunks.

Saemo, can you comment on the debug message I attached to the other mail.

> > I see. However we should support at least the same level of telemetry
> > with the dumb batteries that we had in GTA01.
> If there's no date attached to it, fine, because it isn't exactly a
> blocker: we don't ship with those batteries.


> >> BATTFULL is fine it is an event from the standalone charger state
> >> machine that it sees it should stop charging because the battery is
> >> acting done.  It keeps topping the thing up at (long) intervals and will
> >> repeat it ongoing, but it is accurate.
> >
> > Excellent, we could not sense that in GTA01.
> It's just we used the pcf50633, it deals with all that.



More information about the openmoko-devel mailing list