Welcome, Guest. Please login or register.

Author Topic: Kickstart ROM Replacement (Phase I) Bounty Assigned  (Read 37961 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« on: October 15, 2010, 08:16:23 AM »
Quote from: kolla;584809
it would be interesting to know how far apart AROS on PowerPC is from MorphOS and OS4 in terms of binary compatibility.

Very far apart.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« Reply #1 on: October 15, 2010, 08:26:34 AM »
Quote from: vidarh;584812
Not only this, but a working, binary compatible version of AROS on real Amiga's is pretty much the holy grail for determining how compatible AROS is with real AmigaOS.

I did a bunch of work to the console.device and console handler in AROS recently, and to debug incompatibilities with AmigaOS I had to spend a lot of time getting really old AmigaOS example code compile with AROS on x86. With AROS running fine on m68k Amiga's, I could've gone straight to running Amiga apps as test cases.

Getting it running should help us fix a lot of bugs and incompatibilities that will benefit AROS as a whole
Indeed. MorphOS started with creating a static 68k emulation and running the original KS ROM. Then each module were replaced one by one with PowerPC native versions. This allowed us to run original 68k apps and identify and fix bugs and incompatibilities instantly. This is something AROS hasn't been able to do before (except in limited fashion thru AfA).

There's no question that AROS has thousands of issues that never have been fixed before. Hopefully the author won't get too frustrated.

To help avoid the frustration I'd recommend using the same method MorphOS used: Take original KS ROM and replace components one at a time. This will help debugging a lot. You can easily switch between original and replacement modules to see where some issue might originate. Eventually you wil be able to get rid of the original KS ROM completely and run on your own.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« Reply #2 on: November 06, 2010, 07:54:34 PM »
Quote from: Terminills;589923
from Jason...


First trackdisk-loader ADF that was able to run on AROS M68K is:

EXILE!

http://www.evillabs.net/wiki/index.php/AROS_m68k-amiga#Nov_16.2C_2010:_AROS_.28no_KS.29_ROM

Screenshot and AROS ROM image available. As always, A1200 'stock' configuration.

NOTE: This will *NOT* load any 'standard' DOS loading ADFs, only ones which have
custom non-DOS bootloaders.

But its a start.

Hmm, correct me if I'm wrong but doesn't UAE have a built-in KS ROM replacement being able to do exactly the same?
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« Reply #3 on: November 06, 2010, 11:42:43 PM »
Quote from: bloodline;589969
Sure, from little acorns do big oak trees grow! I think the take home here is that systems which used to just guru now actually do something.

Not much yet, however. It gets really messy around the time dos.library gets into the picture. If good compatibility is desired there's a lot to do there.

Now that the easy part is over the real work can begin.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« Reply #4 on: November 09, 2010, 09:01:27 AM »
Quote from: bloodline;590451
Well, I've said this before, why not join the Dev mailing list and watch the progress :)

I'm pretty sure you will find the current discussion about the BCPL interface interesting (both Jason and Toni seem keen on ensuring 1.3 compatibility :) )

Actually I don't. Trying to do the BCPL interface in C isn't my idea of "fun". I'm sure it is possible, but IMHO certainly not worth the effort.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: Kickstart ROM Replacement (Phase I) Bounty Assigned
« Reply #5 on: November 15, 2010, 02:40:22 PM »
Quote from: bloodline;591912
I can't believe I've waited so long to see this... I hope everyone understands the enormity of what this means!

Frankly I don't see the enormity. It gets interesting if/when Phase II gets completed.