linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ash Logan <ash@heyquark.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Christophe Leroy <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,
	"A. Wilcox" <AWilcox@wilcox-tech.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: 32-bit HIGHMEM and game console downstreams
Date: Tue, 16 Sep 2025 11:58:02 -0500	[thread overview]
Message-ID: <aMmXGjT6Nne708Xc@gate> (raw)
In-Reply-To: <11e667d6-2210-47f0-a9ec-a134a60e138c@heyquark.com>

On Tue, Sep 16, 2025 at 11:57:00AM +1000, Ash Logan wrote:
> On 13/9/25 23:52, Arnd Bergmann wrote:
> > The smaller devices are probable getting problematic sooner, 96MB
> > in the Wii is already really tight and this only gets worse over
> > time.
> 
> The maintainer of that downstream claims to be able to boot modern text-mode
> distros on the GameCube' 24MB, which I find really impressive!

Hey, I still boot up my imac G3 sometimes (if I can find a keyboard for
it!), it has 64MB of RAM and that needs some handholding to boot already
(the zImage needs some manual header editting to fix its load address,
something like that).

But booting it does :-)

> > Just to be clear: there is no general 32-bit deprecation going on. When
> > I talked about phasing out 32-bit platforms over time, that is purely
> > going to be those that have no users left, or the few ones that are
> > causing more work than they are worth. E.g. The ppc405 ones got
> > removed recently (after many years of discussion) because they were
> > making ppc440 maintenance harder and had no known users.

Good good good.  Way too reasonable!

Thanks,


Segher


  parent reply	other threads:[~2025-09-16 16:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 10:53 32-bit HIGHMEM and game console downstreams 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 [this message]
2025-09-14 14:14 ` Segher Boessenkool
2025-09-16  2:10   ` Ash Logan
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=aMmXGjT6Nne708Xc@gate \
    --to=segher@kernel.crashing.org \
    --cc=AWilcox@wilcox-tech.com \
    --cc=arnd@arndb.de \
    --cc=ash@heyquark.com \
    --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 \
    /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;
as well as URLs for NNTP newsgroup(s).