This is the mail archive of the
mailing list for the eCos project.
Re: NAND review
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Ross Younger <wry at ecoscentric dot com>
- Cc: Simon Kallweit <simon dot kallweit at intefo dot ch>, "ecos-devel at ecos dot sourceware dot org" <ecos-devel at ecos dot sourceware dot org>
- Date: Tue, 19 May 2009 16:17:10 +0200
- Subject: Re: NAND review
- References: <4A126D59.email@example.com> <4A12B877.firstname.lastname@example.org>
> The partition definition is necessarily platform-specific, so doesn't fit
> anywhere else.
I simply don't get this.
Take a case i recently had with a NOR based system. I had a linux
kernel bug i had to trace down. So that i had human readable kernel
opps information, i rebuilt the kernel to include debug symbols. The
resulting kernel was too big to fit in the space allocated to it. So i
used redboot fis to zap both the root filesystem and the space holding
the kernel. I recreated the kernel partition a bit bigger and made the
root filesystem a bit smaller. I then installed the new kernel and the
root filesystem. I then had a booting system with opps with symbols,
not hex addresses.
At no point did i need to edit the HAL, rebuild and install a new
redboot. Why should NAND be different? Why cannot this partition
information be configured by redboot? Why must it be platform