From: "Peter A. Bigot" <pab@pabigot.com>
To: meta-ti@yoctoproject.org
Subject: Recipes adding firmware in meta-ti
Date: Mon, 27 Oct 2014 05:24:10 -0500 [thread overview]
Message-ID: <544E1D4A.3010709@pabigot.com> (raw)
In-Reply-To: <544E099F.6060001@ti.com>
I think it would be more in keeping with the Yocto way if all these
firmware capabilities were added through PACKAGECONFIG options in a
meta-ti bbappend to linux-firmware, rather than through separate recipes.
This is especially true of the firmware added in linux-staging-ti. If
those patches are ever upstreamed (I assume that's the intent) then
stock linux-yocto kernels will be getting the images from
linux-firmware, and updated versions obtained in future linux-staging-ti
branches will conflict.
Last I looked, linux-staging-ti had a .elf format firmware blob, which
is not a supported format for linux-firmware. Adding it in a bbappend
produces a QA warning because it gets stripped and the debug version
doesn't get packaged. At that time, although both .bin and .elf
versions of that firmware were available, the code that loaded it would
only work with the .elf version.
In short, consistently putting firmware into linux-firmware now would
decrease integration issues both now and in the future.
Just a thought.
Peter
prev parent reply other threads:[~2014-10-27 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 17:38 [PATCH v3] ipumm-fw: Updated ipumm firmware for latest IPC version Denys Dmytriyenko
2014-10-22 18:05 ` Karthik Ramanan
2014-10-22 18:10 ` Karthik Ramanan
2014-10-22 18:17 ` Denys Dmytriyenko
2014-10-27 9:00 ` Karthik Ramanan
2014-10-27 10:24 ` Peter A. Bigot [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=544E1D4A.3010709@pabigot.com \
--to=pab@pabigot.com \
--cc=meta-ti@yoctoproject.org \
/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.