linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 linux-m68k <linux-m68k@vger.kernel.org>,
	 debian-68k <debian-68k@lists.debian.org>,
	 James Le Cuirot <chewi@aura-online.co.uk>,
	Sam James <sam@gentoo.org>,
	 Geert Uytterhoeven <geert@linux-m68k.org>,
	 Andreas Schwab <schwab@linux-m68k.org>,
	Thorsten Glaser <tg@mirbsd.de>
Subject: Re: Plan needed for switching m68k to 32-bit alignment
Date: Tue, 29 Oct 2024 14:39:15 +1100 (AEDT)	[thread overview]
Message-ID: <de1adc92-f1e9-81fd-9406-7148e8213e4c@linux-m68k.org> (raw)
In-Reply-To: <832d65f2-1796-4ac1-b49b-380bf64700f4@gmail.com>


On Tue, 29 Oct 2024, Michael Schmitz wrote:

> On 25/10/24 22:55, Arnd Bergmann wrote:
> 
> > I also expect that a lot of users (of m68k kernels) are never going to 
> > get the benefits as they are already stuck on older userspace because 
> > of added bloat in new software releases. I assume you have better 
> > understanding than me of what m68k hardware is commonly used these 
> > days, and how constrained that is in practice.
> 
> I second that - currently bisecting to find out what makes my extremely 
> RAM constrained m68k system fail to boot or run anything past 6.9-rc4 
> (sysvinit, not systemd).
> 

As cloud instances multiply, that small quantity of lost RAM gets 
multiplied. So it appears that small systems aren't so strange, even after 
they become unprofitable...

> Much as I appreciate Adrian's efforts to keep up with user space 
> development, I won't be in a position to help with an ABI change.
> 

Bloated m68k packages will continue to work -- given emulators that run 
faster with every hardware upgrade. But how would such a distro add value?

I don't mind if Gentoo ships a separate profile for (downstream) ABI 
experimentation, leaving the default m68k profile on the standard ABI.

And if Debian wants to switch ABI entirely, I won't object further, I've 
said enough about the associated risks.

So I'll just reiterate that I'd rather see more collaboration instead -

1) among all small systems ports, to try to alleviate Debian's package 
   dependency problem

2) among all developers working on non-commercial architectures, to 
   improve the GCC Rust frontend

3) among all 680x0 developers interested in the NetBSD ABI

4) among all users of EOL'd hardware, so that value may continue to be 
   extracted from it (thanks to the efforts of Debian and Gentoo devs, 
   among others).

  reply	other threads:[~2024-10-29  3:39 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  6:48 Plan needed for switching m68k to 32-bit alignment John Paul Adrian Glaubitz
2024-10-25  9:06 ` Finn Thain
2024-10-25  9:18   ` John Paul Adrian Glaubitz
2024-10-26  7:31     ` Finn Thain
2024-10-26 22:04       ` Thorsten Glaser
2024-10-27  2:49         ` Finn Thain
2024-10-27  3:08           ` Thorsten Glaser
2024-10-27  3:47             ` Finn Thain
2024-10-27  4:23               ` Thorsten Glaser
2024-10-27  6:16                 ` Finn Thain
2024-10-27 13:15                   ` Arnd Bergmann
2024-10-28  3:07                     ` Thorsten Glaser
2024-10-28  4:51                       ` Finn Thain
2024-10-28  8:09                         ` John Paul Adrian Glaubitz
2024-10-28  8:49                           ` Finn Thain
2024-11-13 12:53                             ` John Paul Adrian Glaubitz
2024-10-28  8:03                       ` John Paul Adrian Glaubitz
2024-10-28  8:44                         ` Finn Thain
2024-11-13 12:51                           ` John Paul Adrian Glaubitz
2024-10-28  7:58                     ` John Paul Adrian Glaubitz
2024-10-28  7:55                   ` John Paul Adrian Glaubitz
2024-11-14 16:29                   ` Geert Uytterhoeven
2024-11-15  0:24                     ` Finn Thain
2024-11-15  1:24                       ` Thorsten Glaser
2024-11-15  1:31                         ` Thorsten Glaser
2024-10-28  7:53               ` John Paul Adrian Glaubitz
2024-10-28  7:49             ` John Paul Adrian Glaubitz
2024-10-28  7:47           ` John Paul Adrian Glaubitz
2024-10-28  8:40             ` Finn Thain
2024-11-13 12:50               ` John Paul Adrian Glaubitz
2024-11-13 22:01                 ` Finn Thain
2024-10-28  7:43         ` John Paul Adrian Glaubitz
2024-10-28  7:40       ` John Paul Adrian Glaubitz
2024-10-28  8:29         ` Finn Thain
2024-11-13 12:47           ` John Paul Adrian Glaubitz
2024-11-13 22:52             ` Finn Thain
2024-10-25  9:55 ` Arnd Bergmann
2024-10-25 10:10   ` John Paul Adrian Glaubitz
2024-10-25 10:50     ` Arnd Bergmann
2024-10-25 15:07       ` Andreas Schwab
2024-10-28  7:24         ` John Paul Adrian Glaubitz
2024-10-25 21:38     ` Thorsten Glaser
2024-10-25 22:24       ` Andreas Schwab
2024-10-25 23:42         ` Thorsten Glaser
2024-10-27 13:03           ` Greg Ungerer
2024-10-27 12:58         ` Arnd Bergmann
2024-10-28  3:19           ` Thorsten Glaser
2024-10-28  3:54             ` Greg Ungerer
2024-10-28  7:57           ` John Paul Adrian Glaubitz
2024-10-28  7:30         ` John Paul Adrian Glaubitz
2024-10-26 10:46       ` Geert Uytterhoeven
2024-10-28  7:41         ` John Paul Adrian Glaubitz
2024-10-28  7:26       ` John Paul Adrian Glaubitz
2024-11-14 19:46       ` Geert Uytterhoeven
2024-11-14 22:13         ` Thorsten Glaser
2024-11-14 22:37           ` James Le Cuirot
2024-10-28 18:57   ` Michael Schmitz
2024-10-29  3:39     ` Finn Thain [this message]
2024-11-13 12:58       ` John Paul Adrian Glaubitz
2024-11-13 23:12         ` Finn Thain
2024-11-13 12:54     ` John Paul Adrian Glaubitz
2024-11-13 18:36       ` Michael Schmitz
2024-11-13 19:55         ` John Paul Adrian Glaubitz
2024-11-13 20:48           ` Stan Johnson
2024-11-13 21:01             ` John Paul Adrian Glaubitz
2024-11-14 18:07               ` Stan Johnson
2024-11-14 19:28                 ` Geert Uytterhoeven
2024-11-13 20:49           ` John Paul Adrian Glaubitz
2024-11-13 21:33           ` Thorsten Glaser
2024-11-13 23:34             ` Finn Thain
2024-11-14 19:32           ` Geert Uytterhoeven

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=de1adc92-f1e9-81fd-9406-7148e8213e4c@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=chewi@aura-online.co.uk \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@gentoo.org \
    --cc=schmitzmic@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=tg@mirbsd.de \
    /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).