From: Daniel Palmer <daniel@0x0f.com>
To: geert@linux-m68k.org, fthain@linux-m68k.org,
linux-m68k@lists.linux-m68k.org
Cc: linux-kernel@vger.kernel.org, Daniel Palmer <daniel@0x0f.com>
Subject: [RFC PATCH 1/3] m68k: bootinfo: Add tag for FDT address
Date: Sun, 5 Jan 2025 16:14:31 +0900 [thread overview]
Message-ID: <20250105071433.3943289-2-daniel@0x0f.com> (raw)
In-Reply-To: <20250105071433.3943289-1-daniel@0x0f.com>
Allow bootinfo to carry a pointer to an FDT so that the
bootloader can pass us one.
This allows for devicetree support without changing the
boot protocol too much and breaking unmaintained bootloaders.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/m68k/include/uapi/asm/bootinfo.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/m68k/include/uapi/asm/bootinfo.h b/arch/m68k/include/uapi/asm/bootinfo.h
index 024e87d7095f..326f20e82769 100644
--- a/arch/m68k/include/uapi/asm/bootinfo.h
+++ b/arch/m68k/include/uapi/asm/bootinfo.h
@@ -73,6 +73,9 @@ struct mem_info {
#define BI_RNG_SEED 0x0008
+/* Pointer to FDT if there is one */
+#define BI_FDT 0x0009
+
/*
* Linux/m68k Architectures (BI_MACHTYPE)
*/
--
2.45.2
next prev parent reply other threads:[~2025-01-05 7:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 7:14 [RFC PATCH 0/3] m68k goes DT Daniel Palmer
2025-01-05 7:14 ` Daniel Palmer [this message]
2025-01-05 7:14 ` [RFC PATCH 2/3] m68k: bootinfo: Add generic machine type Daniel Palmer
2025-01-05 7:14 ` [RFC PATCH 3/3] m68k: Add dt support (proof of concept) Daniel Palmer
2025-01-05 9:40 ` [RFC PATCH 0/3] m68k goes DT Finn Thain
2025-01-05 11:00 ` Daniel Palmer
2025-01-06 3:28 ` Finn Thain
2025-01-06 15:51 ` Josh Juran
2025-01-07 0:57 ` Bootloaders, was " Finn Thain
2025-03-04 10:43 ` Daniel Palmer
2025-03-05 3:42 ` Finn Thain
2025-01-09 10:06 ` Geert Uytterhoeven
2025-01-05 14:59 ` Greg Ungerer
2025-01-06 2:10 ` Daniel Palmer
2025-01-06 11:37 ` Brad Boyer
2025-01-06 22:14 ` Finn Thain
2025-01-09 10:29 ` Geert Uytterhoeven
2025-01-14 0:42 ` Finn Thain
2025-01-09 10:31 ` Geert Uytterhoeven
2025-01-09 14:08 ` Daniel Palmer
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=20250105071433.3943289-2-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.