FSO 2.6.28 usage report

Andy Green andy at openmoko.com
Mon Jan 12 14:54:01 CET 2009

Hash: SHA1

Somebody in the thread at some point said:

|> Yes I think this is genuine diagnostic about edge appearing on RX during
|> GPS wake.  I don't know what it means that it appears during transfer,
|> but I would hazard a guess it can be true.  A long time ago someone
|> reported in then Bugzilla that if they had the debug cable connected,
|> they found interruptions and garbage on their GPS NMEA stream.
| So you say that there might be hw problems with the uart on the soc?
Or a driver
| bug?

That report told that it only happened with debug flatcable and board
attached.  I can directly imagine that the glitch when we start GPS up
is legitimate and given that report maybe the other ones are too.  Maybe
if people are experiencing that, they can see if it is ever seen with
debug board disconnected to credit or discredit this theory.

| Whops, since when you have this other config? Never seen it before.

It was done on this list about a month ago.  I described then that I
mostly autogenerated it by shell parsing of stable packaging config to
extract what was modules and apply that frankenconfig-style to the
moredrivers one to end up with 2.6.28 with lots of modules.

| Well, this of course means we loking forward for more GTA01 support in
| battery driver comes to mind. :D

Oh it's not forgotten :-)  Balaji has gotten half the GTA02 pcf50633
driver upstream and is testing his uplevel of GTA01's pcf50606 on the
GTA01 Wolfgang mentioned.  So we can expect a refresh of the PMU guts
into regulator style same as pcf50633 has had now.  (But not literally
"battery driver", unlike GTA02 01 has no smart battery.)  This will make
another round of /sys breakage specific to GTA01 but that's OK considering.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list