Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Daniel Palmer <daniel@thingy.jp>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH] m68k: Add 68000 nommu support
Date: Fri, 29 May 2026 20:59:11 +0200	[thread overview]
Message-ID: <ahnh6Z__bUk8a5Uh@windsurf> (raw)
In-Reply-To: <20260419054645.2019170-1-daniel@thingy.jp>

On Sun, Apr 19, 2026 at 02:46:45PM +0900, Daniel Palmer wrote:
> Everyone thinks they like ARM but secretly they want to run
> Linux on their Megadrive[0].
> 
> Building a working toolchain/userland for nommu m68k is a bit
> difficult because of the bitrotten tools all over the place and
> one big issue is GCC generates code that uses unaligned
> accesses that will cause an exception on 68000 machines if you
> aren't careful.
> 
> Buildroot can easily create a working toolchain and userland
> for nommu m68k so why not?
> 
> 0 - This isn't a joke, I'm working on this. I have u-boot working
>     on the Megadrive, Linux is already working on a bunch of 68000
>     machines and I just need to get everything a little bit smaller
>     to get into 4MB of RAM.

Have fun! :-)

> 
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-05-29 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19  5:46 [Buildroot] [RFC PATCH] m68k: Add 68000 nommu support Daniel Palmer
2026-05-29 18:59 ` Thomas Petazzoni via buildroot [this message]

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=ahnh6Z__bUk8a5Uh@windsurf \
    --to=buildroot@buildroot.org \
    --cc=daniel@thingy.jp \
    --cc=thomas.petazzoni@bootlin.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