From: Tom Rini <trini@konsulko.com>
To: Patrick Rudolph <patrick.rudolph@9elements.com>
Cc: Naresh Solanki <naresh.solanki@9elements.com>,
u-boot@lists.denx.de, "Chia-Wei,
Wang" <chiawei_wang@aspeedtech.com>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Aspeed BMC SW team <BMC-SW@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] sbp1: Add support for IBM SBP1 board
Date: Tue, 2 Jan 2024 20:51:54 -0500 [thread overview]
Message-ID: <20240103015154.GF1610741@bill-the-cat> (raw)
In-Reply-To: <CALNFmy26yQYiNb0-7pFzGa3Z1gxkCb1NpwzEwX5tDxcedg9N7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Tue, Jan 02, 2024 at 10:29:05AM +0100, Patrick Rudolph wrote:
> Hi Tom,
> can you please clarify or point us to some documentation that explains
> the new DT setup?
> I thought the u-boot DT is only used for u-boot internal drivers.
The DT has always supposed to have been the same one as the Linux
Kernel, to make things easier for developers as they would only need one
DT, not two. For systems that use the EFI loader we pass the same DT to
the OS which can simplify life.
> Do we need to upstream the kernel DT first?
If the DT is not upstream it really should be being submitted upstream
and not just never upstreamed. I know this is more challenging in some
cases than others.
> Do we need to provide a complete "kernel DT" to u-boot as well?
That is usually easiest, yes.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-01-03 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 9:12 [PATCH] sbp1: Add support for IBM SBP1 board Naresh Solanki
2023-12-20 19:12 ` Tom Rini
2023-12-20 21:08 ` Naresh Solanki
2023-12-20 22:38 ` Tom Rini
2024-01-02 9:29 ` Patrick Rudolph
2024-01-03 1:51 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 10:50 Naresh Solanki
2023-11-23 0:53 ` Tom Rini
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=20240103015154.GF1610741@bill-the-cat \
--to=trini@konsulko.com \
--cc=BMC-SW@aspeedtech.com \
--cc=chiawei_wang@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=ryan_chen@aspeedtech.com \
--cc=u-boot@lists.denx.de \
/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