[OE-core] [RFC PATCH 6/6] classes/image: check kernel config supports IMAGE_FSTYPES items

Christopher Larson clarson at kergoth.com
Mon May 9 16:57:19 UTC 2016


On Mon, May 9, 2016 at 5:05 AM, Bruce Ashfield <bruce.ashfield at gmail.com>
wrote:

> On Mon, May 9, 2016 at 12:43 AM, Paul Eggleton <
> paul.eggleton at linux.intel.com> wrote:
>
>> A lot of the IMAGE_FSTYPES items require the appropriate filesystem
>> driver to be enabled in the kernel configuration; e.g. in order to read
>> a btrfs filesystem, the kernel must enable CONFIG_BTRFS_FS. Add a check
>> to ensure that is the case.
>>
>
>
> So what's the overall design for this ? Is it documented anywhere ? This
> is something
> that we talked about a couple of years and I have reservations and
> objections to
> the current implementation.
>
> .. but since I can only see bits and chunks of patches, I'd rather read
> something
> complete and offer some more detailed feedback.
>
> Bottom line: I see a slippery slope to tightly specified option that
> depend on kernel
> versions, I see kernel options sprayed all over layers, etc, etc. Which is
> exactly
> what we've been trying to avoid with the centralized kernel meta-data, and
> again,
> there's a mechanism that I finished early this year to extend those
> options to any
> kernel, enforce, warn, error, etc .. but now, I'll just toss it into the
> bin.
>

Perhaps this functionality should be by feature or capability rather than
individual options, and let the kernel build determine what features it
provides based on its configuration.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160509/fd221e89/attachment-0002.html>


More information about the Openembedded-core mailing list