From: Brad Boyer <flar@allandria.com>
To: Greg Ungerer <gerg@kernel.org>
Cc: Daniel Palmer <daniel@0x0f.com>,
geert@linux-m68k.org, fthain@linux-m68k.org,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] m68k goes DT
Date: Mon, 6 Jan 2025 03:37:49 -0800 [thread overview]
Message-ID: <20250106113749.GA32654@allandria.com> (raw)
In-Reply-To: <c0428d69-2f18-45d3-8024-a9fe4170b23e@kernel.org>
On Mon, Jan 06, 2025 at 12:59:04AM +1000, Greg Ungerer wrote:
> On 5/1/25 17:14, Daniel Palmer wrote:
> >Short version:
> >I want to start converting m68k (including nommu) to use DT for booting
> >so I can add few cool boards I have (e.g. dual 040/060 VME board..).
> >I need ideas, help etc. Maybe if someone converted an m68k machine they
> >are using to DT alongside me this would have some hope of actually happening?
>
> I have been thinking about this for a while for the ColdFire targets.
> In a few cases the drivers its uses are already devicetree enabled,
> since they are used on some of the NXP/Freescale ARM SoC devices.
> So this is interesting work to me.
The m68k mac platform is similar in this due to sharing some drivers
with ppc macs using Open Firmware. There are a few drivers where we
could eliminate complexity and #ifdef trickery if it was all
device tree based. For example, pmac_zilog.c relies on the data from
OF on a powermac but is getting platform data from the tables in
config.c on m68k. The code in via-cuda.c similarly looks up the
hardware info from OF on a powermac but has hard-coded data on m68k.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2025-01-06 12:06 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 ` [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 [this message]
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=20250106113749.GA32654@allandria.com \
--to=flar@allandria.com \
--cc=daniel@0x0f.com \
--cc=fthain@linux-m68k.org \
--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 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.