Re: Reason for GPS problems found! / more patches
On Tuesday 22 July 2008 05:43, Simon Matthews wrote: So the fact you were OK at drive level 0 should mean are able to use SD card how you like without problems from SD_CLK to GPS any more. Surely the hardware and software 'fixes' can only be seen as a total fix if they make the SN (signal to noise ratio) of the GPS the same as if the SD card is not present. I would have thought that each of these modifications would improve the SN ratio but would not make it the same as not having the SD card present. I know it is hard but it would be nice to get some figures on how each of these modifications by themselves and together effect the SN ratio. It might turn out that the software clock drive solution by itself is as good as or better than adding the capacitor, and adding the capacitor does not improve the SN ratio any further once the clock drive mod is done, which would make it unnecessary. I haven't modded the hardware, but it do use the software fix. With the fix the GPS works great, I can't notice any difference with or without the SD card present. That is, as long as the SD card is idle, if you start hammering the card you will at least lose some precision. Inside my house I generally loose the fix when the SD card is stressed, not sure what will happen outside. But that's only when really hammering the card, incidental usage does not seem to affect the GPS performance in any way. AVee -- You know the great thing about TV? If something important happens anywhere at all in the world, no matter what time of the day or night, you can always change the channel. -- Jim Ignatowski ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Inside my house I generally loose the fix when the SD card is stressed, not sure what will happen outside. But that's only when really hammering the card, incidental usage does not seem to affect the GPS performance in any way. Could you elaborate on how did you exactly hammer the card? Copying a big file to/from the card? I should receive my Freerunner in the beginning of august and from what I heard from the distributors, the SD/GPS hw fix is included on it from the start. It would be nice to run a comparison test and see how big of a difference the fix makes in these conditions. Yogiz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Thanks for that Andy, There are some numbers here: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2 Could you tell me what exactly you are measuring, radiated power? and under what conditions. How was the noise floor measured. Thanks Simon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Thanks for that Andy, | | There are some numbers here: | | http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2 | | | Could you tell me what exactly you are measuring, radiated power? and | under what conditions. | | How was the noise floor measured. This information comes via apparently google-translated Chinese, what I believe was done is stick a probe on SD_CLK each time, noise floor there is when clock is not running, etc. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiG8ncACgkQOjLpvpq7dMpQJgCgiOYVg0SrS6YXVzKxb3+fhPN6 LvEAn3a82+sfmwc01U0u/oelVWKsgIgX =rYui -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | So the fact you were OK at drive level 0 should mean are able to use SD | card how you like without problems from SD_CLK to GPS any more. | | Surely the hardware and software 'fixes' can only be seen as a total fix | if they make the SN (signal to noise ratio) of the GPS the same as if | the SD card is not present. I would have thought that each of these | modifications would improve the SN ratio but would not make it the same | as not having the SD card present. | | I know it is hard but it would be nice to get some figures on how each | of these modifications by themselves and together effect the SN ratio. As far as it is understood, having the SD card in or not is not actually the issue... the problem has been that with an SD Card in we ran SD_CLK all the time, and this raises the noise at 1.5GHz where GSM works. There is a figure for the cap efficacy, it attenuates the crap coming from SD_CLK by 10dB. But of course stopping the clock does better, and changing the rise and fall time is also directly effective even when the clock does run. | It might turn out that the software clock drive solution by itself is as | good as or better than adding the capacitor, and adding the capacitor | does not improve the SN ratio any further once the clock drive mod is | done, which would make it unnecessary. That's the current thinking, this issue can be solved by kernel update and no rework. Basically we're then not running the clock most time anyway, and tests like the one in this thread (which ran the clock all the time) show that at drive strength 0 we talk to the card fine but do not perturb GPS significantly. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiFrX0ACgkQOjLpvpq7dMoe3wCdHokzAYHLaVcVoATXt13kfcAa GxUAn3kKze522PSZXpw4LVqxldJFb96k =Oc/x -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
On ti, 2008-07-22 at 11:43 +0800, Simon Matthews wrote: Surely the hardware and software 'fixes' can only be seen as a total fix if they make the SN (signal to noise ratio) of the GPS the same as if the SD card is not present. FWIW and IMAO, this definition of a total fix is impractical almost to the point of uselessness. There will always be some noise in a tightly packed product incorporating many high frequency sources. The question is if the noise is significant (as it seems to have originally been). Referring back a bit, it _is_ nice to hear though that the clock drive tuning can improve the situation noticably even with SD clock on, should probably give that a try myself one of these days. (Haven't tested GPS in a while now, but it _would_ be nice not to have to send my unit in for service :) Again, kudos to the team for a job well done on all fronts, sw and hw, with regard to this issue. -- Mikko Rauhala [EMAIL PROTECTED] University of Helsinki ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
So the fact you were OK at drive level 0 should mean are able to use SD card how you like without problems from SD_CLK to GPS any more. If at all possible, can someone who understands this explain it so we developers can add the hack/patch to our running Freerunners and continue development unimpeded by this issue any longer? Or do we just have to wait until the next image update or something? ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Hey Andy, will the patch be spread by opkg too? I did some updates, but the sd_card file still does not appear. Anything I missed? thx in advance Bastian On Mon, Jul 21, 2008 at 2:11 AM, Andy Green [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: | Thanks for this report, I went and looked and found I didn't take care | of the case where last packet transferred was not a bulk read packet: | that what happens on resume. I added a patch to stable branch that | should be out tomorrow hopefully and give the same SD_CLK performance | with or without resumes. | | Thanks for fixing it. I'll test it more once the new kernel build hits the | repos. Just a heads-up there is also another relevant patch on stable tonight. ~ It gives another interesting knob to twiddle about GPS performance. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 You can check if your kernel package has it tomorrow by looking for ~ cat /sys/module/glamo_mci/parameters/sd_drive if the file doesn't exist you don't have the patch in yet. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiD02gACgkQOjLpvpq7dMoQ8gCgj2Hbu5yh7mzPgclo66rbmn4m wqoAn0/TiHsJEJIoZ51Cs8eYArP449yn =3S3d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- -- spread the word ... see www.browsehappy.com ;o) Calvin: Weekends don't count unless you spend them doing something completely pointless. Join the Greater IBM Connection (http://www.xing.com/premiumgroup-6291.d26b7d) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | So the fact you were OK at drive level 0 should mean are able to use | SD | card how you like without problems from SD_CLK to GPS any more. | | | If at all possible, can someone who understands this explain it so we | developers can add the hack/patch to our running Freerunners and | continue development unimpeded by this issue any longer? Or do we | just have to wait until the next image update or something? I will change the default drive strength to 0 today, tomorrow's kernel should just work. The SD Card we ship anyway seems to work fine like that. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiFy/0ACgkQOjLpvpq7dMrCLQCfU0laYPbSmWELTc0JDkuekmNj T6wAoIBoNn+lpWWYD16KMYC9f3YevB/U =llOW -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
I will change the default drive strength to 0 today, tomorrow's kernel should just work. The SD Card we ship anyway seems to work fine like that. okay great, i'll keep an eye out for that update tomorrow and test it with my 8gig MicroSD card (kingston), which so far has been working very nicely. \and may i just add: its very nice to be back in the openmoko developer chair again .. having the freerunner for the last 24 hours has been a very big boon to my private development projects .. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hey Andy, | will the patch be spread by opkg too? | I did some updates, but the sd_card file still does not appear. | | Anything I missed? According to the filename, this uImage.bin has the patch in http://buildhost.openmoko.org/daily/freerunner/200807/20080722/uImage-2.6.24+git23+1d04b142ffeaa15129f046751f1366b0f0614f47-r0-om-gta02.bin Likewise, this package http://buildhost.openmoko.org/daily-feed/om-gta02/kernel-image-2.6.24_2.6.24+git23+1d04b142ffeaa15129f046751f1366b0f0614f47-r0_om-gta02.ipk has the right hash in for having the patch too. If they still don't have the /sys thing, something 'orrible has happened somewhere. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiF0cEACgkQOjLpvpq7dMolXgCdEmeIz0qxkeZEZvAatsyCYAo7 tLUAoJB27QpRa3lMFo54Q/5lM8YAFFUc =3nXL -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
According to the filename, this uImage.bin has the patch in http://buildhost.openmoko.org/daily/freerunner/200807/20080722/uImage-2.6.24+git23+1d04b142ffeaa15129f046751f1366b0f0614f47-r0-om-gta02.bin how did you tell? by looking at the md5sum? btw: why can't these packages not simply have a date in the name, maybe with a time, too? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
btw: why can't these packages not simply have a date in the name, maybe with a time, too? These signify which git tree/revision is built. The date is in the folder names containing it. doesn't help with opkg -- from looking at the package's name you cannot tell if your kernel is from today or two weeks old. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Surely the hardware and software 'fixes' can only be seen as a total fix if they make the SN (signal to noise ratio) of the GPS the same as if the SD card is not present. FWIW and IMAO, this definition of a total fix is impractical almost to the point of uselessness. There will always be some noise in a tightly packed product incorporating many high frequency sources. The question is if the noise is significant (as it seems to have originally been). Sorry i don't think i have made myself clear. What i meant is that each of the modifications has been claimed to be a fix, when i would think they are only an improvement. What i am trying to get at is to find which of the modifications gives the best improvement. I know it is difficult to quantify this but it would be nice to know that say the clock current drive decrease by itself improved the SN ratio by say 6dB, the capacitor mod by itself improved the SN by say 3dB, and combined the change was 6dB. If this was the case just the software mod would be necessary. If on the other hand the combined change was 9dB then both would be worthwhile. Again, kudos to the team for a job well done on all fronts, sw and hw, with regard to this issue. I agree with this. I find it very impressive that they can get three radio transmitters, four radio receivers, high speed electronics and audio working in such a small package without more problems, and probably done on a shoestring budget as well. Simon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Hi, So you mean the patch allowing to change the drive strength for SD, not the latest patch you committed about 2 hours ago which set default strength to 0 ? On Tue, Jul 22, 2008 at 14:41, Andy Green [EMAIL PROTECTED] wrote: Somebody in the thread at some point said: | According to the filename, this uImage.bin has the patch in | | http://buildhost.openmoko.org/daily/freerunner/200807/20080722/uImage-2.6.24+git23+1d04b142ffeaa15129f046751f1366b0f0614f47-r0-om-gta02.bin | ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Hi Andy, Can you do your voodoo so that this will install from opkg upgrade? Thanks, Vinc Duran user On Tue, Jul 22, 2008 at 6:01 AM, Andy Green [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | So the fact you were OK at drive level 0 should mean are able to use | SD | card how you like without problems from SD_CLK to GPS any more. | | | If at all possible, can someone who understands this explain it so we | developers can add the hack/patch to our running Freerunners and | continue development unimpeded by this issue any longer? Or do we | just have to wait until the next image update or something? I will change the default drive strength to 0 today, tomorrow's kernel should just work. The SD Card we ship anyway seems to work fine like that. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiFy/0ACgkQOjLpvpq7dMrCLQCfU0laYPbSmWELTc0JDkuekmNj T6wAoIBoNn+lpWWYD16KMYC9f3YevB/U =llOW -END PGP SIGNATURE- ___ 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: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I know it is difficult to quantify this but it would be nice to know | that say the clock current drive decrease by itself improved the SN | ratio by say 6dB, the capacitor mod by itself improved the SN by say | 3dB, and combined the change was 6dB. If this was the case just the | software mod would be necessary. If on the other hand the combined | change was 9dB then both would be worthwhile. There are some numbers here: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2 - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiF7ekACgkQOjLpvpq7dMrO1QCffFC9Yi13p++StrjrrfhYLcZd 3c8AoJIXpKWvb/qsxTCQOpi3mg+blXcG =ccYU -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | So you mean the patch allowing to change the drive strength for SD, | not the latest patch you committed about 2 hours ago which set default | strength to 0 ? Yes, the now older patch introduced the /sys things. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiF7jAACgkQOjLpvpq7dMow0QCfeykm0Z81BdgVY5zOfIachLs6 vhAAoIKFrtLbtUA8s2XQsiaCxsn/X0j5 =2ifJ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi Andy, | Can you do your voodoo so that this will install from opkg upgrade? That's someone else's voodoo, but it is the intention that it'll just turn up in packages after 24hrs or less. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiF7msACgkQOjLpvpq7dMruqACglQXUFWZibexvsQoMeapvFWkB rKwAni8O+4Rhu1g76FLCCjaj5LAOcqXj =+IOf -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
On Tue, 22 Jul 2008 17:34:58 +0200, Andy Green [EMAIL PROTECTED] wrote: I guess you're not a kernel coder... not only is the segment for these definitively zero at start of kernel, but it is an offence against ./scripts/checkpatch.pl to explicitly zero these things. It's strange to have a script that enforces a worse practice, even when you really can assume that the segment is zeroed. -- Alexey Feldgendler [EMAIL PROTECTED] [ICQ: 115226275] http://feldgendler.livejournal.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
On Mon, 21 Jul 2008 02:11:38 +0200, Andy Green [EMAIL PROTECTED] wrote: Just a heads-up there is also another relevant patch on stable tonight. ~ It gives another interesting knob to twiddle about GPS performance. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 What does “strength” mean in this context? Voltage? -- Alexey Feldgendler [EMAIL PROTECTED] [ICQ: 115226275] http://feldgendler.livejournal.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Mon, 21 Jul 2008 02:11:38 +0200, Andy Green [EMAIL PROTECTED] wrote: | | Just a heads-up there is also another relevant patch on stable tonight. | ~ It gives another interesting knob to twiddle about GPS performance. | | http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 | | What does “strength” mean in this context? Voltage? No, it will refer to the amount of current allowed to the drive the output transistors in the Glamo's SD-related IO cells. If they are starved of current, it affects the rise and fall time of the output, it is the sharpness of the edges that creates the higher frequency energy that makes trouble at 1.5GHz we suspect. Running at strength 0 worked fine here on the SD Card we ship and should significantly affect those high harmonics. I eyeballed the clock signal that results and it's not so degraded. Basically stopping the clock when idle attacks it the bulk of the time when we don't talk to the device and the strength setting attacks it even when we are talking to the SD Card. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiEPCYACgkQOjLpvpq7dMoPJQCdFrzIBw19ilHUDH595cfjGEqU WD4AnA0XBJT3W3bpq72gdtVcBjgcZTfH =Eplk -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
Andy Green wrote: Just a heads-up there is also another relevant patch on stable tonight. ~ It gives another interesting knob to twiddle about GPS performance. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 I did some tests with the new settings. My observations are based on the signal strength output in AGPS-UI. sd_idleclk=1 and sd_drive=2: The strength of the gps-signal rapidly goes down, then I loose the fix on my window. sd_idleclk=1 and sd_drive=0: I can't see a weakening of the gps-signal. Signal strength seems as good as with sd_idleclk=0. I copied some (big) files to and from the card, none were corrupted, all md5-sums were identical. I'm using a sandisk 4GB SDHC card. Thanks for the great work. -Chris ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
does it say what the two settings actually do? Scott Chris wrote: Andy Green wrote: Just a heads-up there is also another relevant patch on stable tonight. ~ It gives another interesting knob to twiddle about GPS performance. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 I did some tests with the new settings. My observations are based on the signal strength output in AGPS-UI. sd_idleclk=1 and sd_drive=2: The strength of the gps-signal rapidly goes down, then I loose the fix on my window. sd_idleclk=1 and sd_drive=0: I can't see a weakening of the gps-signal. Signal strength seems as good as with sd_idleclk=0. I copied some (big) files to and from the card, none were corrupted, all md5-sums were identical. I'm using a sandisk 4GB SDHC card. Thanks for the great work. -Chris ___ 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: Reason for GPS problems found! / more patches
look here: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 Scott Derrick wrote: does it say what the two settings actually do? Scott ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | sd_idleclk=1 and sd_drive=0: | I can't see a weakening of the gps-signal. Signal strength seems as good | as with sd_idleclk=0. | I copied some (big) files to and from the card, none were corrupted, all | md5-sums were identical. I'm using a sandisk 4GB SDHC card. Cool, thanks for the report. That was a tougher test than you might have thought, since sd_idleclk=1 keeps the SD Clock going all the time. ~ Normally you would leave sd_idleclk at default of 0 and stop the clock when no transfer. So the fact you were OK at drive level 0 should mean are able to use SD card how you like without problems from SD_CLK to GPS any more. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiE8SgACgkQOjLpvpq7dMoKIwCfba4dU+ZhkhCvE5E1clEhXZHE 6AQAoIYO4/nomPKkGN3GdGL47knTZzi2 =KFb/ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
So the fact you were OK at drive level 0 should mean are able to use SD card how you like without problems from SD_CLK to GPS any more. Surely the hardware and software 'fixes' can only be seen as a total fix if they make the SN (signal to noise ratio) of the GPS the same as if the SD card is not present. I would have thought that each of these modifications would improve the SN ratio but would not make it the same as not having the SD card present. I know it is hard but it would be nice to get some figures on how each of these modifications by themselves and together effect the SN ratio. It might turn out that the software clock drive solution by itself is as good as or better than adding the capacitor, and adding the capacitor does not improve the SN ratio any further once the clock drive mod is done, which would make it unnecessary. Simon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Reason for GPS problems found! / more patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: | Thanks for this report, I went and looked and found I didn't take care | of the case where last packet transferred was not a bulk read packet: | that what happens on resume. I added a patch to stable branch that | should be out tomorrow hopefully and give the same SD_CLK performance | with or without resumes. | | Thanks for fixing it. I'll test it more once the new kernel build hits the | repos. Just a heads-up there is also another relevant patch on stable tonight. ~ It gives another interesting knob to twiddle about GPS performance. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=1d04b142ffeaa15129f046751f1366b0f0614f47 You can check if your kernel package has it tomorrow by looking for ~ cat /sys/module/glamo_mci/parameters/sd_drive if the file doesn't exist you don't have the patch in yet. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiD02gACgkQOjLpvpq7dMoQ8gCgj2Hbu5yh7mzPgclo66rbmn4m wqoAn0/TiHsJEJIoZ51Cs8eYArP449yn =3S3d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
