On Sat, 12 Jul 2008, RHS Linux User wrote:
> If I understand your point about the 3rd option?
>
> 1. The driver(s) could either be in the kernel,
>
> 2. In the greater kernel image (flash chip) as drivers loaded after
> kernel boot.
>
> 3. On some removeable device (USB or whatever).
>
> If the drivers are capable of being loaded by the kernel, then they
> could be either in 2 or 3.
>
> Except that the drivers necessary to "mount" or make available the
> device of #3 (USB or whatever), "must" reside in 2. These drivers could be
> either linked statically to the particular kernel image or not.
>
>
> There is one additional point that is probably relevant.
>
> The boot kernel could be replaced by a kernel and filesystem provided
> by the USB or whatever device.
>
> IMHO getting this sort of KERNEL-PIVOT operation really working would
> be the best of all. The boot kernel would only be used for boot and debug
> and a "real" kernel could run "real" applications on the USB. The boot
> kernel could even become a "task" running under the new kernel.
If your platform supports kexec, you can boot a new kernel from the boot
kernel.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
