From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Hongzhi, Song" <hongzhi.song@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: Is it necessary to fix the Bugzilla – Bug 11807 and 5876 ?
Date: Wed, 5 Dec 2018 05:57:26 -0500 [thread overview]
Message-ID: <a545e5df-65fc-1249-4fcd-d0c9b0175e27@windriver.com> (raw)
In-Reply-To: <3fdeffd5-0d20-b50a-0d8c-8aec3715ebb2@windriver.com>
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.
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.
Bruce
>
>
> --Honghzi
>
>
next prev parent reply other threads:[~2018-12-05 10:57 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 [this message]
2018-12-06 3:04 ` Hongzhi, Song
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=a545e5df-65fc-1249-4fcd-d0c9b0175e27@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=hongzhi.song@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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