Hi Wolfgang, It's true that specifically for the kernel we have no intrinsic way of verifying from the recipe that appropriate kernel functionality is enabled. It probably wouldn't be too hard to

Hello, I'm looking ofr a good way to deal with some build breakages caused by missing dependency checking. The problem: some packages require certain capabilities, without checking for these, and

Hi Rich, It sounds like it's working incorrectly. Since meta-raspberrypi constructs the SD card image using its own custom class I wonder if it has anything to do with that. Andrei, do you know

It probably depends on the BIOS, iirc, standard PXE does not support anything other than tfpt, but you can probably configure the IP settings manually, and I think the bios on the machine I was

Hi Thomas, My case is a bit more complicated as I also can't have non-secure (t)ftp! Are you saying that PXE can work without DHCP/BOOTP? I think this could be made a general use-case. A meta-layer

Depends on the bios, if your machine's bios supports PXE, then you do not need ipxe, just a tftp server set up on the LAN that serves PXELinux. I am wondering if having a thin meta-pxe layer would be

This patch and the related audit patch have been applied to both master and dylan branches. Thanks! --Mark

My apologies, I thought this had been integrated already. A similar patch has been pushed to the repository for the 'master' branch. I have not yet validated the dylan, but as you indicated it

Ahh I had a local version of this patch that I thought had been previously pushed. I've synced this and a few other changes and pushed to the meta-selinux repository. 'master' should now be current

On Jul 31, 2013, at 9:35 PM, Khem Raj <raj.khem@...> wrote: uci.bb Doubting that I can use Poky, or doubting that Poky will conflict with TI's arago? Or doubting that using 1.3 has any relevance to

Hi Tomas, Thanks, these look very useful. I think it is ;-) I think I'll still need to use ipxe as I need to be able to boot without DHCP support as well. Chris

Hi Paul, I'm running on Cedartrail, so this will probably work nearly as-is. Thanks. I need to use http rather then tftp, but that looks simple enough to do. I think I need to add a new image so

If I follow the instructions in Yocto's quick-start-guide and perform a simple build of core-image-minimal using today's master and make almost no changes to the configuration (other than to switch to

CQID: 418197 Reference /usr/sbin instead of the directory into which the script is installed on the host. Signed-off-by: Joe Slater <jslater@...> ---

From: Anders Hedlund <anders.hedlund@...> CQID: 428272 The audit build uses swig to generate a python wrapper. Unfortunately, the swig info file references host include directories. Some

Hi Paul, I commented out all the noexec flag settings in image.bbclass and the results are still the same. I was starting to get the suspicion that all of that content needed to be moved to a

The USB device port is fully supported in upstream Linux via the CONFIG_USB_EG20T driver. I tested this myself with the g_mass_storage driver and it is functional. The BSP is in the meta-minnow layer

To be completely accurate, they don't populate the rootfs directly, they install files into the ${D} directory (${WORKDIR}/image) during do_install, then do_package creates package definitions from

Hi Chris, I am attaching the patches I have, it's a bit raw, and needs more work before submitting for consideration in oe-core, but I think out of the box tftp support would be useful to have