All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] imx8mq_evk/README: add missing firmware extract step
Date: Thu, 28 Feb 2019 06:26:55 +0200	[thread overview]
Message-ID: <87r2bs5yi8.fsf@tarshish> (raw)
In-Reply-To: <CAOMZO5B5puLwEBaRwEKyma77fzAZg9fGpEXicbDSZwuva8owaA@mail.gmail.com>

Hi Fabio, Stefano,

On Thu, Feb 28 2019, Fabio Estevam wrote:
> On Sun, Feb 24, 2019 at 3:21 PM Baruch Siach <baruch@tkos.co.il> wrote:
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>> ---
>>  board/freescale/imx8mq_evk/README | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/board/freescale/imx8mq_evk/README b/board/freescale/imx8mq_evk/README
>> index e1335293a08f..2529f7da3d98 100644
>> --- a/board/freescale/imx8mq_evk/README
>> +++ b/board/freescale/imx8mq_evk/README
>> @@ -18,6 +18,7 @@ Get the ddr and hdmi firmware
>>  Note: srctree is U-Boot source directory
>>  $ wget https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-7.9.bin
>>  $ chmod +x firmware-imx-7.9.bin
>> +$ ./firmware-imx-7.9.bin
>
> I would suggest making this one the first patch of this series.

Should I post v2 with that change?

> Tested-by: Fabio Estevam <festevam@gmail.com>

Thanks,
baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2019-02-28  4:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 18:20 [U-Boot] [PATCH 1/2] imx8mq_evk/README: fix DDR training firmware path Baruch Siach
2019-02-24 18:20 ` [U-Boot] [PATCH 2/2] imx8mq_evk/README: add missing firmware extract step Baruch Siach
2019-02-28  0:55   ` Fabio Estevam
2019-02-28  4:26     ` Baruch Siach [this message]
2019-02-28 10:43       ` Fabio Estevam
2019-02-28  0:55 ` [U-Boot] [PATCH 1/2] imx8mq_evk/README: fix DDR training firmware path Fabio Estevam

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=87r2bs5yi8.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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.