Conversation

and

From a usability p.o.v. I'd skip the FM and go with a sample player. Think Amiga tracker.

Replying to

I have nothing! I plan to interface primarily over SPI, though I'm happy to plunk down an STM32G0 "coprocessor" to handle the management of whatever codec. I actually have no amiga exp., and only vaguely know how trackers work. Also I don't have SDcard yet, so not much space.

Replying to

Wait half a year I might be able to hand you over an engine :-)

Replying to

Nice! I actually can load (well, load a single fixed program) and run userspace programs now, so I'm getting closer to something that could be fun to hack on :)

Replying to

Can it host C code?

Replying to

Yes, though the syscall serialization only really supports Rust, but it'd be easy to make rust FFI shims (and build as a staticlib) for that part, or hand-build/decode the format yourself. If that's something that you'd be interested in, I can do it quickly for you.

Replying to

Oh yes. For various reasons. This being one: zwizwa.be/rai/ I plan to revive for upcoming synth work.

Replying to

Sure, gimme a min.

Replying to

and

Okay, more like an hour, but most of that was writing docs. Just for you: github.com/jamesmunns/pel

Replying to

and

I don't expose the allocator yet (64KiB), so you'll have to do your own memory management in the 128K of space you have. But I do plan on supporting that soon, or at least automatically mapping the unused space out of 128K to be a user heap with a syscall interface.

Tom Schouten

Replying to

5:29 PM · Apr 7, 2022Twitter Web App

Not an issue for me at this point. Thanks for the patch. I'll send word when I have something going. Hope to get to it tonight. Time for emergency nap first :-)

Replying to