From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: Roger Quadros <rogerq@kernel.org>, <trini@konsulko.com>,
<vigneshr@ti.com>, <m-chawdhry@ti.com>, <sjg@chromium.org>,
<jonas@kwiboo.se>, <srk@ti.com>, <bb@ti.com>, <praneeth@ti.com>,
<u-boot@lists.denx.de>
Subject: Re: [PATCH 1/2] board: ti: am62x: am62x.env: Fix boot_targets
Date: Wed, 4 Oct 2023 08:54:36 -0500 [thread overview]
Message-ID: <20231004135436.ihofrxutzcdefica@audacious> (raw)
In-Reply-To: <26457fd1-439d-fb87-52cc-350a884a8dcd@ti.com>
On 08:48-20231004, Andrew Davis wrote:
> On 10/4/23 8:23 AM, Roger Quadros wrote:
> > ti_mmc is not a valid boot_target for standard boot flow so
>
> Is there some way to make it into a valid boot_target? Otherwise
> how do we use uEnv.txt files, or boot from FIT images with overlays?
envboot takes care of uEnv.txt file (see
https://lore.kernel.org/all/20231004132324.44198-3-rogerq@kernel.org/)
Early remote proc loading and FIT image is a question for stdboot itself.
>
> Andrew
>
> > remove it. Prefer mmc1 (sd-card) over mmc0 (emmc).
> >
> > Signed-off-by: Roger Quadros <rogerq@kernel.org>
> > ---
> > board/ti/am62x/am62x.env | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/board/ti/am62x/am62x.env b/board/ti/am62x/am62x.env
> > index 22a6c2c91b..e53a55c38f 100644
> > --- a/board/ti/am62x/am62x.env
> > +++ b/board/ti/am62x/am62x.env
> > @@ -8,7 +8,7 @@ args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000
> > ${mtdparts}
> > run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
> > -boot_targets=ti_mmc mmc0 mmc1 usb pxe dhcp
> > +boot_targets=mmc1 mmc0 usb pxe dhcp
> > boot=mmc
> > mmcdev=1
> > bootpart=1:2
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-10-04 13:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 13:23 [PATCH 0/2] board: ti: am6x: Switch to standard boot Roger Quadros
2023-10-04 13:23 ` [PATCH 1/2] board: ti: am62x: am62x.env: Fix boot_targets Roger Quadros
2023-10-04 13:48 ` Andrew Davis
2023-10-04 13:54 ` Nishanth Menon [this message]
2023-10-05 14:19 ` Andrew Davis
2023-10-05 16:36 ` Tom Rini
2023-10-05 17:10 ` Nishanth Menon
2023-10-05 17:16 ` Nishanth Menon
2023-10-05 17:22 ` Andrew Davis
2023-10-05 17:28 ` Nishanth Menon
2023-10-05 17:22 ` Simon Glass
2023-10-06 9:54 ` Roger Quadros
2023-11-06 5:53 ` Manorit Chawdhry
2023-11-06 15:31 ` Tom Rini
2023-11-06 17:27 ` Andrew Davis
2023-11-06 17:47 ` Simon Glass
2023-11-06 18:05 ` Andrew Davis
2023-11-28 9:31 ` Manorit Chawdhry
2023-11-30 2:16 ` Simon Glass
2023-11-30 2:45 ` Simon Glass
2023-12-31 12:48 ` Simon Glass
2024-01-02 14:58 ` Andrew Davis
2024-01-04 7:52 ` Manorit Chawdhry
2024-01-04 15:55 ` Andrew Davis
2024-01-04 22:23 ` Jon Humphreys
2024-01-05 7:46 ` Manorit Chawdhry
2023-10-04 13:59 ` Nishanth Menon
2023-10-04 13:23 ` [PATCH 2/2] board: ti: am64x: Switch to standard boot flow Roger Quadros
2023-10-04 13:59 ` Nishanth Menon
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=20231004135436.ihofrxutzcdefica@audacious \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=jonas@kwiboo.se \
--cc=m-chawdhry@ti.com \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=sjg@chromium.org \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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