Refactor BIO2 emulation similar to acioemu #24

Closed
opened 2019-09-28 20:15:32 +03:00 by icex2 · 5 comments
icex2 commented 2019-09-28 20:15:32 +03:00 (Migrated from github.com)

In GitLab by @xyen on Sep 28, 2019, 19:15

DDR X64, IIDX 25+, SDVX V, and DRS all use BIO2.

Rather then having the bio2emu code inside each instance, should really factor it out, and share it similar to acioemu.

The devices should be kept to each game though, since they're all identified as BI2A.

In GitLab by @xyen on Sep 28, 2019, 19:15 DDR X64, IIDX 25+, SDVX V, and DRS all use BIO2. Rather then having the bio2emu code inside each instance, should really factor it out, and share it similar to acioemu. The devices should be kept to each game though, since they're all identified as BI2A.
icex2 commented 2019-09-28 23:32:48 +03:00 (Migrated from github.com)

Hint: The ezusb layering architecture might serve as another reference for a design that helps sharing the common parts. It introduces a device layer (which in your case is acio), the ezusb protocol layer (firmware flashing, vendor request handling) and the message layer (currently only iidx mesage handling implemented but prepared for popn IO2 as well).

Hint: The ezusb layering architecture might serve as another reference for a design that helps sharing the common parts. It introduces a device layer (which in your case is acio), the ezusb protocol layer (firmware flashing, vendor request handling) and the message layer (currently only iidx mesage handling implemented but prepared for popn IO2 as well).
icex2 commented 2019-09-29 00:19:46 +03:00 (Migrated from github.com)

In GitLab by @praxis on Sep 28, 2019, 23:19

I have some preliminary work on this that follows a roughly similarly layout, to be subject to some due improvements.

In GitLab by @praxis on Sep 28, 2019, 23:19 I have some preliminary work on this that follows a roughly similarly layout, to be subject to some due improvements.
icex2 commented 2019-09-29 00:36:37 +03:00 (Migrated from github.com)

Feel free to open a PR with a "[WIP]" in the title and describe what you have worked on so far. You can continue an keep pushing/updating this PR and update us in the comments as you continue working on it. This gives us visibility that someone is already taking care and what's the progress on it. You can ask for feedback about specific parts of your code or existing code.

Feel free to open a PR with a "[WIP]" in the title and describe what you have worked on so far. You can continue an keep pushing/updating this PR and update us in the comments as you continue working on it. This gives us visibility that someone is already taking care and what's the progress on it. You can ask for feedback about specific parts of your code or existing code.
icex2 commented 2019-10-12 21:40:52 +03:00 (Migrated from github.com)

In GitLab by @xyen on Oct 12, 2019, 20:40

@praxis this is in master now, should be relatively easy to refactor any work that relied on similar layouts.

If you have any questions lemme know.

In GitLab by @xyen on Oct 12, 2019, 20:40 @praxis this is in master now, should be relatively easy to refactor any work that relied on similar layouts. If you have any questions lemme know.
icex2 commented 2019-10-12 21:40:52 +03:00 (Migrated from github.com)

In GitLab by @xyen on Oct 12, 2019, 20:40

closed

In GitLab by @xyen on Oct 12, 2019, 20:40 closed
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Max/djhackersdev_bemanitools#24