Skip to content

Better encapsulation of various Voodoo I/O spaces #7751

@angelosa

Description

@angelosa
Member
  • Voodoo(s) I/O space is really a switch-case hell with [[fallthrough]];, device id checks and offset-based register areas. A typical case where having progressive inheritance can help with readability and maintenance.
    PCI space is very stub, needs to be separated for each variant type;
    Voodoo Banshee/Voodoo 3 VGA portion should use the common architecture instead of reinventing the wheel;
    Voodoo Rush support cfr. ProMotion cards

Activity

added
deviceDeprecated label, use `<realm> device` labels instead.
legacycode bitrot from C era
on Feb 6, 2021
self-assigned this
on Jun 22, 2021
angelosa

angelosa commented on Feb 27, 2024

@angelosa
MemberAuthor

Break down OP message into tasks.

removed their assignment
on Feb 27, 2024
added and removed
deviceDeprecated label, use `<realm> device` labels instead.
on May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    To do

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @aaronsgiles@angelosa

        Issue actions

          Better encapsulation of various Voodoo I/O spaces · Issue #7751 · mamedev/mame