From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: imx8qxp mek: Booting mainline kernel with mainline U-Boot
Date: Thu, 16 Jan 2020 17:57:09 +0100 [thread overview]
Message-ID: <20200116175709.19f4d5ad@crub> (raw)
In-Reply-To: <CAOMZO5CPP+ZLgRgWOmXFmMb42wsPwhPU8zLV2GWZqsNU-QCbAw@mail.gmail.com>
Hi Fabio,
On Thu, 16 Jan 2020 13:38:26 -0300
Fabio Estevam festevam at gmail.com wrote:
> Hi Anatolij,
>
> On Tue, Jan 14, 2020 at 8:04 PM Anatolij Gustschin <agust@denx.de> wrote:
>
> > Currently I do not have an i.MX8QXP MEK board with RevB CPU and cannot
> > test, but I have an i.MX8QXP based custom SoM with console on ttyLP2.
> > Here I tested with NXP BSP kernel based on branch imx_4.14.98_2.0.0_ga
> > and it boots successfully (with NFS rootfs or rootfs on eMMC).
>
> I have just tested imx_4.14.98_2.0.0_ga and still get the same hang.
then it might be due to scfw API incompatibility?
> [Adding Marcel]
>
> Just wondering if anyone else managed to boot mainline U-Boot with
> mainline kernel on i.MX8QXP.
yesterday I wanted to test some mainline drivers on my SoM and
created simple device tree for booting with console output.
Mainline kernel v5.5-rc6 booted successfully, (but without FEC
support).
> If so, what firmware combination was used?
Unfortunately, my i.MX8QXP SoM was damaged today and it doesn't boot
any more and it is not recoverable, so I cannot check the used firmware
hashes. I only know that it was something from 4.14.98_2.0.0_ga release.
--
Anatolij
next prev parent reply other threads:[~2020-01-16 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 15:36 imx8qxp mek: Booting mainline kernel with mainline U-Boot Fabio Estevam
2020-01-13 15:53 ` Anatolij Gustschin
2020-01-13 16:03 ` Fabio Estevam
2020-01-14 23:04 ` Anatolij Gustschin
2020-01-16 16:38 ` Fabio Estevam
2020-01-16 16:57 ` Anatolij Gustschin [this message]
2020-01-16 18:03 ` Igor Opaniuk
2020-01-16 18:16 ` Tom Rini
2020-01-17 6:07 ` Lokesh Vutla
2020-01-23 13:53 ` Oliver Graute
2020-01-23 14:07 ` Lokesh Vutla
2020-01-27 13:13 ` Peng Fan
2020-01-14 0:46 ` Peng Fan
2020-01-14 1:08 ` Fabio Estevam
2020-01-14 19:01 ` Fabio Estevam
2020-01-21 17:39 ` Fabio Estevam
2020-01-27 13:11 ` Peng Fan
2021-06-12 12:51 ` vmuthusu
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=20200116175709.19f4d5ad@crub \
--to=agust@denx.de \
--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 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.