All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>, <yocto@yoctoproject.org>
Subject: Re: Warning about auto generated BSP description
Date: Mon, 14 Sep 2015 13:41:02 -0400	[thread overview]
Message-ID: <55F706AE.6080208@windriver.com> (raw)
In-Reply-To: <17509C1F9D0D41DE8575215D4D609FBC@PAULD>

On 15-09-14 01:38 PM, Paul D. DeRocco wrote:
>> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
>>
>> The tool may have created these files, but the question is ..
>> 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.
>
> I'm using Fido.
>
>> 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.
>
> The file
> "/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
> ta/top_tgt" contains
> "/home/pauld/yocto-fido/build/tmp/work-shared/chroma-bsp/kernel-source/.me
> ta/cfg/scratch/obj/home/pauld/yocto-fido/meta-chroma-bsp/recipes-kernel/li
> nux/files/chroma-bsp-preempt-rt.scc". That referenced folder includes a
> copy of all the .scc and .cfg files I mentioned before. I guess that means
> that they are in fact being used.

Yep. If everything was copied, then you are good.

And now that you point that out, I recall a bug that when I created
that warning, that it was catching the yocto BSP generated files.
I swear I fixed it, but obviously not. I'll need to track down that
bugzilla entry.

Bruce

>
> Does that mean that this warning message is spurious, and can be ignored?
> My kernel is hanging during the boot at this point, but I suspect my real
> problem is elsewhere.
>
> Thanks so much for your time helping me to figure this out.
>



      reply	other threads:[~2015-09-14 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 20:15 Warning about auto generated BSP description Paul D. DeRocco
2015-09-14  1:40 ` Robert Calhoun
2015-09-14  8:48   ` Paul D. DeRocco
2015-09-14 14:11 ` Bruce Ashfield
2015-09-14 17:38   ` Paul D. DeRocco
2015-09-14 17:41     ` Bruce Ashfield [this message]

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=55F706AE.6080208@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=pderocco@ix.netcom.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.