> O.k. So redboot doesn't have code any chipset specific code yet?
> I'm curious how much did redboot need to change to be able to
> run under linuxBIOS? To build the ebi?
No, it's all very generic.
When I first started with RedBoot, I was stumbling over it's memory
placement because the ROM configuration method that seemed to make sence
to me at the time wanted to load at 0x2000, and your elf loader didn't
like that. However, against the documentation, they had a configuration
method for RAM loading (for booting RedBoot from RedBoot), which used a
more hospitable 0x108000. That worked fine right away, save turning off
such features as video console, and of course setting serial baud to
115200. Those changes are all made in the configuration script i provided.
> Looks interesting. I don't know if it is a final solution but
> redboot looks small enough that it could easily make a good
> playground for testing things out and getting drivers to work. No
> offense to tiara but last I looked it was tied to tightly to the
> SiS630 to make a good playground.
I agree. I'm quite pleased with how beautifully abstracted LinuxBIOS and
RedBoot has been. There's one gotcha right now though, that RedBoot
doesn't have the code in it to boot a linux kernel on x86. It should be
fairly simple and straightforward to implement and I'm not real sure why
they haven't. I haven't had time yet to investigate it fully. Oh, and
RedBoot is under an Apache like license.
> Unless there are caveats for using your ebi on other chipsets I'll
> try it out later today.
Good deal.
- adam
