the current openbios cvs contains a lot of new code from the device
interface. We have a device tree now and can evaluate FCode on device
Now OpenBIOS lacks a whole lot of Open Firmware "support packages" like the
deblocker, tftp booting for network interfaces, the terminal emulator,
filesystem support, etc etc.
And of course: OpenBIOS needs device drivers! Open Source drivers,
vendor FCode, everything that helps OpenBIOS to support a wide range of
I started setting the framework for the support packages in
openbios/forth/packages, find one source file per support package.
Also, there's an example fcode driver coming with the QT-Plugin of the
openbios kernel: openbios/kernel/plugins/plugin_qt/qt_rom.fs
I'll attach a simple example to this mail that executes the QT Plugins
FCode. To test it, do:
~/openbios $ make
~/openbios $ make rungui < device-example.fs
It will use the FCode binary built into the plugin to initialize the
virtual graphics hardware and output a character.
Next thing I'm going to work on is to finish the terminal emulator and
other support packages, then facing the client interface code to finally
boot an operating system
For the client interface it should make sense to reuse a lot of existing
code, i.e filesystem drivers (GRUB), elf booting (Filo, LinuxBIOS),
etc. by using the calling interfaces from forth to C and the other way round.
Show replies by thread