Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split flashfloppy into a library and an app ? #819

Open
bog-dan-ro opened this issue Aug 25, 2023 · 1 comment
Open

Split flashfloppy into a library and an app ? #819

bog-dan-ro opened this issue Aug 25, 2023 · 1 comment

Comments

@bog-dan-ro
Copy link

bog-dan-ro commented Aug 25, 2023 •
edited
Loading

I'd like to port flashflopy to Raspberry Pi Pico (RP2040) and I wonder if isn't better to split flashfloppy into two components:

  • a platform agnostic library. This library can be used to build other apps for other platforms.
  • and the application for Gotek.
@keirf
Copy link
Owner

keirf commented Aug 25, 2023

Perhaps. Certainly there are ad hoc interface boundaries in FlashFloppy already:

  • Gotek vs "other" boards: To allow wiring / pin assign differences. Only Gotek is currently supported though.
  • Different MCUs, 105/415 vs 435. All STM32-centric though

No doubt RP2040 would need some different interfaces to abstract the STM32 specific stuff. The easiest first step is to hack in support for RP2040 and see where those boundaries lie, and clean it up after it's working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@keirf @bog-dan-ro