Re: [maemo-developers] initfs hacking questions
Eero Tamminen wrote: IMHO best would be to re-create the initfs partition image and flash it. Then there's no need for JFFS2 garbage collecting. :-) I would like to store last chosed rootfs in some config file there so it would be nice to find out if it works or not. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] initfs hacking questions
Hi, > BTW when editing /linuxrc multiple times it happened to me that I still > had 124 blocks free and could remove files but creating/modifying file > produced 'no space on device'. Looks like some trouble with jffs2 > garbage collecting. This is strange. I wonder whether reboot may fix > this? Unfortunately the file I successfully deleted was /linuxrc so I > had to reflash. IMHO best would be to re-create the initfs partition image and flash it. Then there's no need for JFFS2 garbage collecting. :-) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] initfs hacking questions
Devesh Kothari wrote: Can I distribute hacked initfs? If not, is binary patch OK? I am not a legal expert, but please read the EULA (End user license agreement). I would be pretty surprise if they would let you do so :) Devesh I am not a legal expert too so reading EULA is probably waste of time :-) But anyway I will put instructions how to rebuild it somewhere but release also binary diff and wait for Nokia lawyers to ask me to remove it. IMO binary diff is not considered as breaking "You may not copy, distribute, or make derivative works of the Software". In theory it should contain only my pieces of software. So far I have stripped initfs with one extra uclibc binary to check which key is pressed and shell stript to show onscreen menu. It still boots fine when no key is pressed :) As for the uclibc toolchain it was the one without soft floats. I'm still not sure whether I should store last rootfs setting with cal-tool in config partition or better write it to file in initfs filesystem (mtd3, jffs2) or somewhere else. BTW when editing /linuxrc multiple times it happened to me that I still had 124 blocks free and could remove files but creating/modifying file produced 'no space on device'. Looks like some trouble with jffs2 garbage collecting. This is strange. I wonder whether reboot may fix this? Unfortunately the file I successfully deleted was /linuxrc so I had to reflash. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] initfs hacking questions
ext Frantisek Dufka wrote: > Hello, > > recently I tried to modify initfs to allow dual booting and got some > questions: > > Is there a way to get code of pressed HW key in /linuxrc script? There > is command that waits for keypress. There is also something is sysfs > for detecting battery door, shell, headphone jack state but nothing > simple for keys. Anything I missed or do I need to compile my own > executable? > > Which scratchbox uclibc toolchain should I use? There are two ones here > http://scratchbox.org/download/files/sbox-releases/0.9.8/tarball/ > sf (softfloats) and non-sf. > > What exactly is testserver? initfs is full in IT2006 so I need to > delete something. I deleted testserver and its shared libraries and > device seems to boot. Is this needed for device operation or it is > really for factory testing or something like that so it never gets > executed automatically on boot. How do I run those test anyway? > > Can I distribute hacked initfs? If not, is binary patch OK? > I am not a legal expert, but please read the EULA (End user license agreement). I would be pretty surprise if they would let you do so :) Devesh > Which functionality I loose when dsme is not executed from /linuxrc > (battery charging?) > > Is is a good idea to use cal-tool frequently (i.e on each boot) to set > various flags (root device,..)? This get stored to flash, how it is > with wear leveling of config partition? > > Thanks for any answers. > > Frantisek > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] initfs hacking questions
On Fri, 2006-07-14 at 09:01 +0200, ext Frantisek Dufka wrote: > Hello, Hi, I'll reply only to those points I'm 100% sure of, sorry for the incomplete answer. Probabaly Devesh can provide some info on the legal side. > recently I tried to modify initfs to allow dual booting and got some > questions: > > Is there a way to get code of pressed HW key in /linuxrc script? There > is command that waits for keypress. There is also something is sysfs > for detecting battery door, shell, headphone jack state but nothing > simple for keys. Anything I missed or do I need to compile my own > executable? > > Which scratchbox uclibc toolchain should I use? There are two ones here > http://scratchbox.org/download/files/sbox-releases/0.9.8/tarball/ > sf (softfloats) and non-sf. > > What exactly is testserver? initfs is full in IT2006 so I need to delete > something. I deleted testserver and its shared libraries and device > seems to boot. Is this needed for device operation or it is really for > factory testing or something like that so it never gets executed > automatically on boot. Only for test mode and factory. And you are right: it's a good target to free space =) > How do I run those test anyway? > > Can I distribute hacked initfs? If not, is binary patch OK? > > Which functionality I loose when dsme is not executed from /linuxrc > (battery charging?) WDs kicking, sw watchdog for processes, battery charging, device mode control and backlighting(almost certainly). > Is is a good idea to use cal-tool frequently (i.e on each boot) to set > various flags (root device,..)? This get stored to flash, how it is with > wear leveling of config partition? > > Thanks for any answers. > > Frantisek > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers -- Cheers, Igor Igor Stoppa (Nokia M - OSSO / Tampere) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
