Re: Warning about auto generated BSP description

[Bruce Ashfield <bruce.ashfield@windriver.com>]

On 15-09-13 04:15 PM, Paul D. DeRocco wrote:
> I'm getting the following warning:
>
> [kernel]: An auto generated BSP description was used, this normally
> indicates a misconfiguration.
> Check that your machine (chroma-bsp) has an associated kernel description.
>
> Googling turns up the information that this is sometimes a spurious error
> and nothing to worry about, because a full BSP description isn't strictly
> required. However, as far as I can see I do indeed have a BSP description.
> I built the BSP using the yocto-bsp tool. It created a
> linux-yocto-rt_3.14.bbappend (since I'm using the RT kernel), and the
> following files:
>
>      chroma-bsp.cfg
>      chroma-bsp.scc
>      chroma-bsp-preempt-rt.scc
>      chroma-bsp-standard.scc
>      chroma-bsp-tiny.scc
>      chroma-bsp-user-config.cfg
>      chroma-bsp-user-features.scc
>      chroma-bsp-user-patches.scc

The tool may have created these files, but the question is .. were they
actually used.

That's what the check in question is trying to determine.

Rather than fail to build, the tools (kernel, not yocto-bsp) will
generate a skeleton BSP, and start the build. Chances are that
skeleton BSP isn't what you want .. and that's what the tools are
warning.

Clearly the message still needs more tweaking, as do the docs.

>
> The bbappend refers to chroma-bsp-preempt-rt.scc and the last three
> (empty) files. chroma-bsp-preempt-rt.scc contains the requisite KMACHINE,
> KTYPE and KARCH, and includes chroma-bsp.scc, which refers to
> chroma-bsp.cfg. This seems to fit the definition of a "BSP description" in
> 3.4.5 of the Kernel Development Manual. The whole BSP tree is called
> "meta-chroma-bsp" and that is indeed listed in my bblayers.conf. So why is
> it complaining?

What release are you using ? If you check something in the kernel meta
directory, I can tell you if the warning is wrong, or something is 
really being missed.

The reason I asked about the release, is that the location of the kernel
meta directory will be in a different place between the various
releases. But it is always in the kernel source directory, whether it is
in work-shared, or in work. So if you head to that directory and look
for either .meta or .kernel-meta, you should see a file "top_tgt" in that
directory.

Look at the contents of that file. It should point to those generated
files you referenced above. If it doesn't .. they weren't used, and we
need to figure out why.

Cheers,

Bruce

>
> Also, I don't know that "Check that your machine has an associated kernel
> description" means. The term "kernel description" doesn't appear anywhere
> in the docs.
>