Here's a list of bounties I plan on adjusting and then submitting.

First EMU68 Bounty. (This one is set in stone as it was written with the help of mschulz).

Porting Emu68 to EFI
Overview
This bounty focuses solely on adapting Emu68 to function as an EFI binary executable, laying the foundation for future work to enable AmigaOS/AROS 68K to boot natively on ARM hardware. Since EFI handles hardware abstraction via its protocols, the scope of this bounty is limited to making Emu68 compliant with the EFI standard and ensuring basic ACPI table parsing for future use.

Objectives
1. Adapt Emu68 to function as a compliant EFI binary executable.
2. Implement basic support for:
ACPI Table Parsing: Convert Little Endian ACPI data to Big Endian for compatibility with 68K environments.
3. Lay the groundwork for AmigaOS and AROS integration in subsequent phases.

Last edited by terminills on 21-Dec-2024 at 05:38 PM.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

AROS Bounties

• 
  Pre-Boot Phase:
  
  
  
  
  
  
  
  • 
    Automatically select the best
    available resolution using GOP before boot services terminate.
    
    
  
  
  • 
    Optional: Allow users to select a
    resolution via the Early Startup Control menu.
    
    
  
  
  
  


• 
  Runtime Phase:
  
  
  
  
  
  
  
  • 
    Develop a HIDD driver to use the
    static framebuffer provided by GOP for rendering after
    ExitBootServices.
    
    
  
  
  • 
    Ensure compatibility with AROS’s
    graphics subsystem.
    
    
  
  
  
  


• 
  Fallback and
  Compatibility:
  
  
  
  
  
  
  
  • 
    Use the VESA ROM driver as a
    reference for structure.
    
    
  
  
  • 
    Provide fallback options for systems without GOP support.
    
    
  
  
  
  

• 
  Enables AROS to display graphics
  on modern UEFI-based systems using GOP.
  
  


• 
  Similar to what VESA driver provides on PCs
  



• 
  Provides automatic resolution
  selection or the option for manual configuration during boot.
  
  


• 
  Offers basic graphics functionality for systems lacking
  legacy BIOS modes.
  
  

• 
  Use EFI_SIMPLE_TEXT_INPUT_PROTOCOL
  for keyboard input and EFI_SIMPLE_POINTER_PROTOCOL
  for mouse input during the pre-boot phase.
  
  


• 
  Ensure a smooth transition to AROS’s input.device
  post-boot.
  
  

• 
  Ensures full keyboard and mouse
  functionality during boot and runtime.
  
  


• 
  Enables a smooth transition from pre-boot input handling to
  AROS’s native input system.
  
  

• 
  Parse and convert ACPI tables into
  a format usable by AROS.
  
  


• 
  Validate ACPI-driven hardware discovery and initialization.
  
  

• 
  Allows AROS to detect and utilize
  hardware like storage devices, network cards, and USB ports.
  
  


• 
  Improves hardware compatibility with modern systems by
  leveraging ACPI.
  
  

• 
  Add support for
  EFI_BLOCK_IO_PROTOCOL and
  EFI_SIMPLE_FILE_SYSTEM_PROTOCOL.
  
  


• 
  Validate kernel and file loading
  from block-oriented devices.
  
  


• 
  Ensure compatibility with GRUB.
  
  

• 
  Enables AROS to boot directly from
  modern storage devices like SSDs or USB drives.
  
  


• 
  Supports both UEFI-native and GRUB-based boot setups.
  
  

• 
  Integrate EFI system table and
  memory map handling.
  
  


• 
  Add support for
  EFI_DEVICE_PATH_PROTOCOL for locating
  devices.
  
  


• 
  Leverage GOP for display initialization during boot.
  
  

• 
  Improves bootloader performance
  and compatibility on EFI-based systems.
  
  


• 
  Provides better hardware support during boot, enhancing the
  user experience.
  
  

• 
  Add support for
  EFI_SIMPLE_NETWORK_PROTOCOL in the AROS
  bootloader.
  
  


• 
  Enable PXE boot functionality.
  
  


• 
  Add tools for diagnosing network connectivity during
  pre-boot.
  
  

• 
  Enables network booting, allowing
  AROS to be loaded directly over a network.
  
  


• 
  Adds pre-boot networking diagnostics for troubleshooting and
  improved reliability.
  
  

• 
  Adapt EFI protocols for
  cross-platform compatibility.
  
  


• 
  Validate EFI functionality on ARM, MC68K, and x86 platforms.
  
  

• 
  Broadens AROS’s compatibility
  with modern hardware architectures, including ARM and retro-inspired
  68K systems.
  
  


• 
  Ensures AROS can run on diverse hardware platforms.
  
  

• 
  Add support for authenticated boot
  processes using signed kernels.
  
  


• 
  Validate Secure Boot workflow on EFI platforms.
  
  

• 
  Enables AROS to boot securely on
  systems with Secure Boot enabled.
  
  


• 
  Ensures compatibility with security requirements on modern
  PCs.
  
  

• 
  Provide tools for accessing EFI
  protocols (storage, graphics, input, networking).
  
  


• 
  Implement diagnostics for troubleshooting EFI-related issues.
  
  

• 
  Simplifies managing EFI features
  on AROS systems.
  
  


• 
  Provides tools for diagnosing EFI hardware and improving
  system stability.
  
  

Last edited by terminills on 21-Dec-2024 at 06:43 PM.
Last edited by terminills on 21-Dec-2024 at 06:09 PM.
Last edited by terminills on 21-Dec-2024 at 05:58 PM.
Last edited by terminills on 21-Dec-2024 at 05:33 PM.
Last edited by terminills on 21-Dec-2024 at 05:19 PM.
Last edited by terminills on 21-Dec-2024 at 05:13 PM.
Last edited by terminills on 21-Dec-2024 at 04:56 PM.
Last edited by terminills on 21-Dec-2024 at 04:55 PM.
Last edited by terminills on 21-Dec-2024 at 04:52 PM.
Last edited by terminills on 21-Dec-2024 at 04:40 PM.
Last edited by terminills on 21-Dec-2024 at 04:35 PM.
Last edited by terminills on 21-Dec-2024 at 04:18 PM.
Last edited by terminills on 21-Dec-2024 at 04:15 PM.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

This isn't AROS specific but rather AmigaOS but I didn't want to separate it from the rest.


AmigaOS Boot Implementation for EFI-Based "MC68K" Machine

Overview:

This bounty focuses on the development of a secondary 68K bootloader to enable AmigaOS 68K to boot on an EFI-based "MC68K" machine. The bootloader will be designed to initialize hardware via EFI, emulate missing hardware components like CIA chips and display, and then transition control to the AmigaOS kernel. The bootloader will utilize the Emu68 platform to provide hardware abstraction and initialization.

Key Objectives:

ACPI Table Handling:

Parse and utilize Big Endian ACPI tables (converted in Bounty 1) to extract hardware information such as USB, PCI, networking, and storage.
Provide hardware details to the AmigaOS environment through accessible memory structures or standard tables.
Ensure efficient integration with EFI protocols for seamless hardware initialization.
Development of a Secondary Boot Program:

Create a standalone 68K bootloader program that:
Loads the AmigaOS ROM from an EFI-compliant storage device using EFI_BLOCK_IO_PROTOCOL and EFI_SIMPLE_FILE_SYSTEM_PROTOCOL via Emu68.
Initializes basic system state, including memory mapping, hardware detection, and CIA chip emulation.
Uses EFI-provided input protocols (keyboard/mouse) for interaction during boot, if required.
Transitions control to the loaded AmigaOS kernel.
ROM Loading and Initialization:

Implement a ROM loading mechanism to:
Locate and load the AmigaOS ROM file from storage.
Set up a compatible memory environment for AmigaOS execution.
Use EFI-provided framebuffer graphics (via GOP) to display basic output during boot.
Initialize key hardware interfaces such as storage, input, and display for AmigaOS compatibility.
Emulation of Missing Hardware:

CIA Chip Emulation:

Emulate the missing CIA chips within the bootloader. The CIA chips are responsible for essential hardware interactions like keyboard input, timers, and other system-level I/O tasks. This emulation must mimic the behavior of the original CIA chips to ensure compatibility with AmigaOS.
Display Support:

Emulate display support for AmigaOS, either by:
Using the GOP framebuffer for basic display output.
Optionally simulating Amiga-native graphics modes (PAL/NTSC) by:
Emulating graphics.library functionality in the bootloader to present the framebuffer as a native mode.
Creating a minimal P96 GOP driver for direct rendering.
AmigaOS Transition:

Finalize hardware initialization and transfer control to the AmigaOS kernel, ensuring that:
The kernel has access to hardware details provided by EFI protocols.
A pre-initialized environment for storage, input, and graphics is set up.
Document the handoff mechanism for compatibility with AmigaOS expectations.
Compatibility Testing:

Test the bootloader and overall environment using real Amiga applications, particularly Deluxe Music 2.0, to verify hardware compatibility and proper operation.
Identify and resolve any issues related to hardware initialization or emulation (e.g., CIA chip behavior, input handling, display modes).

Deliverables:

68K Bootloader Program:

A secondary bootloader program running under Emu68 capable of:
Loading and initializing the AmigaOS ROM.
Performing essential hardware initialization, including CIA chip emulation and display emulation.
Transitioning control to the AmigaOS kernel.
Graphics Output:

GOP-based framebuffer graphics support during boot.
Optional support for simulated Amiga-native modes via graphics.library emulation or a P96 GOP driver.
Hardware Abstraction:

Initialization of storage, input, and graphics hardware using EFI protocols.
Accessible tables or structures for AmigaOS to use initialized hardware.
Emulation of CIA Chips and Display:

Emulation of CIA chip functionality in the bootloader.
Display emulation through GOP framebuffer or simulated Amiga-native modes.
Testing and Compatibility:

Verification of the bootloader functionality using Deluxe Music 2.0 and other critical Amiga applications to ensure compatibility and correct operation.
Resolution of any issues identified during testing.
Documentation:

Detailed documentation covering:
Bootloader functionality and setup.
ROM loading and hardware initialization processes.
Mechanism for CIA chip emulation and display emulation.
Transitioning control to the AmigaOS kernel.
Compatibility considerations and testing procedures.

Last edited by terminills on 22-Dec-2024 at 01:15 AM.
Last edited by terminills on 21-Dec-2024 at 05:49 PM.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

Aros 68k or AmigaOS running on ARM-Hardware with only emu68 as layer would give unbeatable cheap and powerful hardware. Nice new toys

@OlafS25

Would be really something else! A second renaissance

_________________
Indigo 3D Lounge, my second home.
The Illusion of Choice | Am*ga

@pixie



I have this.

but I'm looking into upgrading to this.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

The DraCo method requires CIA chips and extra ROM to patch KickStart 3.1 ROM.

UEFI Emu68 would need to patch KickStart 3.x ROM for missing CIA and display.

I use Deluxe Music 2.0 as one of the test apps against the so-called Amiga wannabes.

Last edited by Hammer on 22-Dec-2024 at 01:01 AM.
Last edited by Hammer on 22-Dec-2024 at 12:55 AM.

_________________
Amiga 1200 (rev 1D1, KS 3.2, PiStorm32/RPi CM4/Emu68)
Amiga 500 (rev 6A, ECS, KS 3.2, PiStorm/RPi 4B/Emu68)
Ryzen 9 7950X, DDR5-6000 64 GB RAM, GeForce RTX 4080 16 GB

@Hammer

EMU68 isn't going to be expanded for that purpose. That's the purpose of a secondary bootloader. I will however adjust the AmigaOS bounty accordingly. AROS however has no need for CIA emulation or to patch the Kickstart ROM. That's the point of separating the bounties as much as possible.

Last edited by terminills on 22-Dec-2024 at 01:17 AM.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

Love the list.

Are you planning to run the AROS bounties sequentially or in parallel?

_________________
All the way, with 68k

@agami

Quote:

@terminills Love the list. Are you planning to run the AROS bounties sequentially or in parallel?

Parallel as they don't need to be done sequentially. AROS EFI enhancements will help AROS as a whole, EMU68 doesn't need AmigaOS or AROS to be enhanced. The only one that may have to wait is the AmigaOS bootloader.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

Pity that there are no bounty about SVGA3D II for AROS and Gallium support via VMware

_________________

@Seiya

Quote:

by Seiya on 22-Dec-2024 13:22:21 Pity that there are no bounty about SVGA3D II for AROS and Gallium support via VMware

That is not the scope of what I'm trying to accomplish at this point.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

Quote:

terminills wrote: @Hammer EMU68 isn't going to be expanded for that purpose. That's the purpose of a secondary bootloader. I will however adjust the AmigaOS bounty accordingly. AROS however has no need for CIA emulation or to patch the Kickstart ROM. That's the point of separating the bounties as much as possible.

AROS 68K fails the Deluxe Music 2 test.

_________________
Amiga 1200 (rev 1D1, KS 3.2, PiStorm32/RPi CM4/Emu68)
Amiga 500 (rev 6A, ECS, KS 3.2, PiStorm/RPi 4B/Emu68)
Ryzen 9 7950X, DDR5-6000 64 GB RAM, GeForce RTX 4080 16 GB

@Hammer

Quote:

AROS 68K fails the Deluxe Music 2 test.

Then the AROS portion isn't for you. It is however for those who want to see AROS get used more so it can get fixed.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@Hammer

is that a official benchmark?