From: Ben Nizette Date: Wed, 03 Sep 2008 08:07:57 +1000 Subject: [U-Boot] [PATCH 0/6] ATSTK1000 LCD panel support In-Reply-To: <20080902140903.7ffad080@hskinnemo-gx745.norway.atmel.com> References: <1220347254-13127-1-git-send-email-haavard.skinnemoen@atmel.com> <6B5648EA2E2C2D42AF2FF7691522AD92417D45@wpr01.wprmedical.local> <20080902115419.7e18add1@hskinnemo-gx745.norway.atmel.com> <6B5648EA2E2C2D42AF2FF7691522AD92417D4B@wpr01.wprmedical.local> <20080902140903.7ffad080@hskinnemo-gx745.norway.atmel.com> Message-ID: <1220393277.9531.34.camel@moss.renham> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, 2008-09-02 at 14:09 +0200, Haavard Skinnemoen wrote: > Right. I was thinking maybe we could extend the boot protocol to pass > partitioning information from u-boot to the kernel -- that should make > it possible to run the same kernel on boards with different flash > layout as long as the in-flash u-boot is consistent with the flash > layout. If we do end up with libfdt on avr32 then we solve our problems here too, we can encapsulate this partitioning in the fdt image. But, as I understand it, that involves not only the actual libfdt support but making all avr32 driver nice and OF compatible. At least, if we want the fdt support to be _useful_ then that needs to happen (CMIIW). > > One problem this doesn't solve is that if you load an older kernel > which doesn't understand the extended boot protocol, it will keep using > the old flash layout. Doesn't the MTD system have facility to override partitioning information from the boot arguments? If so then any big u-boots can just ship with such a clause in their default bootargs, job done. Have to look in to that... --Ben.