From: Oliver Graute <oliver.graute@kococonnector.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 2/2] core: device: use dev_power_domain_on
Date: Tue, 21 Jan 2020 10:36:30 +0000 [thread overview]
Message-ID: <20200121103350.GA4218@optiplex> (raw)
In-Reply-To: <CAByghJbRwYn-d+pXH7raB4MXkPiuWwvwkYoSpyOmchxHPQgWNw@mail.gmail.com>
On 16/12/19, Igor Opaniuk wrote:
> Hi Oliver, Fabio, Peng,
>
> On Thu, Dec 12, 2019 at 9:20 AM Oliver Graute
> <oliver.graute@kococonnector.com> wrote:
> >
> > On 11/12/19, Fabio Estevam wrote:
> > > Hi Oliver,
> > >
> > > On Tue, Dec 10, 2019 at 11:50 PM Peng Fan <peng.fan@nxp.com> wrote:
> > >
> > > > Update your scfw/atf and they try again.
> > >
> > > Does it boot if you use the imx_4.19.35_1.0.0 ATF branch?
> >
> > Unfortunately, not. I checked out imx-atf in that branch. Build it with:
> >
> > make PLAT=imx8qm bl31
> >
> > copied the resulting bl31.bin into my u-boot folder and rebuild that.
> >
> > But the imx8qm board is not booting with the resulting u-boot.
> >
> > do I need a new scfw from my vendor?
> >
> > Best Regards,
> >
> > Oliver
>
> FYI,
>
> I do face the same boot issues on colibri-imx8qxp_defconfig ,
> In my case using imx_4.19.35_1.0.0 TF-A(ATF) doesn't help too.
>
> Bi-secting also points to this commit.
Did you made some progress here?
I tried this combination but without success for the imx8qm_rom_7720:
u-boot 2020.01
imx-atf imx_4.19.35_1.1.0
imx-sc-firmware-1.2.7.1.bin
imx-seco-2.3.1.bin
Which latest combination is vaild for the imx8qm_mek board?
Best Regards,
Oliver
prev parent reply other threads:[~2020-01-21 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 1:55 [U-Boot] [PATCH V3 1/2] power: domain: add dev_power_domain_on Peng Fan
2019-09-27 1:55 ` [U-Boot] [PATCH V3 2/2] core: device: use dev_power_domain_on Peng Fan
2019-12-10 14:18 ` Oliver Graute
2019-12-11 2:50 ` Peng Fan
2019-12-11 3:15 ` Fabio Estevam
2019-12-11 14:15 ` Fabio Estevam
2019-12-12 7:20 ` Oliver Graute
2019-12-16 15:29 ` Igor Opaniuk
2019-12-16 16:24 ` Fabio Estevam
2019-12-16 21:16 ` Igor Opaniuk
2019-12-16 22:47 ` Fabio Estevam
2019-12-17 10:56 ` Igor Opaniuk
2019-12-17 11:21 ` Igor Opaniuk
2019-12-17 11:23 ` Fabio Estevam
2019-12-17 11:22 ` Fabio Estevam
2019-12-17 1:14 ` Peng Fan
2020-01-21 10:36 ` Oliver Graute [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=20200121103350.GA4218@optiplex \
--to=oliver.graute@kococonnector.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 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.