cakehonolulu
Absolutely. I even call that out on the post itself. Couldn't agree more.
The issue for me is that I'm a complete novice when it comes to buying speakers, like I'm not even sure what you need to "look" into them so you get the best bang for your buck (And also taking into consideration where you'll end up placing them and all that). That's the main reason behind me not owning an AVR already.
I'm actually looking forward into owning an AVR and starting "simple" (Subwoofer, central speaker and 2x fronts) but I kinda want to future-proof a bit (I'd like 5.1, at least, in the future) so I'm eyeing what are the better options for me to buy in terms of hardware.
I really value having the "freedom" of having more codecs available to work with (Soundbars aren't great for that), but I wanted something "simple" for the time being before I do the actual jump to an AVR.
Interestingly enough my father used to have a 5.1 setup with a Yamaha AVR in the '00s and he told me he was able to go to a specialized store where they let him test a myriad of speakers so he could customize the sound "flavor" to his liking; but seems it's closed and I'm a bit nervous spending money on something I can't hear...
Oddly enough (At least in my model) the ‘trigger’ to setup the universal remote is within the ‘input sources’ menu?
Banter aside; I was basically on a tunnel-vision/nerd-snipe/however you want to call it to get it to run; GCC report is still coming. It’s just that I’ve never sent out (a report) to them (gcc) and wasn’t really sure how to proceed (Even though they give out a pretty step-by-shep guide) so I wanted to finish the bringup and then try to make some easy reproduction code (That’s not compiling Linux, that is).
I actually have a comment on GH from one of the many cool people that’s (I think?) maintaining the GCC backend for SuperH.
TL;DR: It’s coming.
I do recall having a RAM expansion cartridge in mine that could possibly be used to fit more stuff if the main 2MBs it had were too little to hold Linux.
You got me thinking…
Regardless, I don't really know if there's the notion of an SMP-enabled m68k board based on Linux so I would not really know where to start.
For SuperH, I've gotten very lucky because there's a single CPU subtype (J2, https://j-core.org/) which has SMP tidbits that helped me understand what to look for and where in terms of wiring the 32X's CPU subtype.
The branch delay slots/load delay slots thing was also something that plagued some MIPS processors back then too; 5th generation of consoles (At least, from Sony, Nintendo and Sega) had either all or a subset of those quirks on their flagship machines.
Yes so, this was tested within a software context; the ASIC that does the bus arbitration on the side of the 32X has some of the required pins as N/C. They do a much more interesting deep-dive on the link you added.
I initially thought the 68000 side /UWR & /LWR pins were wired to the complimentary 315-5818 ones (Since there wasn't any apparent difference between the pinouts of both).
This makes the setup a bit different since you'd not be addressing the cart's PSRAM, but instead, the 32X's SDRAM. With XIP (Like on the Jaguar port) you could probably pull it off (Not sure if you'd be able to cram the entire Busybox environment but maybe a small program could do it).
Good thing is, this is actual Linux (And not uCLinux) so there's still stuff that can be disabled further if for some reason it can't fit still on the available memory.
The BogoMIPS value is derived from a calibration that Linux does against the timer of choice so it could very well be a reason why.
There's really clever ways you can get down to scratch that space-saving itch; I'm not knowledgeable about it either (I'm just really bad when it comes to analog signals) but if you really, really needed to shave off even more stuff; I reckon that the video console driver could possibly be reduced to something far more esoteric (That'd need signal processing to get tangible output of). But at that point, just use UART (Which is simple-enough already and should not really starve you out of much memory).
Honestly, no idea if Krikkz's Extended SSFv2 is even implemented on MiSTer. I'd have to check but considering the rarity of it I'd be surprised if it was there.
Porting Linux to SH3 is surely easier than what it has been for SH2 (SH7604, more precisely); and considering it has 512MB of RAM you probably can just get away with a non-stripped to the bones Linux image (And initramfs, of course). It surely sounds like a good playground.
As to the Sega CD; it'd probably be cool but this is already super-slow as it is (There's lots of bus contention already from 2 x SH2s and 1 x 68000) so yeah.
Maybe a cool project would be SMP for the 2 68000s (Sega CD + Genesis) but I'm not even sure if there's any form of SMP available for arch/m68k in Linux (If both 68000s are wired you could maybe get away-ish with some simple bringup but can't really say for sure).
Linux on the Sega 32X. Who needs hardware synchronization primitives anyway?
In theory it should be possible I think?
I don't exactly recall the memory differences (Chip RAM vs Fast RAM and all that) but assuming you have enough Chip/Fast RAM and thereabout of a megabyte in a storage medium for the actual kernel binary; I don't see why it should not be possible.
If WHDLoad is a thing on base 500/500+ then you'd be able to fit more stuff on the "userspace" side of things, since 1.44 megs can't really hold much (And having to swap floppies in the way Workbench does it is not something I'm sure can be done on Linux).
The main issue I see is that you'd probably need to "free" up memory by unloading Workbench (If it's loaded) and possibly re-configuring the hardware (So it's in a known good state for Linux), but yeah; it should honestly be feasible.
As for the mainline stuff: Sure! May I reach out to see how I can help?
As for 80 columns... I'd probably need to choose a different (Narrower) font. With a bit smaller font I reckon it should be feasible to have it (Since current one has 8x8 glyphs).
In theory it should be feasible but I'm not too sure how you'd "adapt" the way of doing things within Linux; the environment is very limited and I can't think of a way to cleanly make the Tom more "accessible" (While again, Tom is already executing the object lists to drive the Linux console). Doesn't help that it'd need additional afterthought not to trip it up with one of the many hardware erratas both Tom & Jerry had...