All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:08:44 -0700	[thread overview]
Message-ID: <27593.1667581724503766480@lists.openembedded.org> (raw)
In-Reply-To: <d682bdd7-ba1f-8708-fb64-6ae29b2ac074@theobroma-systems.com>

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

I have a linux-firmware_%.bbappend ( https://github.com/Freescale/meta-freescale-3rdparty/blob/kirkstone/recipes-kernel/linux-firmware/linux-firmware_%25.bbappend ) from meta-freescale-3rdparty layer. I think, it is too simple, it can not cause the problem. In my local.conf I set up to generate buildhistory (i used the following commands), soon my next image build is ready an i can share the results.

INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "0"

[-- Attachment #2: Type: text/html, Size: 552 bytes --]

  parent reply	other threads:[~2022-11-04 17:08 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
2022-11-04 14:07     ` [OE-core] " 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 [this message]
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=27593.1667581724503766480@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.