Kickstart ROM Replacement (Phase II) Assigned

[bloodline]

Great!

I am just looking forward that Amiga 68k hunk compatibility gets achieved (not just a loader).

In that way, we can freely mix Aros68k with native AmigaOS68k files, and get the best from both worlds.

It does use Amiga hunk files, and you can mix and match to some degree (AROS components are ELF files), But AROS can load both

[Gulliver]

It does use Amiga hunk files, and you can mix and match to some degree (AROS components are ELF files), But AROS can load both

I see your point, but I am looking that it works both ways, not just Amiga files in an AROS enviroment, but AROS executables in an Amiga enviroment.

Remember that still, Amiga68k is much more optimised/faster than AROS on the same hardware.

[vidarh]

I see your point, but I am looking that it works both ways, not just Amiga files in an AROS enviroment, but AROS executables in an Amiga enviroment.

Remember that still, Amiga68k is much more optimised/faster than AROS on the same hardware.

There's a tool that can convert AROS ELF binaries to AmigaOS hunk files. But if you want files that work both places, just compile them for AmigaOS...

[Gulliver]

There's a tool that can convert AROS ELF binaries to AmigaOS hunk files. But if you want files that work both places, just compile them for AmigaOS...

Which tool performs that convertion? It would be very interesting to get some AROS components working on AmigaOS.

Thanks in advance

[dammy]

not so great a quality pictures:

http://img684.imageshack.us/i/aros1p.jpg/
http://img21.imageshack.us/i/aros2c.jpg/
http://img101.imageshack.us/i/aros3.jpg/

Very impressive, just wish this was done years ago.

[vidarh]

Which tool performs that convertion? It would be very interesting to get some AROS components working on AmigaOS.

Thanks in advance

ELF2HUNK by Jason McMullan

There are some limitations. Most notably, AROS apps using arosc.library won't work (at least not yet), and arosc.library itself won't work so moving that over won't do you any good. But apps that stick with purely the AmigaOS API will work. This restrictions makes it quite limited at the moment.

To get AROS components working on AmigaOS you're better off looking AfA.

[deadwood]

More news from Toni (source: AROS dev list):


ArosBootStrap now accepts more parameter(s), one or more extra resident
files (similar to BlizKick)

For example "arosbootstrap aros.elf.gz scsi.device_40.12(A3000)" allows
AROS to boot from SCSI on my real A3000.
(scsi.device is extracted from A3000 ROM using romsplit that comes with
remus package)

Next phase is to support RTG boards using AOS Picasso96 .card and .chip
files. (I think I already mentioned this few months ago)

"arosbootstrap aros.elf.gz libs:picasso96/CirrusGD542X.chip
libs:picasso96/PicassoII.card scsi.device_40.12(A3000)"
already loads on my PicassoII expanded A3000, PicassoII.card FindCard()
and InitCard() functions already succeed but nothing is visible yet.
I hope I have something working in next few days..

Motorola 68040/68060 missing instruction emulation library is also working
now, but it isn't yet  rom built-in. It is quite big  (~60k) so I guess it
should be only included in arosbootstrap file at this point?
(official 68040/68060 libraries may not be used because for example they
need  to update FPU stack frame handling = touch exec internals that
shouldn't be touched)

Autoconfig support has been partially rewritten, most boards should now
configure properly.

[wawrzon]

havnt had time to test for few days, but now im getting curious. hope the other commits improve stability a little. and of course fpu support is a must to try.

[Heiroglyph]

I tested todays build and it is looking much better in WinUAE.

It's a shame that the preferences aren't set better.  Until you tweak it, it seems really bad.

Screen refresh in non-truecolor modes is painfully slow.  You can watch the pixels draw in, even on a fast WinUAE system.

Use the new build of WinUAE or else it won't run.
Use the nightly ROM and System HD folder from Sourceforge.
Set it for a stock A1200 with extra fast RAM (16M+ I saw some huge memory use/leaks in Wanderer)
Enable JIT and Picasso emulation
Painfully get into preferences and set the screen mode to a 32bit RTG mode and save (test doesn't seem to work)

Restart WinUAE after this, otherwise it doesn't seem to really pick up on the changes, causing other redraw problems.

At that point it works fairly well, but it's still pretty buggy.

[Terminills]

From the dev mailing list while talking about scalos for aros.

"I'll put that on my list of things to test after (a) DOS Packets, (b)
Mediator PCI support for m68k, (c) AHCI support for AROS [all
architectures], (d) VESA ROM PCI graphics card support for AROS
(non-x86)[1]

But it's in my list!

[1] This uses the x86 emulator code from u-boot, which is *not* GPL licensed.

--
Jason McMullan"

[deadwood]

Look what people can do now with AROS m68k!

http://eab.abime.net/showthread.php?t=60144

[SysAdmin]

Look what people can do now with AROS m68k!

http://eab.abime.net/showthread.php?t=60144

Very nice!