cakehonolulu

> you’re getting a product that is handicapped by physics (and cost).

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.

100% agree. It was merely a pun, I do actually enjoy reading through some of the posts there.

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...

I actually recall seeing an option on my TV to set up the Samsung remote as a ‘universal’ controller. I haven’t had the need to do so because I have a Philips Sync Box that handles HDMI-CEC for me (So I can basically use the TV’s controller on the devices connected to the Sync Box).

Oddly enough (At least in my model) the ‘trigger’ to setup the universal remote is within the ‘input sources’ menu?

Exactly. I in part, chose this setup to avoid running cables; I figured that technology has come a long way… but here we are unfortunately.

Yeah… fair enough. I’m honestly a noob when it comes to TV/Audio equipment so it doesn’t surprise me that I picked one of the worst brands out of the bunch… hah!

How I found out I could get a 2026+ TV feature working on a (Year) older one and a few other rants.

Aha! You got me ;)

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.

It does require an MMU technically, this kernel is built with that in mind but I see no mention of uCLibc whatsoever on the kernel log (Or that I remember out of all the files I saw open). I’ll see if I can pinpoint exactly what it is.

I was actually thinking, if memory is the bottleneck; I could always go with the Saturn instead (Or find a way to have the 32X catridge writes go through…; but I’m no EE unfortunately).

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…

I actually didn't know the THUMB thing; pretty interesting stuff...

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.

Hi! Nice to see you here.

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.

That was something I also noticed; I can't say for sure (Since I haven't yet checked) but I feel like I may have done something incorrect when wiring the FRT (The timer) to the secondary, smp-enabled SH2.

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.

Not a silly question actually.

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).