revolution (i.e. whether there is any‐
thing in the kernel/userspace boundary that direly needs to
change, for this or anyway, and is a breaking change… though
maybe even then).
On Sun, 27 Oct 2024, Greg Ungerer wrote:
There is plenty of Linux on ColdFire, but all the m68k'isms apply the same.
On 26/10/24 09:42, Thorsten Glaser wrote:
On Sat, 26 Oct 2024, Andreas Schwab wrote:
Already basic things like struct stat64 will break.
OK. Then, flag day, I guess.
How do we model this in Debian. Rename libc to libc6.1 and
conflict with libc6 to force no coïnstallability, rename the
arch
Hi Adrian,
On 18/6/25 20:04, John Paul Adrian Glaubitz wrote:
Hello Geert,
On Wed, 2025-06-18 at 11:56 +0200, Geert Uytterhoeven wrote:
Coldfire already uses a different alignment (for the stack):
/* ColdFire and fido strongly prefer a 32-bit aligned stack. */
#define PREFERRED_STACK_BOUNDAR
Hi Geert,
On 18/6/25 22:54, Geert Uytterhoeven wrote:
Hi Adrian,
On Wed, 18 Jun 2025 at 14:27, John Paul Adrian Glaubitz
wrote:
On Wed, 2025-06-18 at 22:21 +1000, Greg Ungerer wrote:
Could you please elaborate this a bit more, please?
Coldfire is handled as a separate target via
On 19/6/25 08:29, Finn Thain wrote:
On Wed, 18 Jun 2025, Greg Ungerer wrote:
It's not really necessary to enforce this on Coldfire. However, since
buildroot builds completely from source, it wouldn't even be a problem
to change the alignment there as well.
Yes, that is totall
On 19/6/25 15:31, Finn Thain wrote:
On Thu, 19 Jun 2025, Greg Ungerer wrote:
On 19/6/25 08:29, Finn Thain wrote:
On Wed, 18 Jun 2025, Greg Ungerer wrote:
It's not really necessary to enforce this on Coldfire. However,
since buildroot builds completely from source, it wouldn't
6 matches
Mail list logo
