From: Daniel Palmer <daniel@thingy.jp>
To: buildroot@buildroot.org
Cc: Daniel Palmer <daniel@thingy.jp>
Subject: [Buildroot] [RFC PATCH] m68k: Add 68000 nommu support
Date: Sun, 19 Apr 2026 14:46:45 +0900 [thread overview]
Message-ID: <20260419054645.2019170-1-daniel@thingy.jp> (raw)
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.
Signed-off-by: Daniel Palmer <daniel@thingy.jp>
---
arch/Config.in.m68k | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/Config.in.m68k b/arch/Config.in.m68k
index 235cafacf5b7..74a197934ff1 100644
--- a/arch/Config.in.m68k
+++ b/arch/Config.in.m68k
@@ -23,6 +23,11 @@ choice
help
Specific CPU variant to use
+config BR2_m68k_68000
+ bool "68000"
+ select BR2_m68k_m68k
+ select BR2_SOFT_FLOAT
+
config BR2_m68k_68030
bool "68030"
select BR2_m68k_m68k
@@ -41,6 +46,7 @@ config BR2_m68k_cf5208
endchoice
config BR2_GCC_TARGET_CPU
+ default "68000" if BR2_m68k_68000
default "68030" if BR2_m68k_68030
default "68040" if BR2_m68k_68040
default "5208" if BR2_m68k_cf5208
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-04-19 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 5:46 Daniel Palmer [this message]
2026-05-29 18:59 ` [Buildroot] [RFC PATCH] m68k: Add 68000 nommu support Thomas Petazzoni via buildroot
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=20260419054645.2019170-1-daniel@thingy.jp \
--to=daniel@thingy.jp \
--cc=buildroot@buildroot.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