Guys,

As I told before, I already tried the config fragment strategy and it did
not worked too.

Looking at linux-mailine-3.8.bb from meta-beagleboard[1] it just inherits
kernel and not inherits linux-yocto or requires linux-yocto.inc. So I
believe that the config fragment will not work. But I can be wrong.

On directory "meta-mine/recipes-kernel/linux/" I have this:

.
├── files
│   ├── mine.patch
│   └── defconfig
└── linux-mainline_3.8.bbappend


And my linux-mainline_3.8.bbappend recipe:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += " file://mine.patch \
             file://defconfig \
             "

The mine.patch is applied but defconfig not.

I've already tried to use another FILESEXTRAPATHS layout like[2],but no
success too.

How can I have the "bb" command listed on the following link?
http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS


[1] -
 https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
[2] -
http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/15 Andrea Adami <andrea.adami@gmail.com>

> Hi,
>
> I guess you're setting a wrong FILESEXTRAPATHS_prepend :=
> "${THISDIR}/files:"
>
> See this example, using simple defconfig for some devices and an
> experimental configuration (WIP ;) fo others using fragments.
>
>
> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend
>
> Cheers
>
> Andrea
>
>
> On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif
> <rstreif@linuxfoundation.org> wrote:
> > Diego,
> >
> > You are appending a kernel recipe that uses the Linux Yocto tooling. The
> > defconfig is essentially comprised of many different pieces from the meta
> > branch of the Yocto kernel repository and optional configuration
> fragments
> > that you provide. This tooling will not recognize a defconfig file you
> > provide but it does recognize configuration fragments to be added to
> > .config.
> >
> > You need to put
> >
> > CONFIG_WATCHDOG_NOWAYOUT=y
> >
> > into a file that ends with .cfg eg. watchdog.cfg and then modify your
> > bbappend to
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> > SRC_URI += " file://0019-mine.patch \
> >              file://watchdog.cfg \
> >              "
> >
> > Rudi
> >
> >
> >
> > On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com>
> > wrote:
> >>
> >> Folks,
> >>
> >> I created the following bbapend recipe for linux-mainline_3.8.bb (from
> >> meta-beagleboard on dylan branch) for beaglebone.
> >> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
> >>
> >> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> >> SRC_URI += " file://0019-mine.patch \
> >>              file://defconfig \
> >>              "
> >>
> >> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
> >> meta-beagleboad, not from my bbappend.
> >>
> >> I tried to follow the instructions to add config fragments on the page
> >> below but it did not worked too.
> >>
> >>
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
> >>
> >> The strange thing is: My patch is applied but my defconfig, or config
> >> fragment is not used.
> >> I just want to add CONFIG_WATCHDOG_NOWAYOUT=y.
> >>
> >> I already did a cleasstate but no success.
> >>
> >> Any hints?
> >>
> >>
> >> Regards,
> >>
> >> --
> >> *dS
> >> Diego Sueiro
> >>
> >> /*long live rock 'n roll*/
> >>
> >> _______________________________________________
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >>
> >
> >
> >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>