Ronald G Minnich <[EMAIL PROTECTED]> writes:
> On 21 Jun 2001, Eric W. Biederman wrote:
>
> > O.k. This explains the disconnect. Except for test setups, my common
> > case is to boot a second kernel from the one in flash.
>
> ah ha!
>
> > I hate to encourage using the kernel in flash as your primary kernel
> > as that encourages reflashing it. Unless you have a good fallback
> > booter reflashing the kernel in flash is dangerous.
>
> ok, I'll buy it, you're right. It's just that I have gotten so spoiled by
> booting from the one in flash ...
For a single function machine, (most embedded setups) we still
need to support using the kernel in flash. But that is very different
from a general purpose machine where there are reasons to upgrade
your kernel relatively often.
> Now that I understand what you're up to I can go with that.
>
> Where do you put the cramfs image with nbc? bundled with kernel image?
> seperate flash segment?
Well actually I've been generating a romfs image, and putting that in
an initrd that I bundle with the kernel with mkelfImage. It makes
the testing simpler. As I can put the setup on a floppy, in flash,
or boot it over the network. The script to generate it all is
in nbc-1.4.tar.gz.
I don't have any problems with adding an mtd driver to the kernel and
using cramfs, or jffs, or whatever. I designed the basic setup before
I had figured out about the mtd drivers, and with a truly small
boot image. With only the one tiny program in the fs it hasn't
presented a problem to be on a ramdisk.
I can burn 16K on a ramdisk even on my Timex Sinclair. :)
Eric
