[yocto] [meta-selinux][PATCH] policycoreutils: drop the patch for old refpolicy

From: Jackie Huang The patch policycoreutils-revert-run_init-open_init_pty.patch is only for refpolicy version older than 2.20120725, now the refpolicy is updated to 2.20130424 so drop the patch or it will make run_init fail to start some init scripts. Signed-off-by: Jackie Huang --- ...cycore

Re: [yocto] Building on target

usbip from /usr/src/kernel/drivers/staging/usbip On Wed, Mar 12, 2014 at 11:44 AM, Gary Thomas wrote: > On 2014-03-12 10:09, Rick Bianchi wrote: > > I completely agree with regards to the comparison, but I have compiled > the same exact source on the same target (arm) and it only took 5 minutes

Re: [yocto] SysVinit and psplash

David, Thanks for that pointer. I updated my u-boot ini file to pass the console=tty2 to the kernel command line and it took care of the problem. -Kevin From: David Welch [djwelch...@gmail.com] Sent: Wednesday, March 12, 2014 4:39 AM To: Kevin Evans Cc: yocto@yo

Re: [yocto] Building on target

On 2014-03-12 10:09, Rick Bianchi wrote: > I completely agree with regards to the comparison, but I have compiled the > same exact source on the same target (arm) and it only took 5 minutes when > running the Linaro image. > > To clarify, the only difference is the build, one is Linaro (took 5 m

[yocto] ADT: understanding YOCTOADT_TARGET_MACHINE_arch

Hi list, I've been looking at the ADT, and specifically building a custom SDK/ADT for a particular board... This is an ARM board, so I thought I'd set: YOCTOADT_TARGET_MACHINE_arm="myboard" Sadly, that doesn't work. I'm trying to understand why. Despite changing YOCTOADT_REPO in my adt_insta

Re: [yocto] Building on target

On 03/12/2014 04:28 PM, Gary Thomas wrote: > On 2014-03-12 09:15, Rick Bianchi wrote: >> >> I have the gumstix-console-image with the added packages below. When I >> compile on the target is take a very long time for it to complete, over 24 >> hours. I have compiled the same >> code on the same t

Re: [yocto] Building on target

I completely agree with regards to the comparison, but I have compiled the same exact source on the same target (arm) and it only took 5 minutes when running the Linaro image. To clarify, the only difference is the build, one is Linaro (took 5 minutes to compile source on the target) and the other

Re: [yocto] Building on target

On 2014-03-12 09:15, Rick Bianchi wrote: > > I have the gumstix-console-image with the added packages below. When I > compile on the target is take a very long time for it to complete, over 24 > hours. I have compiled the same > code on the same target, but running Linaro image, and it only take

[yocto] Building on target

I have the gumstix-console-image with the added packages below. When I compile on the target is take a very long time for it to complete, over 24 hours. I have compiled the same code on the same target, but running Linaro image, and it only takes a few minutes. Is there another recipe that I need t

Re: [yocto] Autotools not configuring

Hi, On Mon, Mar 10, 2014 at 3:24 PM, sheerapthinath wrote: > Can anyone please tell whats wrong with the recipe and why am getting > this error? I think you need to share the contents of hello/ in order for anyone to be able to help. It sounds very much like you just lack a install target in you

Re: [yocto] Creating an installer for your Yocto image.

Hi David, On 12/03/2014 10:35, David Welch wrote: > Hi, > > Currently we are dd'ing a yocto created image to a hd. This works great > for having our production people create new machines in a factory. > > I have a new requirement now for what happens if we want to re-image a > machine in the fi

Re: [yocto] SysVinit and psplash

I too found this to be a problem. Setting console=tty2 made the messages come out on another console and not visible on the screen. On Mon, Mar 10, 2014 at 4:19 PM, Kevin Evans wrote: > Hello all: > > I am using yocto denzil release with an IGEPv2 (beagle board clone). It > appears the init i

[yocto] Creating an installer for your Yocto image.

Hi, Currently we are dd'ing a yocto created image to a hd. This works great for having our production people create new machines in a factory. I have a new requirement now for what happens if we want to re-image a machine in the field. Ideally I would like to be able to insert a USB stick and h

Re: [yocto] Working with a git'ed kernel on the server

On 2014-03-11, 6:10 PM, Paul Eggleton wrote: On Tuesday 11 March 2014 22:05:53 Paul Eggleton wrote: On Tuesday 11 March 2014 17:53:04 Bruce Ashfield wrote: On 2014-03-11, 3:22 PM, Andy Ng wrote: Thank you, I've just noticed my bb file has: SRCREV_pn-${PN} = "${AUTOREV}" So it should be ok?