From: Michael Walle <michael@walle.cc>
To: Tony Dinh <mibodhi@gmail.com>
Cc: "Stefan Roese" <sr@denx.de>,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Tom Rini" <trini@konsulko.com>, "Pali Roh�r" <pali@kernel.org>
Subject: Re: [PATCH] arm: kirkwood: Enable uart0 dm-pre-reloc for Kirkwood boards
Date: Wed, 01 Feb 2023 08:53:55 +0100 [thread overview]
Message-ID: <1ab1b2faa95c5ec618a7aad5ce0903ea@walle.cc> (raw)
In-Reply-To: <20230201011116.17699-1-mibodhi@gmail.com>
Hi Tony,
Am 2023-02-01 02:11, schrieb Tony Dinh:
> When DM_SERIAL is enabled, the device-tree property dm-pre-reloc is
> required to boot over UART with kwboot. Enable this in a Kirkwood
> common u-boot dtsi.
My (dev) board unfortunately, have a bootloader which can't boot over
serial. Could you elaborate that a bit more? Why is this required for
uart boot? kwboot will talk with the bootrom why does u-boot need
anything? Or will there just be no output until the uart is initialized?
>
> Signed-off-by: Tony Dinh <mibodhi@gmail.com>
> ---
>
> arch/arm/dts/kirkwood-u-boot.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
> create mode 100644 arch/arm/dts/kirkwood-u-boot.dtsi
Is this new? AFAIK only <boardname>-u-boot.dtsi is included
automatically.
-michael
next prev parent reply other threads:[~2023-02-01 7:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 1:11 [PATCH] arm: kirkwood: Enable uart0 dm-pre-reloc for Kirkwood boards Tony Dinh
2023-02-01 6:30 ` Stefan Roese
2023-02-01 7:05 ` Tony Dinh
2023-02-01 7:53 ` Michael Walle [this message]
2023-02-01 8:02 ` Pali Rohár
2023-02-01 8:17 ` Michael Walle
2023-02-01 19:05 ` Pali Rohár
2023-02-01 21:13 ` Tony Dinh
2023-02-02 4:53 ` Tony Dinh
2023-02-02 18:04 ` Pali Rohár
2023-02-02 23:59 ` Tony Dinh
2023-02-03 4:28 ` Tony Dinh
2023-02-03 21:54 ` Tony Dinh
2023-02-03 22:05 ` Pali Rohár
2023-02-04 0:11 ` Tony Dinh
2023-02-09 3:17 ` Tony Dinh
2023-02-09 7:15 ` Stefan Roese
2023-02-09 21:33 ` Tony Dinh
2023-02-09 21:45 ` Pali Rohár
2023-02-10 1:37 ` Tony Dinh
2023-02-10 6:32 ` Stefan Roese
2023-02-10 17:29 ` Pali Rohár
2023-02-10 21:38 ` Tony Dinh
2023-02-10 21:44 ` Pali Rohár
2023-02-11 2:29 ` Tony Dinh
2023-03-14 20:59 ` Tony Dinh
2023-03-14 21:09 ` Pali Rohár
2023-03-14 21:30 ` Tony Dinh
2023-03-14 23:07 ` Tony Dinh
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=1ab1b2faa95c5ec618a7aad5ce0903ea@walle.cc \
--to=michael@walle.cc \
--cc=mibodhi@gmail.com \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--cc=trini@konsulko.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