All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Tapp <opensource@keylevel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Kernel configuration
Date: Sat, 3 Jan 2015 00:57:50 +0000	[thread overview]
Message-ID: <AB3518D3-AE10-4889-ADB6-8A662EF8C458@keylevel.com> (raw)
In-Reply-To: <CADkTA4MDLvwaGp_rcuUsOaXEC46_dxd6QH9k0PZmofhnxNLBoQ@mail.gmail.com>

Hi Bruce,

On 3 Jan 2015, at 00:08, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

> On Fri, Jan 2, 2015 at 9:52 AM, Chris Tapp <opensource@keylevel.com> wrote:
>> I thought I knew how to do this, but... ;-)
>> 
>> I'm trying to add configuration items to the valleyisland BSP. I've got the following bbappend:
>> 
>> File: linux-yocto_3.10.bbappend
>> -------
>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> 
>> SRC_URI += " file://enable-hid-apple.cfg"
>> SRC_URI += " file://enable-R8169.cfg"
>> 
>> However, these .cfg fragments aren't even getting pulled into the build area.
>> 
>> Adding a reference to a non-existent file is ignored when I would have expected to see a fetch error
>> 
>> SRC_URI += "file://fsdfsdfdsfsd"
>> 
>> What else do I need to do to get my .cfg files pulled in?
> 
> What release / branch is this with ? What you have above is all that you need
> to do. I'm not near my development machine, but will be on Monday and can
> confirm that something hasn't been broken.

This is with 'daisy'.

> In the meantime, have you dumped the environment to confirm that that your
> values really are on the SRC_URI and that something else in the layers
> isn't coming along later and clobbering the SRC_URI (unlikely, but worth ruling
> out).

Ah - that shows:

# $SRC_URI [8 operations]
#   set /media/SSD-RAID/poky-git/meta/conf/bitbake.conf:588
#     ""
#   set /media/SSD-RAID/poky-git/meta/conf/documentation.conf:378
#     [doc] "The list of source files - local or remote. This variable tells the OpenEmbedded build system what bits to pull in for the build and how to pull them in."
#   set /media/SSD-RAID/poky-git/meta/recipes-kernel/linux/linux-yocto_3.10.bb:23
#     "git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
#   append /media/SSD-RAID/meta-keylevel-sjs/project-specific-layers/opty4-valleyisland/recipes-kernel/linux/linux-yocto_3.10.bbappend:4
#     " file://enable-R8169.cfg"
#   append /media/SSD-RAID/meta-keylevel-sjs/project-specific-layers/opty4-valleyisland/recipes-kernel/linux/linux-yocto_3.10.bbappend:5
#     "file://fsdfsdfdsfsd"
#   finalize ast.py:323 [finalize]
#     "was: git://git.yoctoproject.org/linux-yocto-3.10.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta  file://enable-R8169.cfg file://fsdfsdfdsfsd"
#   override[valleyisland-64]:set /media/SSD-RAID/meta-intel-git-2/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.10.bbappend:33
#     "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-io-3.0;name=machine,meta,valleyisland-io"
#   finalize override[valleyisland-64]:
#     "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-io-3.0;name=machine,meta,valleyisland-io"
# computed:
#   "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-io-3.0;name=machine,meta,valleyisland-io"
SRC_URI="git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;nocheckout=1;branch=standard/base,meta,valleyisland-io-3.0;name=machine,meta,valleyisland-io"

If I change my bbappend to use lines of the form:

  SRC_URI_valleyisland-64 += " file://enable-R8169.cfg"

then the fragments make it in to the configuration.

I've never really understood machine overrides that well - I thought that using a plain SRC_URI would apply regardless, but that's obviously not the case ;-)

Thanks for the pointer :-)

--

Chris Tapp
opensource@keylevel.com
www.keylevel.com

----
You can tell you're getting older when your car insurance gets real cheap!



  reply	other threads:[~2015-01-03  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 14:52 Kernel configuration Chris Tapp
2015-01-02 16:26 ` Jacob Kroon
2015-01-02 20:20   ` Chris Tapp
2015-01-03  0:08 ` Bruce Ashfield
2015-01-03  0:57   ` Chris Tapp [this message]
2015-01-19 14:37     ` Paul Eggleton
2015-01-19 20:43       ` Chris Tapp
  -- strict thread matches above, loose matches on Subject: below --
2021-02-27 14:37 Leandro Bucci
2021-02-27 14:56 ` Greg Gallagher
2021-02-27 23:48   ` Leandro Bucci
2011-04-26  3:32 kernel configuration lina
2003-09-09 15:10 atticclaw
2003-09-09 16:29 ` James Miller
2003-09-09 19:04   ` Ray Olszewski
2003-09-09 20:59     ` James Miller (office)
2001-10-16 15:52 Kamil Kompa

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=AB3518D3-AE10-4889-ADB6-8A662EF8C458@keylevel.com \
    --to=opensource@keylevel.com \
    --cc=bruce.ashfield@gmail.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.