[Arm-netbook] meta-allwinner

[lkcl luke]

On Fri, Jun 8, 2012 at 9:05 AM, Enrico <ebutera at users.sourceforge.net> wrote:
> On Fri, Jun 8, 2012 at 1:13 AM, lkcl luke <luke.leighton at gmail.com> wrote:
>> On Fri, Jun 8, 2012 at 12:01 AM, Enrico <ebutera at users.sourceforge.net> wrote:
>>> On Fri, Jun 8, 2012 at 12:24 AM, Henrik Nordström
>>> <henrik at henriknordstrom.net> wrote:
>>>> Have not managed to boot it yet, but not sure if that's your or my
>>>> problem..
>>>>
>>>> What I did notice however is that the rootfs do contain the uImage and
>>>> one kernel module. Is this intentional?
>>>
>>> Yes, they are included in the rootfs tar by oe.
>>>
>>> Additional modules are in the modules-xxx.tar.gz, i never investigated
>>> what's the criteria to put a module in the rootfs or in the modules
>>> tar gz...
>>
>>  there's a way to specify modules that should be built (and installed)
>> in openembedded's bitbake build files, it's quite easy to do, i forget
>> exactly how - something like ooo... LINUX_KERNEL_modules += "{insert
>> modules here}" where _modules is what does the trick.  the thing is
>> though that the "include" system is often over-used so you have to
>> hunt through half a dozen files, tracking each include as you find
>> them, to locate where a module might be being added.
>
> You can add kernel modules to the image adding "kernel-module-xxxx" to
> the image recipe, some kernel modules are automatically added because
> of dependencies so that's why they end up in the rootfs without you
> specifing it.

 that's it.  yep.  it's been a while since i looked at this stuff.
so, henrik somewhere buried deep in some nested includes there's a
kernel-module-2.6.36 += "usb_gadget" kicking around.

 l.