remoteproc module

remoteproc module

[Edward Wingate]

I'm trying to get the remoteproc module onto my wandboard image, but
not having much luck.

I created a linux-wandboard_3.14.28.bbappend recipe with the following:
    FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
    SRC_URI += "file://defconfig"

In my recipe folder, I created files/defconfig.  I got defconfig from
an existing .config in
.../tmp/work/wandboard-poky-linux-gnueabi/linux-wandboard/3.14.28-r0/build
folder and added:
    CONFIG_REMOTEPROC=m

In my image conf, I added:
    MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-remoteproc"

With this, I would expect remoteproc.ko module in /lib/modules
directory, but there is no /lib/modules directory at all in the
rootfs.  What am I missing?

I realize even if this worked, remoteproc won't actually do anything
at this point, but I just wanted to take the first steps towards
creating my own remoteproc module by seeing what steps to take to get
the base remoteproc module built and deployed.  Thanks for you help.

Re: remoteproc module

[Edward Wingate]

On Sun, Oct 11, 2015 at 11:23 AM, Edward Wingate <edwingate8@gmail.com> wrote:
> I'm trying to get the remoteproc module onto my wandboard image, but
> not having much luck.

I forgot to mention that after doing a clean and compile, the .config
in .../tmp/work/wandboard-poky-linux-gnueabi/linux-wandboard/3.14.28-r0/build
does not have my addition of CONFIG_REMOTEPROC=m.

So it doesn't seem like the kernel bbappend file is doing anything.

Re: remoteproc module

[Edward Wingate]

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.

Re: remoteproc module

[Otavio Salvador]

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

Re: remoteproc module

[Edward Wingate]

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?

Re: remoteproc module

[Otavio Salvador]

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

Re: remoteproc module

[Bob Cochran]

On 10/14/2015 08:52 AM, Otavio Salvador wrote:
> 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).
>

Have you looked at run.do_configure in your temp directory?  You should 
be able to find the lines that copy the defconfig and figure it out from 
there.

Also, as Otavio previously pointed out, make sure you understand your 
file search path.  Grep on ^FILESPATH= after running a

$ bitbake virtual/kernel -e

It can be helpful to redirect this to a file for further examination:

$ bitbake virtual/kernel -e > linux.out



Bob

Re: remoteproc module

[Edward Wingate]

On Wed, Oct 14, 2015 at 7:20 AM, Bob Cochran <yocto@mindchasers.com> wrote:
> Also, as Otavio previously pointed out, make sure you understand your file
> search path.  Grep on ^FILESPATH= after running a
>
> $ bitbake virtual/kernel -e

The directory with my defconfig is the very first directory in
FILESPATH.  Does that mean mine should take precedence over all
others?

> Have you looked at run.do_configure in your temp directory?  You should be
> able to find the lines that copy the defconfig and figure it out from there.
> Have you looked at run.do_configure in your temp directory?  You should be
> able to find the lines that copy the defconfig and figure it out from there.

Yes, in run.do_configure I see where my defconfig is copied (via sed)
to build/.config.  I see a few conditionals after that where if
build/.config doesn't exist, then it'll copy some other defconfig to
build/.config.  But I don't see anything that renames an existing
build/.config to build/.config.old and uses another defconfig.

I put the run.do_configure here: http://pastebin.com/zPfuSwTV
I'd appreciate any further pointers to tracking this down.