Hi, some updates on paflof I made recently: * use c style comments to not break non gcc compilers (compile with -ansi -pedantic) * implement unaligned-w@, unaligned-w!, unaligned-l@, unaligned-l! * implement 2constant * fix typo in dict.source * use conf.pl to create types.h according to compiler capabilities (cross compiling possible) (cleaner version then last patch) * move unix host code from prim.code to unix.code Best regards, Stefan Reinauer -- The x86 isn't all that complex - it just doesn't make a lot of sense. -- Mike Johnson, Leader of 80x86 Design at AMD Microprocessor Report (1994)
how soon do you think it will be before we can try this under linuxbios? ron - To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message http://www.freiburg.linux.de/OpenBIOS/ - free your system..
* Ronald G Minnich <rminnich@lanl.gov> [020623 18:23]:
how soon do you think it will be before we can try this under linuxbios?
the only missing words that might be critical for operation are key?, alloc-mem, free-mem. We should be able to use the values from the LinuxBIOS table to initialize memory allocation. Can we assume memory being one linear chunk? A nice thing to have is package/properties support because that would allow us to write initialization drivers as packages, using the OO capabilities of Open Firmware instead of having one linear bunch of code that is executed for initialization. I started writing an fcode evaluator in Forth. The skeleton is working, but some words for flow control are missing. This will allow to execute FCode binaries instead of forth source code with paflof. Stefan -- The x86 isn't all that complex - it just doesn't make a lot of sense. -- Mike Johnson, Leader of 80x86 Design at AMD Microprocessor Report (1994) - To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message http://www.freiburg.linux.de/OpenBIOS/ - free your system..
participants (2)
-
Ronald G Minnich -
Stefan Reinauer