On Fri, 2013-12-06 at 14:08 -0500, r10kindsofpeople wrote:
> After some success building my system (crownbay), I'm now trying to
> optimize boot time, so I read up on poky-tiny, created a new layer and
> am trying to build. I think I've pulled most of my system changes out
> so that I can at least
After some success building my system (crownbay), I'm now trying to
optimize boot time, so I read up on poky-tiny, created a new layer and am
trying to build. I think I've pulled most of my system changes out so that
I can at least bitbake core-image-minimal, but I'm still not able to get
past ncu
It seems weird that you can fully setup wifi with nmcli, but you can't set up a
basic static wired network, you have to do it
the old way with network/interfaces ... where is the consistency?
Sent from Samsung tablet
Original message
From: Gaurang Shastri
Date: 06/12/2013
On 2013-12-06 08:15, Chris Larson wrote:
On Fri, Dec 6, 2013 at 8:08 AM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
The 'git' fetcher was recently changed to expect/need the branch
name for the desired revision. Many recipes don't have this and
the revision is not on the master
On Fri, Dec 6, 2013 at 8:08 AM, Gary Thomas wrote:
> The 'git' fetcher was recently changed to expect/need the branch
> name for the desired revision. Many recipes don't have this and
> the revision is not on the master branch, hence leading to errors
> like this:
> ERROR: Fetcher failure: Una
The 'git' fetcher was recently changed to expect/need the branch
name for the desired revision. Many recipes don't have this and
the revision is not on the master branch, hence leading to errors
like this:
ERROR: Fetcher failure: Unable to find revision
f89bc066db0569008418fac1a0408a9a57f2232f
I understand, thanks a lot.
Cheers,
Bruce
On Fri, Dec 6, 2013 at 10:48 PM, Kumita Bruce wrote:
> So for |, user only needs to comply with either one, for &, user needs to
> follow all, right?
>
>
> Cheers,
>
> Bruce
>
>
> On Fri, Dec 6, 2013 at 10:37 PM, Chris Larson wrote:
>
>> On Fri, Dec
So for |, user only needs to comply with either one, for &, user needs to
follow all, right?
Cheers,
Bruce
On Fri, Dec 6, 2013 at 10:37 PM, Chris Larson wrote:
> On Fri, Dec 6, 2013 at 7:23 AM, Kumita Bruce wrote:
>
>> I don't know whether this is the right place to ask the question. Hope to
Hi All,
I am trying to setup yocto-autobuilder on my remote server to enable
nightly builds for my project.
I have done the following so far:
- download yocto-autobuilder from git.yoctoproject; master branch
- installed tightvnc server and viewer.
- installed expect, read that it was a dependency
On 6 December 2013 14:23, Kumita Bruce wrote:
> I don't know whether this is the right place to ask the question. Hope to
> get some help from here.
>
> I see below two types definition of LICENSE in Yocto recipe:
> LICENSE = "license-1 & license-2"
> LICENSE = "license-1 | license-2"
>
> Can some
On Fri, Dec 6, 2013 at 7:23 AM, Kumita Bruce wrote:
> I don't know whether this is the right place to ask the question. Hope to
> get some help from here.
>
> I see below two types definition of LICENSE in Yocto recipe:
> LICENSE = "license-1 & license-2"
> LICENSE = "license-1 | license-2"
>
> C
Hi,
I don't know whether this is the right place to ask the question. Hope to
get some help from here.
I see below two types definition of LICENSE in Yocto recipe:
LICENSE = "license-1 & license-2"
LICENSE = "license-1 | license-2"
Can somebody help to give some explanation for the difference of
David,
This patch did not format well when I sent to my Linux box. I cannot
apply it. I can apply it by hand or you can try and form the patch
again and re-send it to the yocto@yoctoproject.org mailing group.
Thanks,
Scott
On 12/5/2013 6:44 AM, David Nyström wrote:
This reverts commit f80
Hi all,
I am new to yocto project.
Can anyone please tell me which is the most suitable kernel version in
yocto project to bring up camera module from leopard imaging on Beagle
board-xM
I have Beagleboard-xM revision C with two camera module LI-LBCMVGA and
LI-LBCM3M1.
Regards,
VG
___
14 matches
Mail list logo
