Here is another interesting take on this problem, once booted into Linux
(from whatever means), can you access the NOR directly without having to
use the MTD interface?
Andrew
On Fri, 2007-08-10 at 10:48 -0400, Roberto Waltman wrote:
> Andy Ngo wrote:
> > ...
> > ... Why does the ramdisk.gz image have to be in RAM first; isn't the
> > kernel going to "uncompress" it to another part of RAM anyways; if so,
> > why can't it "uncompress" the ramdisk.gz directly from flash to RAM ...
> My answer is only an "educated guess", treat it accordingly. I assume
> that is to make the kernel and booting process more simple and
> consistent by dealing with one case only: ramdisk.gz is already in
> memory, expand it an use it from here.
>
> Otherwise the kernel would have to know how to directly handle any one
> of today's various memory architectures, plus anything the future may bring.
> For example, the ramdisk image could be stored in NOR FLASH chips,
> ("plain memory", address + data), NAND FLASH chips, (more of a block
> device, you provide commands and read/write blocks of data), I2C EEPROMS
> (read a bitstream), etc.
>
> It makes sense from a design perspective to have the bootloader, (that
> needs to be customized for a particular hardware platform anyhow,) take
> care of these hardware related details and provide a more a uniform
> environment for the kernel start-up.
>
>
> Roberto Waltman
>
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
