My custom kernel configuration got just a little too
big too fit into the standard vmlinux flash partition without
compressing it. The uncompressed kernel image was
almost 2MB, the compressed (zImage) is only about .7MB.
Uncompressing the kernel adds only a fraction of a second
to the boot up time. I'm surprised that more develpers
don't opt for this approach.
This leaves a 1.3MB unused "hole" in the flash.
Can anyone suggest how best to merge extra space into the
(reserved) partition and thus increase the size
of the JFFS2 filesystem?
Redboot directly follows the (reserved) area.
So, my first thought was to simply shift
this partition 1.25MB up in the flash.
But, I could easily end up with an "bricked"
board if this fails.
What's involved in moving Redboot
(ie. changing its load address)
Is there a way to test a Redboot image
so that I have some fallback if it does not work?
Can RedBoot load itself? If so, how?
Is there a better way?
Any tips or pointers would be appreciated.
- brent
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|