[OE-core] Is it necessary to fix the Bugzilla – Bug 11807 and 5876 ?

Hongzhi, Song hongzhi.song at windriver.com
Thu Dec 6 03:04:31 UTC 2018



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
>>
>>
>
>



More information about the Openembedded-core mailing list