From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: Trevor Woerner <twoerner@gmail.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-freescale] suspicious MACHINE_FIRMWARE for mainline bsp
Date: Tue, 9 Feb 2021 16:58:21 -0300 [thread overview]
Message-ID: <CAP9ODKrWRT7=7iqkiTZRt=JnB0L1RiCLAk13MiYk2_ZRJH2uQw@mail.gmail.com> (raw)
In-Reply-To: <20210209173408.GA12199@localhost>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Em ter., 9 de fev. de 2021 às 14:34, Trevor Woerner <twoerner@gmail.com>
escreveu:
> In the master branch of
> https://git.yoctoproject.org/git/meta-freescale.git we
> find (at line 247):
>
> MACHINE_FIRMWARE_append_use-mainline-bsp = "
> linux-firmware-imx-sdma-imx6q linux-firmware-imx-sdma-imx7d
> firmware-imx-vpu-imx6q firmware-imx-vpu-imx6d"
>
> This looks suspicious to me since firmware-imx things are being included
> with
> the use-mainline-bsp OVERRIDE. Building for wandboard fails as a result.
>
> Is this intentional/required with mainline?
>
The build error is not intended but yes, the firmware are as we support all
those.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
[-- Attachment #2: Type: text/html, Size: 1502 bytes --]
next prev parent reply other threads:[~2021-02-09 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 17:34 suspicious MACHINE_FIRMWARE for mainline bsp Trevor Woerner
2021-02-09 19:58 ` Otavio Salvador [this message]
[not found] <166224C7215CF162.16853@lists.yoctoproject.org>
2021-02-09 17:40 ` [meta-freescale] " Trevor Woerner
2021-02-09 19:58 ` Otavio Salvador
2021-02-09 20:31 ` Trevor Woerner
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='CAP9ODKrWRT7=7iqkiTZRt=JnB0L1RiCLAk13MiYk2_ZRJH2uQw@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=twoerner@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).