mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ash Logan <ash@heyquark.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: arnd@arndb.de, christophe.leroy@csgroup.eu,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	officialTechflashYT@gmail.com, AWilcox@wilcox-tech.com,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: 32-bit HIGHMEM and game console downstreams
Date: Tue, 16 Sep 2025 12:10:14 +1000	[thread overview]
Message-ID: <95d176d1-e1be-4594-91bd-caf0d68fd532@heyquark.com> (raw)
In-Reply-To: <aMbNwBrxtBSPl8NQ@gate>

On 15/9/25 00:14, Segher Boessenkool wrote:

Hello!

> On Sat, Sep 13, 2025 at 08:53:08PM +1000, Ash Logan wrote:
>> Wii (2006)
>> - 1x PowerPC 750CL "Broadway" @ 729MHz
>> - 24MB "MEM1" + 64MB "MEM2" (non-contiguous - MEM2 starts 256MiB in)
>> - Kernel 4.19 (+ CIP patchset), dev has been working on forward-porting all
>> the drivers one major version at a time (he's currently up to 5.15 last I
>> checked) + limited upstream support (hardware bringup, UART, not many
>> peripherals)
> 
> There *aren't* many peripherals, so that is quite okay :-)

That's true. The lack of a UART or similar does make USB kinda essential 
for an input device in my opinion, though getting it working is 
Complicated for DMA reasons. (I think this is the main thing holding the 
downstream back in their rebasing efforts)

>> Wii U (2012)
>> - 3x PowerPC 750CL "Espresso" @ 1.2GHz
> 
> It is not a 750CL.  We never found out what the model # is, if indeed it
> has one!  But the CPU cores are compatible to the Broadway, sure, there
> even are configuration bits to make it do the bugs that were fixed in
> Espresso!  (Just like Broadway can emulate a Gekko, 750CXe, the GCN
> thing).
> 
> It does have its own PVR value of course, that is something at least :-)
> 
> (Espresso is one chip btw, with three mostly symmetrical cores).

Yeah, I was just going for the closest "public" chip :) I think the PVR 
is closer to the CXe too, but all the HIDs, missing THRM, missing 
frequency scaling - it's very CL-y...

>> - 32MB "MEM1" + 2GB "MEM2" (also starts 256MiB in) + various small SRAMs
> 
> It has 32MB MEM1?  Huh.  Why?

New generation upgrade? MEM1 does get used for Wii U software too, 
usually to keep framebuffers and other 3D things, so I guess they wanted 
just a little more for all the 1080p buffers the new console juggles.

>> Distribution-wise, we're supported by ArchPOWER [5], Adélie Linux [6], and
>> other distros. The Wii U's Espresso has CPU errata requiring a patched
>> compiler,
> 
> Can you remind me what that is about?  It shouldn't be too hard to
> include it in mainline GCC.

The short version is "every stwcx. should be prefaced with a dcbst" - 
something to do with bus snooping (store-with-flush, store-with-kill) 
I'd guess. I have some GCC patches drafted (activated by -mcpu=espresso) 
here: https://gitlab.com/linux-wiiu/smp-patches

I'm impressed by how often IBM stuffed up atomics during this 
generation. The Xbox 360 has an extremely similar issue despite being an 
entirely different lineage of chip. No surprise the console vendors all 
went to x86 and ARM right after, I suppose.

Thanks,
Ash

  reply	other threads:[~2025-09-16  2:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 10:53 Ash Logan
2025-09-13 13:52 ` Arnd Bergmann
2025-09-16  1:57   ` Ash Logan
2025-09-16  6:20     ` Arnd Bergmann
2025-09-16  7:00       ` Willy Tarreau
2025-09-16  9:13         ` Arnd Bergmann
2025-09-16 16:58     ` Segher Boessenkool
2025-09-14 14:14 ` Segher Boessenkool
2025-09-16  2:10   ` Ash Logan [this message]
2025-09-16 15:41     ` Segher Boessenkool

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95d176d1-e1be-4594-91bd-caf0d68fd532@heyquark.com \
    --to=ash@heyquark.com \
    --cc=AWilcox@wilcox-tech.com \
    --cc=arnd@arndb.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=officialTechflashYT@gmail.com \
    --cc=segher@kernel.crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®