That's great! And just one line to add. Perfect solution!
Thanks a lot!
Michael
Am 02.05.2014 19:24, schrieb Bruce Ashfield:
> On 14-05-01 01:12 PM, Bruce Ashfield wrote:
>> On 14-05-01 02:32 AM, Neuer User wrote:
>>> Hi Bruce
>>>
>>> Here is the error messega, I get after a "bitbake linux-cubox
On 14-05-01 01:12 PM, Bruce Ashfield wrote:
On 14-05-01 02:32 AM, Neuer User wrote:
Hi Bruce
Here is the error messega, I get after a "bitbake linux-cubox-i -c
cleansstate; bitbake linux-cubox-i" using the recipe you posted:
Aha. This is what I was seeing as well, and there's some issues and
On 14-05-01 02:32 AM, Neuer User wrote:
Hi Bruce
Here is the error messega, I get after a "bitbake linux-cubox-i -c
cleansstate; bitbake linux-cubox-i" using the recipe you posted:
Aha. This is what I was seeing as well, and there's some issues and
assumptions
that are built into those kerne
Hi Bruce
Here is the error messega, I get after a "bitbake linux-cubox-i -c
cleansstate; bitbake linux-cubox-i" using the recipe you posted:
ERROR: Function failed: do_patch (log file is located at
/home/ubuntu/yocto/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/temp/log.do_pa
On 2014-04-30, 5:08 PM, Bruce Ashfield wrote:
On 14-04-28 09:54 AM, Neuer User wrote:
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
If you send me pointers to your bblayers and local.conf settings, I'll
run a build to see what happens here as well.
I'm always interested in tracking these down
On 14-04-28 09:54 AM, Neuer User wrote:
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
If you send me pointers to your bblayers and local.conf settings, I'll
run a build to see what happens here as well.
I'm always interested in tracking these down regardless.
Bruce
Testing this should be pr
Am 30.04.2014 21:21, schrieb Bruce Ashfield:
>
> Hrm. I have all the key layers right, which leaves me with the expansion
> issue. The README indicates the danny branch for the meta-fsl-* layers,
> is that what you are using ?
>
> Bruce
>
No, I'm using master-next. Only in master-next you can fi
On 14-04-30 03:16 PM, Neuer User wrote:
Am 30.04.2014 20:44, schrieb Bruce Ashfield:
Can you send me your bblayers out of band ? I'm using meta-fsl-arm
and meta-fsl-arm-extra to get a build going, and running into
expansion errors in the kernel recipes. Rather than hunt around
more than necessar
Am 30.04.2014 20:44, schrieb Bruce Ashfield:
> Can you send me your bblayers out of band ? I'm using meta-fsl-arm
> and meta-fsl-arm-extra to get a build going, and running into
> expansion errors in the kernel recipes. Rather than hunt around
> more than necessary, I'll check against your layers.
On 14-04-28 09:54 AM, Neuer User wrote:
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
If you send me pointers to your bblayers and local.conf settings, I'll
run a build to see what happens here as well.
I'm always interested in tracking these down regardless.
Bruce
Testing this should be pr
On 14-04-30 06:24 AM, Neuer User wrote:
Hi Bruce
Have you got any further?
Your timing is good. I was preeempted by another issue yesterday, but
I have the fsl-imx layers cloned and am about to start a build. I'll
send a follow up when I know more.
Bruce
I currently use a "defconfig" repla
Hi Bruce
Have you got any further?
I currently use a "defconfig" replacement, but honestly, it feels very
dumb. Fragments seem to be much smarter to combine and test different
configurations.
Cheers
Michael
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
> On 14-04-28 09:35 AM, Neuer User wrote:
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
>
> If you send me pointers to your bblayers and local.conf settings, I'll
> run a build to see what happens here as well.
>
> I'm always interested in tracking these down regardless.
>
> Bruce
>
Testing this should be pretty straightforward, if see
On 14-04-28 09:35 AM, Neuer User wrote:
Am 28.04.2014 15:16, schrieb Bruce Ashfield:
It all depends on how adventurous you are today :) Using a defconfig
will work, and you can generate one without much trouble. Using
fragments will allow you to keep your changes separate from the
baseline confi
Am 28.04.2014 15:16, schrieb Bruce Ashfield:
> It all depends on how adventurous you are today :) Using a defconfig
> will work, and you can generate one without much trouble. Using
> fragments will allow you to keep your changes separate from the
> baseline configuration, but you'll need to tweak
On 14-04-28 09:14 AM, Neuer User wrote:
Am 28.04.2014 15:03, schrieb Bruce Ashfield:
The answer to your question depends on the base linux-cubox-i
recipe.
Config fragment support works for kernels that inherit from linux-yocto,
versus ones that inherit directly from kernel.bbclass. So if you
p
Am 28.04.2014 15:03, schrieb Bruce Ashfield:
>
> The answer to your question depends on the base linux-cubox-i
> recipe.
>
> Config fragment support works for kernels that inherit from linux-yocto,
> versus ones that inherit directly from kernel.bbclass. So if you
> pop open that base recipe, and
On 14-04-28 04:03 AM, Neuer User wrote:
Hello
I am trying to add a custom kernel config to my layer. I followed the
following guide:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#creating-config-fragments
I have the following files in my layer:
recipes-kernel/linux/linux-cubo
18 matches
Mail list logo
