[News] OS4 progress since pre-release | ANN.lu |
Posted on 08-Jun-2004 21:47 GMT by Peter Gordon | 228 comments View flat View list |
Hans-Jorg Frieden has posted a detailed status update on the progress of OS4 to Amigaworld.net.
Brief summary:
· Picasso96 and MUI PPC native
· Kernel supports PPC performance monitor and Altivec
· Moovid (released with OS3.9 as "action") is now running native, and can play DivX and other common formats
· GCC 3.4.0 is ported
· The C libraries are much faster. As a result AmiPDF is up to 60 times faster.
· Serial and floppy drivers coming soon
· USB is working and supports HID devices like keyboards and mice as well as HID joysticks and steering wheels, and USB mass storage devices like USB sticks, flash card readers, 7-in-1 card readers and cameras
· A1 IDE device now has working UDMA support. Also, interrupts are no longer polled but delivered properly. This means that the device does not require any CPU time for transfers.
This material will in due course be released for download to registered users of the Developer Pre-release on our web site at:
http://www.hyperion-entertainment.biz
There is more detail in the original AW.net posting.
|
|
List of all comments to this article |
OS4 progress since pre-release : Comment 157 of 228 | ANN.lu |
Posted by Anonymous on 09-Jun-2004 20:20 GMT | In reply to Comment 152 (Stefan Burström): > Look on an aos4 machine and you'll see lots of library.main in libs. They are the stubs for the main interface. And if the real library is replaced, the
.main file is not loaded
The more I hear about it, the less I like it (it being the m68k integration of AmigaOS4, especially as it related to libraries). Kludges galore, it appears. Reserved address spaces, app runners, stubs for interfaces, where does the madness end? I've always liked the simplicity in AmigaOS, this corner of OS4 sounds like rocket since to me. Please correct me if the next paragraph is wrong, I don't claim to understad the issue: is it correct that MorphOS avoids the complications of two kinds of code by always assuming (even if only for one instruction) that called code is 68k code, and only after that first instruction switching to PPC, if the code is PPC? And thus avoiding reserved memory/address space for 68k code, complicated stubs and such, offloading the whole issue into the compiler? If so, then that sounds a lot smarter to me, for a transitional OS. |
|
List of all comments to this article (continued) |
|
- User Menu
-
- About ANN archives
- The ANN archives is powered by #AmigaZeux. It was updated daily (news last: 22-Oct-2004; comments last: 18-May-2005).
ANN.lu was created, previously owned and maintained by Christian Kemp, www.ckemp.com.
- Contribute
- Not possible at this time!
- Search ANN archives
- Advanced search
- Hosting
- ANN.lu was hosted by Dreamhost. Sign up through this link, mention "ckemp" as referrer and he will get a 10% commission on any account you purchase.
Please show your appreciation for any past, present and future work on ANN.lu by making a contribution via PayPal.
|