From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: How to use linux-firmware to install single firmware package? #kirkstone
Date: Fri, 04 Nov 2022 05:42:06 -0700 [thread overview]
Message-ID: <17126.1667565726738758884@lists.openembedded.org> (raw)
In-Reply-To: <3ac2df35-d9be-5b2d-1576-38ba5a712d56@theobroma-systems.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
In my tmp/deploy/rpm/noarch folder i can see many-many other firmware .rpm files like linux-firmware-bcm43xx, linux-firmware-nvidia-tegra and so on, these were not planed to be installed. It seems to me, the full linux-firmware package was deployed somehow. I think i am using poky now, this is my path for linux-firmware: PROJECT/sources/poky/meta/recipes-kernel/linux-firmware/linux-firmware_20220913.bb
So, my poky come from git.yoctoproject.org ( https://git.yoctoproject.org/poky/log/?h=kirkstone ) , i use latest kirkstone commit ( https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=2e79b199114b25d81bfaa029ccfb17676946d20d ).
In pn-buildlist and task-depends.dot i can see only linux-firmware, i have no any listed single package like should be linux-firmware-imx-sdma-imx7d.
[-- Attachment #2: Type: text/html, Size: 904 bytes --]
next prev parent reply other threads:[~2022-11-04 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 23:07 How to use linux-firmware to install single firmware package? #kirkstone Livius
2022-11-04 9:13 ` [OE-core] " Quentin Schulz
2022-11-04 12:42 ` Livius [this message]
2022-11-04 14:07 ` Quentin Schulz
2022-11-04 14:59 ` Vincent Davis Jr
2022-11-04 16:18 ` [OE-core] " Alexander Kanavin
2022-11-04 17:08 ` Livius
2022-11-04 18:44 ` Livius
2022-11-07 13:03 ` [OE-core] " Quentin Schulz
-- strict thread matches above, loose matches on Subject: below --
2023-02-26 3:03 Yang, Wilson
2023-02-26 3:25 ` Vincent Davis Jr
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=17126.1667565726738758884@lists.openembedded.org \
--to=egyszeregy@freemail.hu \
--cc=openembedded-core@lists.openembedded.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.