The 5.7.1 version has a couple of regresions (one is a crash), fixed in version 5.7.2. However, DispmanX support was dropped starting with 5.7.2 so just bumping the version would break Buster based Pi installation.
Therefore the module was changed so that:
- for DispmanX platforms cherry pick the post 5.7.2 fixes manually and lock the version to 5.7.1
- for every other platform build the 5.7.2 version
Changes in 5.7.1 (https://github.com/BlitterStudio/amiberry/releases/tag/v5.7.1)
* Bugfixes (since 5.6.6):
- improve CD32 default mapping
- fix base color for Radiobuttons in SaveStates panel
- fix KMSDRM video regression
- fixed background color for SaveStates panel checkboxes
- when saving a new config in the GUI, it should be selected after the refresh
- when loading config from the command line and opening the GUI, the settings were reset to defaults
- always clear the text fields when deleting a config
- fullscreen toggle didn't quite work
- quickstart - enabling 2nd floppy drive did not refresh panel
- make guisan widgets active/inactive status more visible
- fixed textbox background color in Create hardfile dialog
- the floppy dropdown wasn't updated properly after a selection
- fixed CD dropdown did not refresh properly
- ensure keyboard keys are released when pressing Alt-Tab
- ignore alt-tab if used to release focus
- GUI Hardware sprite checkbox wouldn't enable when needed
- some RTG options were not changed on-the-fly
- fix mouse drift when using RTG hardware sprite
- mouse - when using SuperHighRes or Single line modes, the movement scaling was incorrect
- fix offset for button indicators in ControllerMap GUI
- mouse: RTG modes can use the positioning directly, but they were affected by the single/double line mode setting, fix absolute positioning
- fixed crash when using Restart after previous updates
- Ensure changes in virtual mouse and magic mouse are applied immediately
- datapath wasn't parsed in WHDBooter
- bugfix: aspect ratio option was not respected in autocrop
- bugfix: return empty string when cancelling file/folder dialog
- fixed select file/folder dialogs briefly showing a scrollbar on startup
- enter would no longer trigger a KEYDOWN event in guisan
- fix memory leak when closing filesys unit
- fixed parsing of ROMs in the GUI
- don't crash if no kickstarts are found on startup
- controller hotkey mapping was broken after recent updates
- fixed navigation in Floppy GUI panel
- fix all A600 quickstart configs would always incorrectly add Fast RAM
- start in Quickstart checkbox would not change status
- virtual Keyboard did not respect Auto-Crop
- listbox selection color was hardcoded when inactive
- if Cancel was used in a file/folder dialog, the path would be emptied on return
* Enhancements:
- Implemented GUI foreground color option for themes
- Updated floppybridge library to latest version
- Added button to Create new folder in the dialogs
- All plugins (floppybridge, capsimg) now live in a separate directory, named "plugins"
- Added option to log to console
- Set config name automatically for CD images as well
- Config panel double-click time reduced to 500ms
- Improve help text in Config panel,Misc panel,Sound Panel
- Add console logging details in GUI helptex
- Added new custom events for Disk Swapper. Two new events were added, Insert Next/Previous disk swapper slot.These allow you to select the next/previous slot and also insert it into DF0: in one step.
- Added default path for LHA archives. This allows you to set a default path that will be used to load WHDLoad .lha files, for use with the WHDBooter.
- Added default Floppy, CD-ROM and Hard Drive paths
- Added option to use "System Default" audio device.This new checkbox in the GUI (Sound panel) will not choose a specific audio device, and instead tell SDL2 to pick the system default one. This helps with systems that may have sound devices that are not listed in the dropdown.
- Added new WHDLoad panel in GUI. This panel exposes the options that the WHDBooter uses, and allows changes to the slave options before launching a title. The Custom Fields can also be customized from this area. All information is parsed from the same XML that Amiberry uses to match the WHDLoad titles.
- Added new "Save Mapping" button in Custom Controls.This allows you to save the current mapping for the selected controller as the default, which will be automatically loaded on startup (if the controller is connected).
- Detect WHDLoad, CD and floppy disk images as parameters in the command line. As a fall back, you can now pass the path to a supported image filename, and it will be loaded automatically. This makes it possible to set Amiberry as the default handler for such files (e.g. .lha, .adf, .adz, .ipf, .cue, .iso, etc.). WHDLoad and CD images trigger the autoloader, while floppy disk images will be loaded into DF0:
- If a config file that matches the inserted disk image exists, it will be loaded automatically. Otherwise the default one will be used instead. This also makes it easy to save a config after you've loaded a disk image, since the panel will be populated with the right name already.
- Added support for custom font colors in the GUI theme
Release notes - https://github.com/BlitterStudio/amiberry/releases/tag/v5.6.0
Changelog for 5.6.0, with modifications added after 5.5.1.
* New features
- implemented On-Screen Virtual Keyboard
- added VKBD retroarch mapping support and VKBD default toggle key
- updated game controllers db to latest version
- decrease mouse map sensitivity on joystick handling
- added new default options in amiberry.conf
- added Warp reset option in Misc Panel
- GUI improvements
- implemented turbo boot option
- added 1024x600 RTG resolution
- allow on-the-fly change of virtual mouse driver
- increased width of dropdowns in Input Panel
- automatically center GUI window when opening
- updated WHDLoad XML to latest version
- updated game controllers db to latest version
* Changes
- refactored input event handling to minimize latency
- rewrite Serial port support, using libserialport
- refactored controller input logic
- decrease mouse map sensitivity on joystick handling
- added more logging during retroarch event handling
* Bugfixes
- fix "default" button setting not fully enabling CD32 pad mode when CD32 was configured.
- detection of hotplug controllers didn't work after 5.4
- restart would cause crashes sometimes
- fixed controller axis should be separate from joystick axis handling
- memory pattern would cause graphics glitches in some cases
- virtual keyboard now works with CD32 mode as well
- fixed crash if something triggered a CPU HALT3
- fixed various compiler warnings
- revert custom, blitter and drawing to WinUAE 4.4.0 standard
- improve scrolling smoothness under 50Hz
- don't use SDL_Quit until we actually quit Amiberry
Update amiberry version to v5.1 tag
Remove no longer needed libxml2-dev dependency
Add patch for amiberry Makefile so it doesn't override our CFLAGS/CPPFLAGS/LDFLAGS
Remove -O3 from Makefile so it uses our default optimisation level. Previously this was -Ofast but from my own testing -O2 with our compiler flags works best.
Modify build_amiberry with updated paths for caps bootstrap/configure. Override CPUFLAGS for amiberry, so our flags are used, rather than the ones hard-coded into the Makefile.
Include abr and kickstarts folder in install_amiberry. The kickstarts folder includes a freely distributable AROS rom, so let's include it.
Symlink cd32.nvr from "$md_inst/data" to "$md_conf_root/amiga/amiberry" so it's writable by amiberry.
Split uae4arm's shared configure function out so uae4arm and amiberry now only share the launcher code. There is a small amount of duplication with some folder creation in configure_amiberry but it makes sense to split them due to the new amiberry changes.
Rework uae4arm/amiberry configure functions to simplify logic and remove nesting by changing order of calls.
Change the addEmulator calls in uae4arm and amiberry due to parameter ordering changes in the shared launcher script.
Move rom location for amiberry/uae4arm/uae4all to $biosdir/amiga
Create update hook to move / symlink kickstart ROMs from $biosdir to $biosdir/amiga
Add .lha to module description extensions
Added .chd extension to platforms.cfg
Rework the logic in the shared launcher script:
* Instead of setting EMULATOR variable via sed in uae4arm/amiberry we just change "use_amiberry=0" to "use_amiberry=1" in configure_amiberry.
* Argument ordering is changed to simplify the logic. Previously the launch script expected [CONFIG] [ROM/GAME], and setting [CONFIG] to auto or "" would handle it automatically. Now it uses [ROM/GAME] [ARGS]. As passing in a configuration was optional, it made it simpler just to have the ROM first, and then allow additional arguments to be sent to the emulator.
* We now build up an parameters array which avoids duplication and simplifies the code - There is only a single call to launch uae4arm/amiberry with the processed parameters.
* Switched to using the amiberry --model parameter over our previous rp-a500.uae/rp-a1200.uae configs. Users who have set a particular rom to use amiberry-a500/amiberry-a1200 will still get the same functionality but it will instead use --model A500/A1200. A per rom .uae config can still be saved with customised settings for an adf etc.
* added support for .chd files for amiberry
How uae4arm.sh handles launching:
* If the first argument (ROM/GAME) is a .cue or .lha file, and we are launching amiberry, use amiberry's --autoload function.
* Otherwise if a rom argument is present, see if it's an archive (only zip supported currently). If it is, unpack all known disk image extensions from the archive attach each one as floppy drive arguments (-0 / -1 / -2 etc)
* If it's not an archive, treat it as a disk image itself, and try and find additional files starting with the same name (eg Game_Disk1/Game_Disk2) and attach them as floppy drive arguments.
* We then check if there is a .uae config file with the same name as the ROM argument in the ROM's folder or in amiberry's conf folder.
* If there isn't we will try and use a config based on the filename. For uae4arm it will use the pre-installed rp-a500.uae config by default and rp-a1200.uae for any files containing AGA or CD32. For amiberry we use the --model parameter which chooses a default config based on argument. By default we use A500, but switch to A500P if a file contains ECS and A1200 if a file contains AGA, and CD32/CDTV if those strings are included also (Although cd images are handled separately so this may not be too useful).
* We always set -G to not show the GUI when the first argument is present - to override this the first argument can be blank and manual parameters can be used (or the amiberry executable can just be used directly)
* sdl1 is now removed - use sdl2 + dispmanx for rpi1/2/3
* simplify platform / bin logic
* don't use sdl1 dependencies from uae4arm / dependency logic cleanup
* remove Makefile CFLAGS patch - uses CPUFLAGS now and they are needed for GNU as
* no need for symlink as final binary is now called amiberry for all platforms
