From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Edward Wingate <edwingate8@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: remoteproc module
Date: Wed, 14 Oct 2015 09:52:58 -0300 [thread overview]
Message-ID: <CAP9ODKpxysJBYh9vNiTSfqU1XX99RDSyisFXvVGm-gj_-JQZsw@mail.gmail.com> (raw)
In-Reply-To: <CAGMdoF=988uYkAMvsoZYcBe=Hi5t4as-1ABoLZ6Ts-9ma0Bipg@mail.gmail.com>
On Wed, Oct 14, 2015 at 4:08 AM, Edward Wingate <edwingate8@gmail.com> wrote:
> On Tue, Oct 13, 2015 at 5:37 AM, Otavio Salvador
> <otavio.salvador@ossystems.com.br> wrote:
>> You need to adjust the search path for the files; check other bbappend
>> files for an example on this.
>
> I think my defconfig is being used, but then there is something else
> that goes on to overwrite my defconfig. My defconfig is copied to
> .../tmp/work/wandboard-poky-linux-gnueabi/linux-wandboard/3.14.28-r0.
> Then I believe it is being used to generate a .config. But then in
> the kernel build directory, I see my defconfig in a .config.old, while
> another .config takes its place. Any idea what could be doing this?
So it is lacking a dependency in the config chain or something. Check
kernel configuration and if it does provide the remoteproc feature
that you are looking for (I guess it does not).
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2015-10-14 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 18:23 remoteproc module Edward Wingate
2015-10-11 18:38 ` Edward Wingate
2015-10-11 19:49 ` Edward Wingate
2015-10-13 12:37 ` Otavio Salvador
2015-10-14 7:08 ` Edward Wingate
2015-10-14 12:52 ` Otavio Salvador [this message]
2015-10-14 14:20 ` Bob Cochran
2015-10-15 5:21 ` Edward Wingate
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=CAP9ODKpxysJBYh9vNiTSfqU1XX99RDSyisFXvVGm-gj_-JQZsw@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=edwingate8@gmail.com \
--cc=meta-freescale@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.