On 31 August 2010 19:15, Jakob <[email protected]> wrote: > On 8/4/10, Joachim Ott <[email protected]> wrote: >> On 3 August 2010 20:58, <[email protected]> wrote: >>> 03.08.2010 14:57, David Garabana Barro пишет: >>> >>>> It was related to uboot. >>>> I flashed qi, and now I get a fix after suspending with no problem. >>> >>> This is weird. >>> What u-boot have to do with gps or any other subsystem for that matter? >>> Are you sure about this? >> >> One difference between uboot and qi is that qi doesn't initialize the >> display. The problem with gps and suspending also occurs on my older >> image from June 28, with upgrades until today and 2.6.32.16. >> _______________________________________________ >> Shr-User mailing list >> [email protected] >> http://lists.shr-project.org/mailman/listinfo/shr-user >> > > Has anyone looked into this problem? > Still no gps after a suspend with uboot. Or is everyone using qi these days?
We must be the only two using u-boot. I suspend very seldom, maybe once in a month and therefore the gps failure doesn't appear on my FR (and I don't use gps very much currently). But it still occurs with 2.6.32.21. I'm trying to find out again. I can't really believe that the bootloader make such a difference. Can someone with Qi show me the value of his /proc/cmdline? With my u-boot it is this: rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs) _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
