Skip to content

Conversation

@Jarvik7
Copy link
Contributor

@Jarvik7 Jarvik7 commented Feb 21, 2024

This is primarily regarding the hashes for bioses.
Currently the hashes are all smashed into a single notes line, which is hard to parse programmatically, and even harder to visually confirm that it is complete (many bios are missing hashes)

This is the first step of an intended cleanup with the end goal of having hashes for all bios, and separately a programmatically generated .dat file for each platform to enable users to easily gather the required bios (and only the required bios) for their platform.

Roadmap is as follows but there should be nothing stopping the immediate commit of this PR.

Roadmap:

  1. Move hashes from notes line into separate firmware#_md5 or firmware#_sha1 lines for each bios definition
  2. Create python script to generate master system.dat from folder of .info files
  3. Add missing bios hashes and switch to sha1
  4. Create additional python script to generate a platform-specific system.dat, e.g. dat for bios needed on cores for PSV retroarch build. This will use platform recipes to select the .info files to use

Clean up by moving into an item under each firmware definition instead of all crammed into the notes.
@fpscan
Copy link
Collaborator

fpscan commented Feb 24, 2024

Can you also do the samething here: https://github.com/libretro/libretro-core-info

@RobLoach
Copy link
Member

Always a fan of more cleanup in these info files.

Move hashes from notes line into separate firmware#_md5 or firmware#_sha1 lines for each bios definition

Is this change supported by RetroArch currently? I haven't seen many .info files using this new format.

Can you also do the samething here: https://github.com/libretro/libretro-core-info

That's just a mirror of this, so likely best to handle it here first.

@RobLoach
Copy link
Member

RobLoach commented Jan 4, 2025

Looks like there's some conflicts now. Always good to clean these up.

Comment on lines -40 to +42
description = "A port of the YabaSanshiro Saturn emulator, which is itself a fork of the venerable Yabause emulator, to libretro. This core is less accurate than Beetle-Saturn core but it runs much faster and has some nice cosmetic features, such as increased internal resolution. Users with more powerful devices who still want cosmetic improvements should usually try the Kronos core first and only fall back to this core if they are unable to maintain full speed."
notes = "Homepage : http://www.uoyabause.org/"

description = "A port of the YabaSanshiro Saturn emulator, which is itself a fork of the venerable Yabause emulator, to libretro. This core is less accurate than Beetle-Saturn core but it runs much faster and has some nice cosmetic features, such as increased internal resolution. Users with more powerful devices who still want cosmetic improvements should usually try the Kronos
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the end got cut off here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants