Thanks for the reply.<br><br>I see your point. I guess a better solution would be to create a boot loader the stays resident after the "main" OS is running, and can be called from that OS. That way the low-level drivers needed for booting could be maintained in only one place. The same could be true for the network stack (to support network boot). Unfortunately, AFAIK, that's not the strategy taken by Open Firmware, U-Boot or any other boot loader.<br>
<br>Would such a sharing approach have merit? Or is it an intellectual/technical dead-end.<br><br>[more comments after the quote]<br><br><div class="gmail_quote">On Tue, Jun 3, 2008 at 5:51 PM, Werner Almesberger <<a href="mailto:werner@openmoko.org">werner@openmoko.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">[ Processing mails accumulated during my vacation ... ]<br>
<div class="Ih2E3d"><br>
Dale Schumacher wrote:<br>
> Has anyone considered using Open Firmware [1] as a more capable bootloading<br>
> system?<br>
<br>
</div>Hmm, no. Much like u-boot, it tries to solve the problem that we<br>
want to have the functionality of a small operating system, but that<br>
we can't afford to actually have that operating system there.<br>
<br>
But we can :-)</blockquote><div><br>What do you mean? Are you thinking that the "real" OS would be kept directly in NAND/NOR flash?<br></div></div><br>