#openmoko
28 December 2007
Total 5 pages. You are browsing page 5/5.
First :: Prev :: [...] [1] [2] [3] [4] [5] :: Next :: Last
20:24 <****> Maybe it updates after a minute or so. I think.
20:24 <****> I probably should retry, so that I can trick around it.
20:24 <****> that is weird
20:24 <****> you would think they would have to do that explicitly
20:25 <****> What?
20:27 <****> I mean, it seems they would have to go out of their way to do the wrong thing
20:27 <****> to make it not update when you're not moving
20:30 <****> current position) to change like mad.
20:30 <****> true...
20:30 <****> but it seems easy enough to allow for error on the client side
20:30 <****> I'd rather be able to get access to the raw data, and then have another api that fudges it for practical reasons
20:30 <****> The solution is letting the consumer choose.
20:31 <****> Yeah, or that.
20:31 <****> The above is my personal guess, why the thing acts in that way.
20:32 <****> makes sense
20:33 <****> Also it has some "smoothing": If you drive with 10km/h north, and then abruptly drive west, the reported position still goes on north for a few secs and then does a smooth quarter circle like thing.
20:37 <****> Which also makes some sense for car usage. For car usage you usually don't drive like that mad, you drive smooth, and so it makes sense to smooth out the noisy data.
20:37 <****> Yeah, but again I would rather have a low level & high level api
20:38 <****> sometimes I know better than they do what the output means, and maybe I want to put a bunch of work into heuristic algorithms that just do a better job than they do
20:41 <****> Right, right.
20:41 <****> Just that API doesn't seem to exist.
20:42 <****> We were trying to reverse engineer the hardware, but I have to admit, other stuff attracted me more lately.
20:43 <****> The 02 hardware kind of bypasses that whole thing by just giving nmea data directly, doesn't it?
20:44 <****> I don't know exactly, what info has been released about 02.
20:44 <****> The driver for the 01 gives NMEA too, just it's "preprocessed".
20:44 <****> I thought I saw a comment on the wiki that the new gps puts out nmea directly
20:44 <****> the GPS chipset simply outputs NMEA in 02
20:45 <****> hey, on the 01, my mp3 player stutters
20:45 <****> Ahh, so it's official now.
20:46 <****> Should I just nice it, or is there some other technique I should be using?
20:46 <****> the ANTARIS supports other protocols too
20:46 <****> all of which are docummented, so it's pretty cool
20:46 <****> very cool!
20:47 <****> balrog-kun - :-)
20:48 <****> the manufacturer claim their other binary protocol is more efective and i think there's a c lib to parse it
20:48 <****> claims
20:48 <****> I guess, gpsd can talk it. ;)
20:48 <****> And yes, the binary protocols are usually better.
20:48 <****> I played a lot with the sirf3 binary stuff.
20:49 <****> Elrond: let me know if you ever re-start your Hammerhead reverse-engineering. I have some newer stuff that I haven't checked into the sphyrna repository yet.
20:49 <****> mmontour - Ahh, yeah. I also have some non-checked-in stuff. :-|
20:53 <****> Elrond: I plan to do some more Hammerhead work over the next few days. What sort of non-checked-in stuff do you have?
21:02 <****> mmontour - Mostly a pygtk frontend for plotting live data on te neo. ;)
21:02 <****> It's a quick and bad hack.
21:06 <****> is LaF0rge around? :-(
21:06 <****> who at 24c3 saw him or will see him?
21:09 <****> josch: Jeroen might
21:10 <****> Jeroen :)
21:10 <****> sounds dutch to me :)
21:10 <****> why Jeroen ?
21:12 <****> who is he?
21:12 <****> LarstiQ, ?
21:33 <****> josch_: because he is at the 24c3?
22:05 <****> I've indeed seen LaF0rge walking around yesterday
22:25 <****> Jeroen, yeah but.... okay well I will just pose my question here
22:26 <****> me and Obri have a problem with neo1973 gta01 hardware running non-openmoko - the tft seems to flicker just as the cpu is being used
22:26 <****> heavy flickering on high cpu use and low flickeriung on low use
22:26 <****> so... why?
22:26 <****> this is not just in X but also in framebuffer console
22:33 <****> if you've screwed up the divisor settings, the framebuffer will contend for memory bandwidth with the CPU I think
22:37 <****> josch_: 640x480 is consuming a lot of bandwith so you should not expect too much with high cpu use. Switch to QVGA mode, I expect it'll be better
22:39 <****> rtp, wohooo wait but openmoko also uses 640x480
22:49 <****> josch_: yeah, but afaik the 2410 is idle most of the time. If you have time, just compute the bandwith usage as explained in the 2410 um :)
22:52 <****> oh I don't have time ^^ but why does it work in openmoko and doesn't with normal xorg?
23:01 <****> josch_: I only play with the kernel. I've no idea how is configured userspace stuff, sorry
23:04 <****> rtp, :-) thx anyway ^^
23:28 <****> * * OM Bug 1149 has been created by andrew(AT)orospakr.ca
23:28 <****> * * Incoming calls work perfectly, but outgoing calls silently fail.
23:28 <****> * * http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1149
23:28 <****> that was the bug I was describing in here last night.
23:50 <****> Does anyone know how to contact Michael Shiloh?
23:50 <****> I need to ask about turnaround time for the modem firmware install on GTA01
23:51 <****> *crickets chirp*
--- Log closed Sat Dec 29 00:00:56 2007
Total 5 pages. You are browsing page 5/5.
First :: Prev :: [...] [1] [2] [3] [4] [5] :: Next :: Last