@ncafferkey
Good point.

Kickstart ROM Replacement (Phase I)
...
5. Proof of bounty:
m68k AROS boots native at least on one specific line of real AMIGA's into Wanderer. The use of the original routines in Kickstart ROM for initialization of the Machine is permitted.
Non AMIGA specific library's and devices that usually rest in Kickstart ROM must have a working AROS replacement.
e.g. Workbench and Icon library

Input/Output devices of the supported machine must work (e.g. Sound,Mouse,GFX). The build gives a basic Workbench replacement.

Kickstart ROM Replacement (Phase II)

2. Create an amiga like ROM image which MUST be suitable to flash to a real rom. Kick 1.x like roms should not be larger than 512kB. Kick 3.x like Roms are allowed to be larger than 512kB as long as the machine can initialize from it and access the HD for loading necessary parts to Ram: then booting into AROS or AOS.

AMIGA specific library's and devices that usually rest in Kickstart ROM must have a working AROS replacement. eg. audio and cia .device

The bounty description for phase 1 is ambiguous about what the underlying platform is. Several posts in this thread seem to assume that it is AmigaOS-hosted, rather than m68k-linux or m68k-mac for instance.

The first headline should of course read:
Kickstart ROM Replacement (Phase I)

I would do a little re wording on the mentioned parts.

Kickstart ROM Replacement (Phase II)
...
5. Proof of bounty: M68K AROS is bootable at least on one specific line of real AMIGA's into Wanderer. Input/Output devices of the supported machine must work (e.g. Sound,Mouse,GFX). The build gives a basic Workbench replacement.
...

Kickstart ROM Replacement (Phase II)
...
2. Create an amiga like ROM image which MUST be suitable to flash to a real rom. Kick 1.x like roms should not be larger than 512kB. Kick 3.x like Roms are allowed to be larger than 512kB as long as the machine can initialize from it and access the HD for loading necessary parts to Ram: then booting into AROS or AOS.
...
5. Due to the special nature of this bounty it must complie to clean room standards. So the actual code writer should not have seen parts of Amiga OS code. Team efforts are encouraged, so that one developer can describe AOS functionality to the implementor if needed.

I think something like
"must support keyboard, mouse and video output of an arbitrary classic Amiga model"
should be added to #23, otherwise you can't do anything with this Kickstart.

Quote:

rtl8139 is indeed not in a working state.

Dammy

The bounty for Kickstart ROM Replacement (Phase I) describe the scope of work and type of work needed to be performed.

What main components are needed? What are optional? Please define them well enough. (e.g. exec library, dos library etc)
Quote:

What is the acceptance criteria? How do you prove the bounty (in #5) if it doesn't have to be compatible (#3) with anything? How do you know if the thing works?
Quote:

You might also want to specify the size of FLASH and may be the target (B2000? A3000? A4000? PowerPC?) and say they should be able to boot to at least a shell or workbench or something?

Think of the bounty description as a contract/specs for that new home improvement plan you have. Without one, it is hard to tell the contractor what you want and hard for people to judge if the work is indeed done when the bounty is finished. $1076 is enough money to spend a bit more time defining it.

This is exactly like writing a one page power point slides of a high level description of a design specs and a verification plan. Enough details to capture everything, but not too much to make everybody fall asleep.

Note: From the wording, #23 reads like bring M68K branch up to date with rest of source trdd and don't care what's in it or what it is compatible with as long as it compiles 0 errors/warnings. #24 is making it work.

If #23 means just compile with 0 errors/warnings (*), then the bounty amount needs to be redistributed with #24.

#23 is exactly what the RTL8139 driver is like at the moment. It has a C syntax and compiles to something, but it crashes when you try to use it.

It's been brought up that the wording maybe need to be changed on one or both AROS68k-kickstart bounties. For the sake of clarity, are there any last minute wording need to be changed that would enhance the chances of getting a developer assigned?

Randy