From: Finn Thain <fthain@linux-m68k.org>
To: Brad Boyer <flar@allandria.com>
Cc: Greg Ungerer <gerg@kernel.org>, Daniel Palmer <daniel@0x0f.com>,
geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] m68k goes DT
Date: Tue, 7 Jan 2025 09:14:30 +1100 (AEDT) [thread overview]
Message-ID: <980f40b3-fd1c-74c7-c651-b85040bbd3fc@linux-m68k.org> (raw)
In-Reply-To: <20250106113749.GA32654@allandria.com>
On Mon, 6 Jan 2025, Brad Boyer wrote:
> There are a few drivers where we could eliminate complexity and #ifdef
> trickery if it was all device tree based.
Ideally, yes. But how would we get there from here?
Should the kernel synthesize a device tree from the bootinfo data, so that
an ideal no-ifdef pmac_zilog could work? (This seems like a maximum bloat
solution.)
Or should the mac platform abandon bootinfo, and require a new bootloader
for all kernel releases after device tree adoption? (This seems maximally
difficult, since it requires simultaneously merging many patches to many
subsystems, even if the bootloader changes could be done in advance...)
I wonder whether any other architectures have attempted to retrofit device
tree support (?)
next prev parent reply other threads:[~2025-01-06 22:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 7:14 Daniel Palmer
2025-01-05 7:14 ` [RFC PATCH 1/3] m68k: bootinfo: Add tag for FDT address Daniel Palmer
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 [this message]
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=980f40b3-fd1c-74c7-c651-b85040bbd3fc@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®