23-Apr-2024 09:45 GMT.		 UNDER CONSTRUCTION
Anonymous, there are 212 items in your selection [1 - 50] [51 - 100] [101 - 150] [151 - 200] [201 - 212]
[News] Hyperion finished AmigaOne firmwareANN.lu
Posted on 29-Sep-2002 18:55 GMT by xisp212 comments
View flat
View list

Hyperion is pleased to report that it has completed the AmigaOne firmware based on the GPL'ed PPCBoot project.

Source: AmigArt.

Leuven, Belgium - September 27, 2002.

Hyperion is pleased to report that it has completed the AmigaOne firmware based on the GPL'ed PPCBoot project. Below you will find a description of the implemented hardware support and functionality. We want to thank everyone who has contributed to this project.

Hardware support for the following devices:
-Serial port
-USB UHCI
-USB keyboard
-USB storage devices
-PS/2 compatible keyboard
-i8259 interrupt controller
-3com 3c920 ethernet with full busmastering
-VIA IDE controller (A and B revision)
-Real time clock (RTC)

Features of PPCBoot (as implemented by Hyperion):
-x86 BIOS emulator capable of initialising and using nearly all PCI and AGP graphic cards based on the chipsets of ATI, nVidia, 3DFX, S3, 3Dlabs (Permedia), Trident etc.
-Auto detection of SDRAM modules
-Auto detection of bus and CPU speed
-Support for PCI and AGP
-General ArtiticaS support
-General VIA686 southbridge support (686A and 686B)
-IDE support (harddisk and CD-ROM booting)
-Floppy support
-Booting over network"

Ben Hermans, Hyperion.

Hyperion finished AmigaOne firmware : Comment 1 of 212ANN.lu
Posted by Berny on 29-Sep-2002 17:27 GMT
Cool. So OS4 is ready. Drooooooooooooooool.
Hyperion finished AmigaOne firmware : Comment 2 of 212ANN.lu
Posted by CD32freak on 29-Sep-2002 17:37 GMT
Yay! Good job, Hyperion team..let's Rock 'n' Roll! :D
Hyperion finished AmigaOne firmware : Comment 3 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 17:49 GMT
Ok well done, but it shouldn't already finished before PA2002?
Hyperion finished AmigaOne firmware : Comment 4 of 212ANN.lu
Posted by Bladerunner on 29-Sep-2002 18:03 GMT
In reply to Comment 1 (Berny):
No. The Bios from the Aone is ready, not OS 4.0
But the Aone might be able now to boot a bit more comfortable ;-)
Hyperion finished AmigaOne firmware : Comment 5 of 212ANN.lu
Posted by Rob on 29-Sep-2002 18:38 GMT
In reply to Comment 4 (Bladerunner):
Now they can concentrate on finishing the rest of OS4.
Hyperion finished AmigaOne firmware : Comment 6 of 212ANN.lu
Posted by chris on 29-Sep-2002 18:54 GMT
In reply to Comment 5 (Rob):
Considering, that there wasn`t even shown an alpha running on CSPPC/BPPC
this "REST" should be around 80% of what is needed for an PPC-AmigaOS...
Sorry folks, don`t expect OS4.0 for christmas - at least not this year, but
perhaps next year christmas...
Hyperion finished AmigaOne firmware : Comment 7 of 212ANN.lu
Posted by Graham on 29-Sep-2002 19:02 GMT
"USB storage devices"
So this means that we should be able to boot off of USB floppies/zips/CD/DVD/flash/etc as well? (like you can with recent PC BIOSen). Neat if this is the case.
Is the firmware graphical or text mode? Any screenshots?
Hoepfully this will provide a firm base for booting AmigaOS4 on the AmigaOne and thus get AmigaOS4 + AmigaOne out in time for Christmas.
Hyperion finished AmigaOne firmware : Comment 8 of 212ANN.lu
Posted by Ben Hermans/Hyperion on 29-Sep-2002 19:05 GMT
In reply to Comment 6 (chris):
You clearly don't have insight into the problem.
With ExecSG finished, the only work required to get a full system is integrating the 68K emulator for those system modules which will not be PPC native.
This work is currently underway and in the hands of an expert in the field (not somebody from Hyperion).
The idea that this will take a year is simply ridiculous.
I could mention the number of weeks we agreed on contractually but that would ruin my chance to make some lucrative bets with some of the nay-sayers here.
Hyperion finished AmigaOne firmware : Comment 9 of 212ANN.lu
Posted by kriz on 29-Sep-2002 19:09 GMT
nice :) ! hyperion keeps it up ..
Hyperion finished AmigaOne firmware : Comment 10 of 212ANN.lu
Posted by anon on 29-Sep-2002 19:14 GMT
In reply to Comment 8 (Ben Hermans/Hyperion):
So basically you are saying hyperion is too clueless to even do something as trivial as an 68k emulation?
Hyperion finished AmigaOne firmware : Comment 11 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 19:18 GMT
In reply to Comment 8 (Ben Hermans/Hyperion):
Ok, so you have someone else to blame on delays now?
Hyperion finished AmigaOne firmware : Comment 12 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 19:20 GMT
In reply to Comment 10 (anon):
Oh, FFS...
Hyperion finished AmigaOne firmware : Comment 13 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 19:25 GMT
Is it Hyperion's intention to merge this with PPCBoot CVS or are they going to maintain their own fork indefinitely ?
Also it's my understanding that this Firmware is for MAI to use on all their motherboards. Will MAI be shipping their boards with source on the driver CD, or just an offer of source ?
Hyperion finished AmigaOne firmware : Comment 14 of 212ANN.lu
Posted by Bladerunner on 29-Sep-2002 19:29 GMT
In reply to Comment 8 (Ben Hermans/Hyperion):
>With ExecSG finished, the only work required to get a full system is integrating the 68K emulator for those system modules which will not be PPC native.
So that means every module which was demoed on the latest shows stuck on 68k? If not, how much time do you expect to port them on PPC?
If so, what except the filesystem and exec will run native? And if there are too many 68k Modules (really i thought OS 4.0 itself runs 100% nativ)
Don`t you think performance on the Phase5/DCE Stuff will be really bad?
Hyperion finished AmigaOne firmware : Comment 15 of 212ANN.lu
Posted by xisp on 29-Sep-2002 19:37 GMT
In reply to Comment 14 (Bladerunner):
@Bladerunner
How come you do so much questions?
I thought everyone in amiga community had a certain knowledge on programming stuff works.
Porting C code from 68k to ppc under the same operating systemchange a few settings+simply recompile.
Is it so hard to understand that Intuition and the rest of demoed modules will only need a few days or HOURS to work on native PPC?
Hyperion finished AmigaOne firmware : Comment 16 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 19:45 GMT
In reply to Comment 15 (xisp):
Obviously you have no clue. Go learn your lesson.
Hyperion finished AmigaOne firmware : Comment 17 of 212ANN.lu
Posted by xisp on 29-Sep-2002 19:51 GMT
In reply to Comment 16 (Anonymous):
Obviously you have no clue. Go learn your lesson
Hyperion finished AmigaOne firmware : Comment 18 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 19:53 GMT
In reply to Comment 15 (xisp):
Especially when the code has been made with this porting in mind (and I can't see why they shouldn't)..
Hyperion finished AmigaOne firmware : Comment 19 of 212ANN.lu
Posted by Ben Hermans/hyperion on 29-Sep-2002 20:05 GMT
In reply to Comment 13 (Anonymous):
We will ofcourse merge our code back into PPCBoot provided the maintainers of PPCBoot are interested.
We will comply fully with the GPL license.
Hyperion finished AmigaOne firmware : Comment 20 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:06 GMT
So since you guys seem to be "expert" about this, please tell us how many OS components you have actually recompiled for the PPC?
Hyperion finished AmigaOne firmware : Comment 21 of 212ANN.lu
Posted by Ben Hermans/Hyperion on 29-Sep-2002 20:13 GMT
In reply to Comment 10 (anon):
We are talking about the 68K emulation but integration of the emulation layer into the OS.
And not with this cumbersome and unelegant "emulation trap" system.
Hyperion finished AmigaOne firmware : Comment 22 of 212ANN.lu
Posted by xisp on 29-Sep-2002 20:16 GMT
In reply to Comment 20 (Anonymous):
Man, use logic.
When you do any piece of software for a certain cpu and YOU KNOW you will have to port it to another, you make it very portable from the begining, as much as you can. So the process is as automatic as possible. Even if they have to rewrite a few parts of the source it will take them less time than A YEAR. (Like someone suggested in an almost-offensive way some posts above this one). In fact it would take days or as much as a couple of weeks if it's especially big.
Hyperion finished AmigaOne firmware : Comment 23 of 212ANN.lu
Posted by Ben Hermans/Hyperion on 29-Sep-2002 20:16 GMT
In reply to Comment 20 (Anonymous):
The list is too long to mention here but essentially ever C based OS component that is somewhat performance critical.
This excludes certain components such as Arexx which are 68K ASM based.
Hyperion finished AmigaOne firmware : Comment 24 of 212ANN.lu
Posted by Bladerunner on 29-Sep-2002 20:18 GMT
In reply to Comment 15 (xisp):
Sorry, maybe I didn`t get it, English is not my mother language, but as i understand ist,
there WILL be 68k OS modules in OS 4.0... Or what else does it mean?
Anyway, I am not a coder, so I can`t say anything about recompiling 68k stuff to PPC.
But I am sure that it is not done with a simple recompile, setting the "magical do ppc binary" switch on.
A Friend did this with Storm 4 and his Prog(Ok, I know it do warp OS code which is different) , 68K Binary worked fine,
PPC binary crashed... (He has no PPC Board)...
Hyperion finished AmigaOne firmware : Comment 25 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:18 GMT
In reply to Comment 8 (Ben Hermans/Hyperion):
This is great news...! Can we have some screenshots of the new early startup menu too? :)
Hyperion finished AmigaOne firmware : Comment 26 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:19 GMT
In reply to Comment 23 (Ben Hermans/Hyperion):
So you claim you can actually use these PPC builded modules?
Hyperion finished AmigaOne firmware : Comment 27 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:19 GMT
In reply to Comment 26 (Anonymous):
"use" as run them right now.
Hyperion finished AmigaOne firmware : Comment 28 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:22 GMT
In reply to Comment 22 (xisp):
So now you suggest that AmigaOS source code was written portability in mind? I very much doubt that, since AmigaOS was never going to be ported to any other system.
Hyperion finished AmigaOne firmware : Comment 29 of 212ANN.lu
Posted by Ben Hermans/Hyperion on 29-Sep-2002 20:22 GMT
In reply to Comment 14 (Bladerunner):
I have already mentioned this quite a few times but I will go through the motions again.
OS 3.x source-code which compiles with GCC can be made to compile with OS 4 nearly out of the box.
The OS 4 development team has obviously been using GCC for quite some time now which essentially means that any C based OS 3.x component will be available in PPC native format for OS 4.
This includes components such as DOS, Exec SG, Roadshow, the Shell, the USB stack, FFS2, Intuition, Reaction etc. etc.
Only non-performance critical components will still be 68K if no C version is available.
Hyperion finished AmigaOne firmware : Comment 30 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:26 GMT
In reply to Comment 29 (Ben Hermans/Hyperion):
So tell us, have you actually ever run these PPC builded components? Or you just assume they work ok?
Hyperion finished AmigaOne firmware : Comment 31 of 212ANN.lu
Posted by Ben Hermans/Hyperion on 29-Sep-2002 20:27 GMT
In reply to Comment 28 (Anonymous):
Honestly, what do you believe we have been doing these last 11 months?
Hyperion finished AmigaOne firmware : Comment 32 of 212ANN.lu
Posted by Rob on 29-Sep-2002 20:30 GMT
In reply to Comment 10 (anon):
If you used your brain then you would realise that Hyperion are not working on every component of OS4. Have you heard of the teamwork, it usually works like this. The more people who work on a project the quicker that project will be completed.
Hyperion finished AmigaOne firmware : Comment 33 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:31 GMT
In reply to Comment 31 (Ben Hermans/Hyperion):
Working blindly on OS components without testing them on PPC, only 68k.
Hyperion finished AmigaOne firmware : Comment 34 of 212ANN.lu
Posted by Steffen Haeuser on 29-Sep-2002 20:35 GMT
In reply to Comment 17 (xisp):
xisp is *right*. Anonymous (from comment 16), Chris (from comment 6, BTW: Please
stop claiming things as truth where you can have ABSOLUTELY no clue about, as
you are not involved - not even if maybe you WANT certain things to
happen) are wrong.
xisp: I can only underline what you said in comment 22. Right ! And you probably
already include some compiler switches for the "system to come" to be able
to compile it with at most a handful of changes later...
Anonymous from comment 13: It does not really matter if they include the source,
or only the offer to get the source from them by asking for it. Both is according to GPL. If you want to
accuse them (or us) of breaking the GPL, please do so openly. In a normal
legal system someone is innocent until proven guilty. And yes, we will comply
to the GPL.
There are many modules where the move to PPC is just a matter of a simple
recompile. This is for example true for the Modules I have been working on.
For other Modules the programmers already included a compiler switch (which just
as long as the Emulator integration was not yet complete was not yet "used",
but where the source-code exists already - and where it is again only a matter
of a simple recompile then) with the actual differences for a PPC Compile.
And again other modules (for example ExecSG) were done in PPC Native code from the
start.
Bottom line: As long as you did not see the source-code you cannot really
do a sensible comment on the time-frame.
All "C-ifying" was of course done with the goal of a port to PPC, not with the
goal to a port to 68k.
So don't assume too much, (certain) people. Especially if it is about things were
you have absolutely no knowledge about.
I am of course aware that there are certain people who would like it pretty much
if we'd be far more behind than we are actually are.
Steffen Haeuser
Hyperion finished AmigaOne firmware : Comment 35 of 212ANN.lu
Posted by Steve on 29-Sep-2002 20:39 GMT
Hello,
"The more people who work on a project the quicker that project will be completed"
No sorry this is not so simple. There is a limit, if the team is too big this slow down the project because of "synchronization" problems.
Regards
Hyperion finished AmigaOne firmware : Comment 36 of 212ANN.lu
Posted by Elektro on 29-Sep-2002 20:41 GMT
In reply to Comment 35 (Steve):
this aint microsoft u know?... :)
Hyperion finished AmigaOne firmware : Comment 37 of 212ANN.lu
Posted by xisp on 29-Sep-2002 20:45 GMT
In reply to Comment 33 (Anonymous):
¿Blindly?
Every big software project is handled on separate modules, all developed in paralel at the same time. Modern languages and compilers provide this module programming aproach, to make it as reliable as possible. Though, there must be coordination between separate teams to prevent that modules cannot be "glued" at last minute.
I don't know if this coordination has been well managed at Hyperion. I hope it has. But I tell you something. If it wasn't done this way, no modern software project would be finished in a year, it would take decades.
I give them the benefit of doubt, because I know (roughly) how this stuff works. Certainly you have no clue, and if I were you I would retreat with dignity without doing this more embarrasing for you (and for the rest of us).
Hyperion finished AmigaOne firmware : Comment 38 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:47 GMT
In reply to Comment 34 (Steffen Haeuser):
So, did Ole-Egil and others already receive the source code for the ROMs that have been distributed to beta testers / developers/ whatever Alan is calling them at the moment?
Hyperion finished AmigaOne firmware : Comment 39 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:50 GMT
In reply to Comment 34 (Steffen Haeuser):
Hi Steffen / Ben!
Few questions...if you can answer: :P
-Will there be decent IDE for AmigaOS4? StormC v.5 or similar?? :)
-How's game developement? Will we see new games simultaneously with OS4 release?
-How about Realsoft 3D...will it be out soon?
-Is all necessary parts now ready (excluding JIT)?
Keep doing a good work!
Hyperion finished AmigaOne firmware : Comment 40 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:54 GMT
In reply to Comment 34 (Steffen Haeuser):
Oh...I have to ask this: "How far you actually are???? Give as a glue!? ;)
Hyperion finished AmigaOne firmware : Comment 41 of 212ANN.lu
Posted by Elektro on 29-Sep-2002 20:56 GMT
In reply to Comment 40 (Anonymous):
hehe glue :D ;)
Hyperion finished AmigaOne firmware : Comment 42 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 20:56 GMT
In reply to Comment 39 (Anonymous):
Oh thanks finally a good comment&questions!
Please no more sad and pointless accuse to OS4.0, if you don't believe on Hyperion just browse the web page www.microsoft.com! You can always buy something funny!!
Hyperion finished AmigaOne firmware : Comment 43 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 21:00 GMT
In reply to Comment 34 (Steffen Haeuser):
> All "C-ifying" was of course done with the goal of a port to PPC, not with the
> goal to a port to 68k.
All that has been shown in public are some (intuition, layers, more?) components patched into OS 3.9, running under 68K CPU.
It's unfortunate that you can't tell public if any of those compoments actually run on PPC... That's classified information right?
But then again, according to information splilled in public, OS4 is all-or-nothing until 68K emu is implemented (either everything must be implemented in PPC, which is quite impossible if you think about it, or the 68K emulation is added so that you can mix PPC and 68K).
Basically this means that OS4 can't be tested under PPC until the 68K emu is finished. And before the actual PPC testing there is no way to know if the PPC build is working at all (obviously).
Oh, and if you (the reader) didn't realize already, this is all wild speculation and there is no doubt that I am going to be proven wrong Real Soon Now.. Right..?
Hyperion finished AmigaOne firmware : Comment 44 of 212ANN.lu
Posted by Adam Kowalczyk on 29-Sep-2002 21:01 GMT
In reply to Comment 38 (Anonymous):
I have the most recent sources of PPCBoot copied to a flash chip and it works quite well on my AmigaOne here. Keep in mind that only a few of us have the capability of flashing chips to perform testing.
Hyperion finished AmigaOne firmware : Comment 45 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 21:03 GMT
In reply to Comment 37 (xisp):
"Blind" was referring to PPC-testing which is non-existant for obvious reasons (the still missing 68K emulation).
Having a component run on 68K will not guarantee it will work out of the box in mixed 68K/PPC environment.
But then again, you have no clue, so...
Hyperion finished AmigaOne firmware : Comment 46 of 212ANN.lu
Posted by .jon on 29-Sep-2002 21:12 GMT
Why is there no Firewire support ?
How does this fit the ZICO specs ? Or is it not important to have Firewire
within the BIOS ?
.jon
Hyperion finished AmigaOne firmware : Comment 47 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 21:12 GMT
In reply to Comment 44 (Adam Kowalczyk):
So you burn the source code to the chip and it gets interpreted on the fly? Amazing technology you have there!
Hyperion finished AmigaOne firmware : Comment 48 of 212ANN.lu
Posted by elektro on 29-Sep-2002 21:13 GMT
In reply to Comment 46 (.jon):
not relevant for bios afaik.
Hyperion finished AmigaOne firmware : Comment 49 of 212ANN.lu
Posted by elektro on 29-Sep-2002 21:15 GMT
In reply to Comment 48 (elektro):
anyway forget those zico specs thats nothing...
Hyperion finished AmigaOne firmware : Comment 50 of 212ANN.lu
Posted by Anonymous on 29-Sep-2002 21:22 GMT
In reply to Comment 23 (Ben Hermans/Hyperion):
"This excludes certain components such as Arexx which are 68K ASM based. "
Hmmm...Wasn't there suppose to be PREXX or something like that?
Anonymous, there are 212 items in your selection [1 - 50] [51 - 100] [101 - 150] [151 - 200] [201 - 212]
Back to Top