Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Hongzhi, Song" <hongzhi.song@windriver.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: Is it necessary to fix the Bugzilla – Bug 11807 and 5876 ?
Date: Thu, 6 Dec 2018 11:04:31 +0800	[thread overview]
Message-ID: <b8a47a27-bc7c-8404-9133-2c036a25a930@windriver.com> (raw)
In-Reply-To: <a545e5df-65fc-1249-4fcd-d0c9b0175e27@windriver.com>



On 12/05/2018 06:57 PM, Bruce Ashfield wrote:
> On 12/5/18 5:17 AM, Hongzhi, Song wrote:
>> Hi all,
>>
>> I don't know if it is necessary to do this enhancement.
>>
>> 1. Bug 11807:
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=11807
>>
>>
>> 'CONFIG_EXTRA_FIRMWARE' is used to be set to the names of firmware 
>> files which
>>
>> should be provided by driver vendors.
>>
>> 'CONFIG_EXTRA_FIRMWARE_DIR' is set to a path which contains above 
>> firmware
>>
>> files. The default path is /lib/firmware if the 
>> 'CONFIG_EXTRA_FIRMWARE_DIR' is not set.
>>
>>
>> The path and firmware files must exist in rootfs eventually.
>>
>>
>> 2. Bug 5876:
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5876
>>
>>
>> I think it mean that bbclass should check the state of menuconfig.
>>
>>
>> I don't know if is necessary to fix these bugs. Could you give me help?
>
> I have some enhancements and other things in flight that can already do
> what these two bugs are talking about. Paul and I had discussed some of
> the config auditing on the list about a year ago, and agreed that
> there's no sense duplicating the functionality that already exists
> (rather I was going to tweak a few things to make it more easily
> accessible).
>
> If you want, you could assign 5876 to me, and I could take care of it.

Hi Bruce,

Thanks, I will assign it to you.

>
> As for 11807, that is simply a kernel configuration option and it should
> be handled like any other. I don't see the need for anything special to
> be done.
>

This option is different from the common options. It can only be set two 
types
of value, "" and "filename1 filename2 ...", which depends on customer.

Maybe we can add a variable containing useful firmware in kernel recipe 
for customer.
The variable will eventually set CONFIG_EXTRA_FIRMWARE in .config .

--Hongzhi

> Bruce
>
>
>>
>>
>> --Honghzi
>>
>>
>
>



  reply	other threads:[~2018-12-06  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 10:17 Is it necessary to fix the Bugzilla – Bug 11807 and 5876 ? Hongzhi, Song
2018-12-05 10:57 ` Bruce Ashfield
2018-12-06  3:04   ` Hongzhi, Song [this message]
2018-12-06  3:33     ` Hongzhi, Song
2018-12-06 21:48       ` Bruce Ashfield

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=b8a47a27-bc7c-8404-9133-2c036a25a930@windriver.com \
    --to=hongzhi.song@windriver.com \
    --cc=bruce.ashfield@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox