what is the "simplest unit of kernel Metadata"?

what is the "simplest unit of kernel Metadata"?

[Robert P. J. Day]

  kernel dev manual, section 3.4.1, claims:

"The simplest unit of kernel Metadata is the configuration-only
feature. This feature consists of one or more Linux kernel
configuration parameters in a configuration fragment file (.cfg) and a
.scc file that describes the fragment."

  that pretty clearly suggests that .cfg fragment files *must* be
accompanied by a related .scc file. but earlier in that same manual,
some examples use only .cfg files:

     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
     SRC_URI += "file://8250.cfg"

so how should that be worded?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is the "simplest unit of kernel Metadata"?

[Bruce Ashfield]

On 15-03-03 08:32 AM, Robert P. J. Day wrote:
>
>    kernel dev manual, section 3.4.1, claims:
>
> "The simplest unit of kernel Metadata is the configuration-only
> feature. This feature consists of one or more Linux kernel
> configuration parameters in a configuration fragment file (.cfg) and a
> .scc file that describes the fragment."
>
>    that pretty clearly suggests that .cfg fragment files *must* be
> accompanied by a related .scc file. but earlier in that same manual,
> some examples use only .cfg files:
>
>       FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>       SRC_URI += "file://8250.cfg"
>
> so how should that be worded?

It is talking about the in-tree meta-data, where .cfg files are
referenced and included by .scc files.

As a convenience to someone working in a recipe who really doesn't
care about the implementation details and just want to add a few
configuration items to their kernel .. A .cfg file that is referenced
in the SRC_URI is detected, and a .scc file generated to include that
fragment. So the end result is that the config items are processed
and merged into the kernel config, with no special processing of those
fragments required.

So the documentation is correct, but it is staying out of some of
the internal details of how that .cfg file actually gets processed.

Cheers,

Bruce

>
> rday
>