Re: More than 7 partitions on the SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Il giorno lun, 09/03/2009 alle 23.48 +0200, Timo Juhani Lindfors ha | scritto: | Pietro \m0nt0\ Montorfano mont...@gmail.com writes: | Sooo, how it's that possible?? Why can't we simply patch the driver | which make the mmcblk device to let us create all the devices? | drivers/mmc/block.c has the limit: | | /* | * max 8 partitions per card | */ | #define MMC_SHIFT 3 | #define MMC_NUM_MINORS (256 MMC_SHIFT) | | Feel free to change but I doubt this will be accepted upstream. | | Well this could be a solution, openmoko may compile that (mmcblk) as a | module (need to verify that) and we or I can provide an opk that I don't think this will happen in order to scratch this pretty unusual itch. One way you can solve it for yourself is by rewriting (with dd) the first sector that contains the partition table and rebooting. So you can have two views on to the rest of the storage exposing just the partitions you want in each view. That'd get you 14 partitions and the ability to share eg /home between the two views and so all OSes. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm2D0UACgkQOjLpvpq7dMqzsACfWLdYbmGna8SJCtjbXcZBDymz nXEAoIWexd4ybdCAL0f1HeE/FhtgQTMK =hECL -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
rework
hi, i was lucky enough to get someone to perform the gsm buzz rework. i find the images used in the http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf quite rather _small_ therefore please find some of my pictures done via microscope here: http://vanous.penguin.cz/files/om/SOP/ Please feel free to use them to improve your manual. Also, we found that placing the 100uF cap according to the manual is rather strange and could cause problems in future - so we placed the cap in a way that is will be soldered to the PCB on both ends, making it hold really tight (that particular picture is somewhat blurry) We didn't have 2k2 in 0402 size so we used 2x 80Ohm in series (we just built a A shape with them). The fix works - done on two units, one showed gsm buzz before and now it's gone. Some of the other pictures show D4301, D4302, as under the microscope we found one of them damaged from manufacturing - placing the cover - something om might watch for. cheers petr ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: More than 7 partitions on the SD
2009/3/10 Pietro m0nt0 Montorfano mont...@gmail.com: Il giorno lun, 09/03/2009 alle 23.48 +0200, Timo Juhani Lindfors ha scritto: Pietro \m0nt0\ Montorfano mont...@gmail.com writes: Sooo, how it's that possible?? Why can't we simply patch the driver which make the mmcblk device to let us create all the devices? drivers/mmc/block.c has the limit: /* * max 8 partitions per card */ #define MMC_SHIFT 3 #define MMC_NUM_MINORS (256 MMC_SHIFT) ... I'm a lazy boy so i really want to have all the distro on tha uSD, also some testing version and so on ;D I'll try to make some changes to that driver.. If you set MMC_SHIFT to 4, you'll get up to 16 partitions per card, but otoh you reduce the number of minor devices that this driver can handle. It's better to simply set MMC_NUM_MINORS to the number of minors you'd like (64?) instead of the 256 MMC_SHIFT. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: wpa_supplicant not dettecting association?
On Friday 06 March 2009 06:40:29 you wrote: 2009/3/5 Daniel Benoy dan...@benoy.name: I'm setting up roaming. For roaming you need different directives in /etc/network/interfaces and an additional program (ifplugd). I made a few tries in the old shr-testing with not much success so far. I'll try again when I'm done flashing and configuring the new shr-testing with 2.6.28 kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ifplugd isn't necessary if you're using wpa_supplicant. -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] WSOD on resume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I've just flashed Qi, 2.6.28 and FSO 5.1. Is there a git hash associated with this 2.6.28 kernel at all? | When the FR resumes, the screen goes white and then slowly fades to black. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm2hiMACgkQOjLpvpq7dMqFjwCeNwqA99ZSNubgdg/X9r0alqnc rE0AnRr3cSdEFQJHkJgAVaV/QmoaL0IC =KGWA -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] WSOD on resume
when speaking of wsod i just wanna say - when i play with my menu kernel + initrd image which is rather big (5-7MB), there are occasions where i get wsod all the time after boot (i used to suffer it a lot during normal operation but not anymore after Andy's fixes). I can correct this [only] by regenerating and reflashing my kernel image (./build GTA02; dfu-...). I could not see any pattern, unfortunately. I also don't have any of the bad kernel images anymore, but when i hit on one again, i can keep it... - could this be kernel size related somehow? -- Petr ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] WSOD on resume
2009/3/10 Andy Green a...@openmoko.com: uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin Well it's from Jan 5th. If you're feeling adventurous (you can back out using that uImage anyway) try this kernel http://people.openmoko.org/andy/uImage-moredrivers-GTA02_andy-tracking-15ca3dafb2662db4.bin That fixes it for me! Thanks. It gives me a few error messages on boot. Would you like me to post them? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
