Maybe this has been asked before, but i've been thinking about exporting functions like serial console, debugger entry points, etc. the PC BIOS uses the interrupt vectors as, well, vectors. I remember the C=64 had a jump table at a fixed address. I was wondering how hard it would be to use an ELF symbol table as a jump table, or at least as the source of information to build one.
* Jeremy Jackson jerj@coplanar.net [040902 06:08]:
Maybe this has been asked before, but i've been thinking about exporting functions like serial console, debugger entry points, etc. the PC BIOS uses the interrupt vectors as, well, vectors. I remember the C=64 had a jump table at a fixed address. I was wondering how hard it would be to use an ELF symbol table as a jump table, or at least as the source of information to build one.
LinuxBIOS exports some information in a data structure called the LinuxBIOS table. It has been the expressed wish of many here to not have any callback functionality in LinuxBIOS, so no entry points or function calls to LinuxBIOS code. If you want this, have a look at OpenBIOS as a payload on top of LinuxBIOS. It provides IEEE 1275-1994 (Open Firmware) compliant callbacks to the operating system.
Stefan
well, the original goal was that the external api was linux. I still hate to abandon this goal.
I'll let eric say more :-)
ron
I remember that some time ago, Miller met the problem with the use FILO and FILO in Etherboot to boot elf made by mkelfImage 2.5....from Kernel and Init.
The kernel said that can not find the init.
Yesterday I met the same problem under following configuration:
Kernel: 2.6.8.1 compiled under Suse 9.1 AMD64 ( gcc 3.3.3). Used mkelfImage under Redhat 9 to produce the final elf.
When I use 2.6.5, 2.6.6, 2.6.7 with Suse 9 compiler gcc 3.3.1, all work well.
Miller seems have problem with 2.6.6 and Suse 9.1.
So I guess there is some problem with gcc 3.3.3 in Suse 9. or there is some optimization for (EM86T) cause problem.
Miller, Can you try to compile your kernel under Suse 9.?
Regards
YH
We're going to switch from using the EPIA MII series to EPIA MS as it meets the needs of a digital entertainment device much better. Anyone else working on getting the MS booting with LinuxBIOS, or will I be in virgin territory? :-)
-marc
Marc Nicholas wrote:
We're going to switch from using the EPIA MII series to EPIA MS as it meets the needs of a digital entertainment device much better. Anyone else working on getting the MS booting with LinuxBIOS, or will I be in virgin territory? :-)
We're starting with the CN400 (found in the Epia N) and newer chipsets. For our apps. the CLE266 is too slow.
-Bari