[meta-freescale] Trouble with i.mx28evk

[Daiane Angolini]

On Thu, Feb 12, 2015 at 1:23 PM, Mark Lane <mark at 2100computerlane.net> wrote:
>
>
> On Wed, Feb 11, 2015 at 6:43 PM, Mark Lane <mark at 2100computerlane.net>
> wrote:
>>
>> Thanks I was actually looking for a longer list of what options I would
>> have there.
>>
>> On Wed, Feb 11, 2015 at 5:47 PM, Daiane Angolini <daiane.list at gmail.com>
>> wrote:
>>>
>>> On Wed, Feb 11, 2015 at 7:42 PM, Mark Lane <mark at 2100computerlane.net>
>>> wrote:
>>> >>
>>> >> On Wed, Feb 11, 2015 at 4:36 PM, Otavio Salvador
>>> >> <otavio at ossystems.com.br>
>>> >> wrote:
>>> >>>
>>> >>> On Wed, Feb 11, 2015 at 7:35 PM, Mark Lane
>>> >>> <mark at 2100computerlane.net>
>>> >>> wrote:
>>> >>> > ROFL no I am using the tool chain. The developer who is working
>>> >>> > with the
>>> >>> > Zigbee device wants to develop on the mx28 so he might try and
>>> >>> > build a
>>> >>> > kernel module on it though.
>>> >>>
>>> >>> Still better to do it outside using the toolchain. I'd likely use the
>>> >>> toolchain and NFS to speed up the development process.
>>> >>>
>>> >>> --
>>> >>> 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
>>> >>
>>> >>
>>> >> As far as I know, He's trying to do this from windows with ubuntu
>>> >> running on
>>> >> a vm to begin with. Who knows if he even has proper usb support from
>>> >> the vm
>>> >> to the target. I will probably make a nfs build which I will used but
>>> >> at
>>> >> this point I am trying to get him started with what he wants.
>>> >>
>>>
>>>  I should be very crazy, because I see a lot of people developing linux
>>>  kernel in a windows machine O.O
>>>
>>>  Something I think is completely infeasible.
>>>
>>>  Now coming back to your problem, I still don't understand If you want
>>> the header files into the rootfs or the *.ko files that are missing
>>>
>>> Take a look here on how to add some native development features to your
>>> image:
>>>
>>>
>>> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-features-image
>
>
> The rootfs still does not contain .ko images. The minimal build seems to
> leave them out and I can seem to find an option to change that. Can I
> changed that with a recipe?

FSL Community BSP state the kernel modules as MACHINE_EXTRA_RRECOMMENDS

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/conf/machine/include/imx-base.inc#n31


And core-image-minimal does not include RRECOMMENDS (only DEPENDS)

I don't remember if core-image-full-cmdline does include, so you
should double check it.

You can read more about the meaning of "EXTRA" "ESSENTIAL" "DEPENDS"
or "RRECOMMENDS" here:

http://www.yoctoproject.org/docs/1.7.1/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules




Daiane