All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Kernel configuration
Date: Fri, 2 Jan 2015 19:08:28 -0500	[thread overview]
Message-ID: <CADkTA4MDLvwaGp_rcuUsOaXEC46_dxd6QH9k0PZmofhnxNLBoQ@mail.gmail.com> (raw)
In-Reply-To: <60148DA2-CAB2-416A-BDEE-783705B3E24E@keylevel.com>

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.

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).

Bruce

>
> --
>
> Chris Tapp
> opensource@keylevel.com
> www.keylevel.com
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


  parent reply	other threads:[~2015-01-03  0:08 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 [this message]
2015-01-03  0:57   ` Chris Tapp
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=CADkTA4MDLvwaGp_rcuUsOaXEC46_dxd6QH9k0PZmofhnxNLBoQ@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=opensource@keylevel.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.