This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
RFC: extending (reserved)
- From: liberty at embeddedx86 dot com
- To: ecos-devel at sources dot redhat dot com
- Date: Wed, 15 Dec 2004 02:38:09 -0700 (MST)
- Subject: RFC: extending (reserved)
I'm requesting comments on extending CYGOPT_REDBOOT_FIS_RESERVED_BASE. As
it now stands, it reserves a generic portion of the flash. I'd like to
extend it and add the infrastructure to have multiple descriptive areas
reserved, such as "bootrom", "OS", etc..all machine specific.
I have two goals in mind:
1) multiple fis entries for reserved areas for a board, enjoying the
protection mechanism that "reserved" and "RedBoot" enjoy
2) simplify board ports to Linux.
On point 1, our platform needs guaranteed space for our BootROM and jffs2
image. An fis list shows them globbed together rather non-descriptively
with
(reserved) 0x60000000 0x60000000 0x00620000 0x0...
RedBoot 0x60620000 0x60620000 0x00040000 0x0...
etc. etc
I'd like to see them as
bootrom 0x60000000 0x60000000 0x00020000 0x0...
jffs2 0x60020000 0x60020000 0x00600000 0x0..
RedBoot 0x60620000 0x60620000 0x00040000 0x0..
this leads to point 2. We now have to create special
linux/drivers/mtd/maps files for our boards, though the physmap.c file
should work. Unfortuantely, we can't get access to the jffs2 image or the
bootrom section. I'd rather just let physmap.c pick up the various
partitions by reading the redboot fis entries.
What do you guys think? Is this just a bonker idea, or is it something
usefull?