All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH] imx8mq_evk: Update the required ATF branch
Date: Wed, 11 Dec 2019 11:01:24 -0300	[thread overview]
Message-ID: <CAOMZO5A=1=3oH3-zUYpfNFG0GzT8oNwT+PjU0yJKR8QF-U+mXQ@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7xK9VkxPcj9qnkEqyixJO+wRifiVQr1HOerktKV8mfBpfw@mail.gmail.com>

Hi Adam,

On Wed, Dec 11, 2019 at 10:56 AM Adam Ford <aford173@gmail.com> wrote:

> Shouldn't we address the mix-match of the firmware-imx  versions as well?
>
> I just increasing numbers over and over, and I was able to use
> firmware 8.5 which.
>
> The readme lists both 7.9 and 8.0.  There is also a typo on the line
> that reads "./firmware-imx-8.0" which should have a .bin appended to
> it.

This error comes from the imx8mm-evk README. I am patching imx8mq-evk
README instead.

> It would nice to know what the differences are between the versions.

Yes, it is becoming painful to find the exact combination that works.

  parent reply	other threads:[~2019-12-11 14:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 13:49 [PATCH] imx8mq_evk: Update the required ATF branch Fabio Estevam
2019-12-11 13:56 ` Adam Ford
2019-12-11 14:00   ` Peng Fan
2019-12-11 14:04     ` Adam Ford
2019-12-11 14:05     ` Fabio Estevam
2019-12-11 14:09       ` Peng Fan
2019-12-11 14:11         ` Fabio Estevam
2019-12-11 14:13       ` Schrempf Frieder
2019-12-11 16:02         ` Fabio Estevam
2019-12-12  1:09           ` Peter Robinson
2019-12-12  1:20             ` Fabio Estevam
2019-12-12  1:57               ` Fabio Estevam
2019-12-12  2:14                 ` Fabio Estevam
2020-04-21 16:05                   ` Angus Ainslie
2019-12-11 14:01   ` Fabio Estevam [this message]
2019-12-12  1:13 ` Peng Fan
2019-12-28 10:48 ` sbabic at denx.de

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='CAOMZO5A=1=3oH3-zUYpfNFG0GzT8oNwT+PjU0yJKR8QF-U+mXQ@mail.gmail.com' \
    --to=festevam@gmail.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.