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: Tue, 13 Oct 2015 09:37:47 -0300 [thread overview]
Message-ID: <CAP9ODKpLemLjQSi0bQKONYzH-Z22vQJswhpFnZgAC3FqTnSEOg@mail.gmail.com> (raw)
In-Reply-To: <CAGMdoFnUG+2eyH1C5OMi4P1yujk2KGH7zJVxCM+KagaDFxwYug@mail.gmail.com>
On Sun, Oct 11, 2015 at 4:49 PM, Edward Wingate <edwingate8@gmail.com> wrote:
> On Sun, Oct 11, 2015 at 11:38 AM, Edward Wingate <edwingate8@gmail.com> wrote:
>> So it doesn't seem like the kernel bbappend file is doing anything.
>
> I found out that if I put my defconfig in linux-wandboard/defconfig
> instead of files/defconfig, then it gets copied to
> .../tmp/work/wandboard-poky-linux-gnueabi/linux-wandboard/3.14.28-r0/defconfig.
> However the .config in
> .../tmp/work/wandboard-poky-linux-gnueabi/linux-wandboard/3.14.28-r0/build
> is still the original one without my config change.
>
> Seems like it is doing something now (copying defconfig over), but
> still doesn't seem like it gets used. There is no remoteproc module
> in the rootfs.
You need to adjust the search path for the files; check other bbappend
files for an example on this.
--
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-13 12:37 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 [this message]
2015-10-14 7:08 ` Edward Wingate
2015-10-14 12:52 ` Otavio Salvador
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=CAP9ODKpLemLjQSi0bQKONYzH-Z22vQJswhpFnZgAC3FqTnSEOg@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.