> 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? Co
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 (si
-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 meas
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
On Wed, July 23, 2008 1:42 am, Alexey Feldgendler wrote:
> 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/checkpa
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
ti, 2008-07-22 kello 17:01 +0200, Alexey Feldgendler kirjoitti:
> On Tue, 22 Jul 2008 16:25:45 +0200, Andy Green <[EMAIL PROTECTED]> wrote:
> > static int sd_drive;
>
> This doesn't seem like zero initialization to me.
Static is initialized to zero. But indeed, I too noticed this from the
patch,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Tue, 22 Jul 2008 16:25:45 +0200, Andy Green <[EMAIL PROTECTED]> wrote:
|
|>
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2
|
|> static int sd_drive;
|
| This
On Tue, 22 Jul 2008 16:25:45 +0200, Andy Green <[EMAIL PROTECTED]> wrote:
> http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=66a83c97c4545ce4f07e0d90998f906fae49caf2
> static int sd_drive;
This doesn't seem like zero initialization to me.
--
Alexey Feldgendler <[EMAIL PROTECTED]>
[ICQ: 11
-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
-BE
-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 t
-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
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
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
> > 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 wil
Hi
On Tue, Jul 22, 2008 at 2:52 PM, arne anka <[EMAIL PROTECTED]> wrote:
>>> 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
>> 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
Hi
On Tue, Jul 22, 2008 at 2:29 PM, arne anka <[EMAIL PROTECTED]> wrote:
>> 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 yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
> 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
-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:/
> 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 workin
-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 expla
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 t
> 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 devel
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 al
-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
> 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
-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
| m
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.
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=1d04
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 setting
-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
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=1d04b142ffeaa15129f04
-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
35 matches
Mail list logo
