On Wed, Apr 11, 2001 at 09:59:20PM +0200, mazsi wrote:
> choosing which image to use as root from the ones sitting in the
> flash. (ROOT_DEV=MKDEV(MTD_BLOCK_MAJOR, ...) / setup_initrd(..., ....) )
>
> can you recommend a better way?
You can modify the initrd parameters at any stage before the ramdisk driver
is initialised, and you can change the root_dev any time before it is
mounted. This includes in an initcall()'d init routine, as long as it
is one of the first few called.
However, I'm not sure that putting all this type of stuff in the kernel
is really the right way to go - we're getting really bloated now, and its
starting to suck badly.
I'd like to see most of the information about the system going into the
kernel loaders where-ever possible and being passed into the kernel via
the defined interface, rather than having lots of things that people
get to edit in the kernel to suit their needs, and/or lots of dependencies
on the architecture number.
So, take this as a constructive plea to the SA1100 people - please reduce
the amount of machine specific stuff in the kernel initialisation.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/ / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
