From: Mathieu Othacehe <othacehe@gnu.org>
To: Primoz Fiser <primoz.fiser@norik.com>
Cc: Peng Fan <peng.fan@nxp.com>, Tom Rini <trini@konsulko.com>,
Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>,
Yannic Moog <Y.Moog@phytec.de>,
u-boot@lists.denx.de, upstream@lists.phytec.de
Subject: Re: [PATCH v2] Add Phytec i.MX93 support
Date: Thu, 25 Jan 2024 17:29:02 +0100 [thread overview]
Message-ID: <87cytpml69.fsf@gnu.org> (raw)
In-Reply-To: <4f0dcc58-7a9f-41d9-9604-f9fe2336eb25@norik.com> (Primoz Fiser's message of "Thu, 25 Jan 2024 12:47:28 +0100")
Hello,
Thanks for having a look!
> Here are my findings:
>
> - FEC ethernet doesn't work
> - distroboot doesn't work
>
> Did you expirience the same?
I have not tested Ethernet ports on u-boot yet. I removed distroboot
support as you proposed later in the review.
Note that my evaluation board has a hardware issue on the eMMC module. I
am testing this patch my flashing the bootloader on the SD card using
the commands in the proposed documentation, and booting on the SD card.
> Can you rework you commit msg + title please?
Done.
> Can you rename to match other?
Sure.
> Can you add:
>
> &wdog3 {
> bootph-all;
> bootph-pre-ram;
> };
>
> here to also enable WDT in SPL, please.
OK.
> I don't think this is necessary?
>
> You are using CONFIG_DM_SERIAL.
It is not necessary indeed.
> IMHO I would disable distroboot and sync with downstream.
Done.
I synced the configuration and environment files to be closer to the
downstream versions.
I will send a v3 soon.
Thanks,
Mathieu
prev parent reply other threads:[~2024-01-25 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 13:42 [PATCH v2] Add Phytec i.MX93 support Mathieu Othacehe
2024-01-25 11:47 ` Primoz Fiser
2024-01-25 16:29 ` Mathieu Othacehe [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=87cytpml69.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=Y.Moog@phytec.de \
--cc=c.stoidner@phytec.de \
--cc=festevam@gmail.com \
--cc=peng.fan@nxp.com \
--cc=primoz.fiser@norik.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox