From: Martin Husemann <martin@NetBSD.org>
To: Tom Rini <trini@konsulko.com>
Cc: Martin Husemann <martin@netbsd.org>,
Yuri Honegger <yuri.honegger@icloud.com>,
u-boot@lists.denx.de
Subject: Re: Placement of FDT in memory
Date: Sat, 10 Jan 2026 18:45:29 +0100 [thread overview]
Message-ID: <aWKQOW_ajq0DsbYA@big-apple.aprisoft.de> (raw)
In-Reply-To: <20260110164349.GO3416603@bill-the-cat>
On Sat, Jan 10, 2026 at 10:43:49AM -0600, Tom Rini wrote:
> I thought it might be something like that. Are there any non-EOL NetBSD
> releases that don't use device tree? If not, we can go and mark the
> legacy option as non-default. Thanks!
I think there are still some ancient arm and mips platforms that have not
been converted to use FDT, though there was a project to fix them recently
(but it is not done).
Martin
prev parent reply other threads:[~2026-01-10 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 22:04 Placement of FDT in memory Yuri Honegger
2026-01-09 11:34 ` Simon Glass
2026-01-09 21:24 ` Yuri Honegger
2026-01-09 17:09 ` Tom Rini
2026-01-09 21:13 ` Yuri Honegger
2026-01-09 21:33 ` Tom Rini
2026-01-10 7:56 ` Martin Husemann
2026-01-10 16:43 ` Tom Rini
2026-01-10 17:45 ` Martin Husemann [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=aWKQOW_ajq0DsbYA@big-apple.aprisoft.de \
--to=martin@netbsd.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=yuri.honegger@icloud.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