From: Daniel Schultz <d.schultz@phytec.de>
To: <u-boot@lists.denx.de>, <upstream@lists.phytec.de>
Cc: <w.egorov@phytec.de>, <trini@konsulko.com>, <d-gole@ti.com>,
<mkorpershoek@baylibre.com>, <nm@ti.com>,
Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 3/4] board: phytec: phycore_am62x: Move earlycon into own variable
Date: Sun, 30 Jun 2024 23:20:49 -0700 [thread overview]
Message-ID: <20240701062050.1475249-3-d.schultz@phytec.de> (raw)
In-Reply-To: <20240701062050.1475249-1-d.schultz@phytec.de>
By moving the earlycon definition into a dedicated variable, it's
easier to change these values in case the kernel should print on
a different serial interface.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
board/phytec/phycore_am62x/phycore_am62x.env | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/board/phytec/phycore_am62x/phycore_am62x.env b/board/phytec/phycore_am62x/phycore_am62x.env
index 42db26a5990..2d6475d408f 100644
--- a/board/phytec/phycore_am62x/phycore_am62x.env
+++ b/board/phytec/phycore_am62x/phycore_am62x.env
@@ -13,7 +13,8 @@ mmcdev=1
mmcroot=2
mmcpart=1
console=ttyS2,115200n8
-mmcargs=setenv bootargs console=${console} earlycon=ns16550a,mmio32,0x02800000
+earlycon=ns16550a,mmio32,0x02800000
+mmcargs=setenv bootargs console=${console} earlycon=${earlycon}
root=/dev/mmcblk${mmcdev}p${mmcroot} rootwait rw
loadimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} Image
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} ${fdtfile}
--
2.25.1
next prev parent reply other threads:[~2024-07-01 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 6:20 [PATCH 1/4] configs: phycore_am62x_a53: Add more commands Daniel Schultz
2024-07-01 6:20 ` [PATCH 2/4] configs: phycore_am64x_a53: " Daniel Schultz
2024-07-01 6:20 ` Daniel Schultz [this message]
2024-07-01 6:20 ` [PATCH 4/4] board: phytec: phycore_am64x: Move earlycon into own variable Daniel Schultz
2024-07-09 7:37 ` [PATCH 1/4] configs: phycore_am62x_a53: Add more commands Wadim Egorov
2024-07-16 23:00 ` 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=20240701062050.1475249-3-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=d-gole@ti.com \
--cc=mkorpershoek@baylibre.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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 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.