[yocto] [PATCH v1] u-boot/beaglebone: Select Beaglebone Black target specifically.

The am335x_evm_config target has a subtle problem which is not present in the am335x_boneblack_config target: When booting from an external MMC card, the internal MMC is not accessible using the former target. This problem was introduced in U-Boot in commit 80b24fcd3083515e6b961, due to the

[yocto] How to get headers installed at target side of SDK?

I'm a little confuse, so I may be about to say non-sense. Correct me if I'm wrong... I'm trying to get some headers installed at SDK so that programs compiled with it see that headers. I tried appending nativesdk-packagegroup-sdk-host adding my nativesdk-foo-dev as dependence to it. With this I

[yocto] distutils break my shebang, what to do?

Hi, I've been trying to install cxxtest to nativesdk. After done I went to run`cxxtestgen` and got a "bad interpreter" error from bash. I look at the script and there was "#! python" at first line. I know that this is something that distutils does. I also know that SDK ships its own python

Re: [yocto] Multiple Projects from the same build directory

Create two recipes that fetch from same source but compile A or B. Something like A.bb and B.bb with same SRC_URI but distinct do_compile. So you can bbappend they independently. You can maintain the common parts at a .inc file also to keep DRY principle. Cheers, 2016-12-15 19:46 GMT-02:00 Rick

[yocto] Multiple Projects from the same build directory

I'll admit I'm being a bit lazy. I have two related projects, will call them A and B. B is dependent on A's layers and adds its own. So far, there have been no issues with just building them in the same directory since they have separate image recepies. However, I'm shortly going to be needing to

Re: [yocto] [recipetool] Failure to create a new recipe (failed to parse setup.py)

Hi Paul, On 12/15/2016 9:28 AM, Paul Eggleton wrote: Sorry for not getting back to you earlier - the patch got sent shortly after our discussion and has now been merged: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8fe1f25ea087cea13c5380de758078f0fb9eae34 Thanks for the link,

[yocto] live" image: iso and ext4 artifacts

Hello Yocto. I am trying x86-64 BSP image (based on jethro version). It has following root filesystem type, and it generats .hddimg file that I am using. > IMAGE_FSTYPES = "live" The issue is that in addition to .hddimg, it produces following image files and it sometimes cause lack of

Re: [yocto] [meta-inte][rmc][PATCH v2 1/1] rmc: add support for alternative EFI bootloaders

On 12/15/2016 10:23 AM, Todor Minchev wrote: On Thu, 2016-12-15 at 10:09 -0800, Cal Sullivan wrote: On 12/13/2016 04:50 PM, Todor Minchev wrote: On Tue, 2016-12-13 at 16:22 -0800, Jianxun Zhang wrote: On Dec 13, 2016, at 2:56 PM, Todor Minchev wrote: RMC

Re: [yocto] [meta-inte][rmc][PATCH v2 1/1] rmc: add support for alternative EFI bootloaders

On Thu, 2016-12-15 at 10:09 -0800, Cal Sullivan wrote: > > On 12/13/2016 04:50 PM, Todor Minchev wrote: > > > > On Tue, 2016-12-13 at 16:22 -0800, Jianxun Zhang wrote: > > > > > > > > > > > On Dec 13, 2016, at 2:56 PM, Todor Minchev > > > .intel.com> wrote: > > > > > >

Re: [yocto] [meta-inte][rmc][PATCH v2 1/1] rmc: add support for alternative EFI bootloaders

On 12/13/2016 04:50 PM, Todor Minchev wrote: On Tue, 2016-12-13 at 16:22 -0800, Jianxun Zhang wrote: On Dec 13, 2016, at 2:56 PM, Todor Minchev wrote: RMC was previously configured to work only with the systemd-boot EFI bootloader. With this commit we can

Re: [yocto] [recipetool] Failure to create a new recipe (failed to parse setup.py)

Hi Vincent, On Wed, 14 Dec 2016 20:59:27 Vincent Rubiolo wrote: > On 12/04/2016 11:14 AM, Paul Eggleton wrote: > > Hmm, it looks like we're treating a byte array as a string (i.e. missing > > decoding) and that doesn't work. Likely this broke during the Python3 > > migration, and since there are

Re: [linux-yocto] [yocto-kernel-cache][PATCH] netfilter: enable connection tracking for IPv6

On 2016-12-12 10:04 AM, Dmitry Rozhkov wrote: In case of the DROP policy in the INPUT chain a host using IPv6 still might need to receive TCP packets for established connections, that is to have the rule -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT in its INPUT chain of

Re: [yocto] NFS rootfs: mount: only root can mount proc on /proc

2016-12-15 12:09 GMT-02:00 Anders Darander : > Hi, > > * John Rama [161215 02:58]: > >> The ideas I can come up with are followings, but those of them are not >> perfect.. >> 1. Run the bitbake as root account >> - would not run as root since the

Re: [yocto] NFS rootfs: mount: only root can mount proc on /proc

Hi, * John Rama [161215 02:58]: > The ideas I can come up with are followings, but those of them are not > perfect.. > 1. Run the bitbake as root account > - would not run as root since the all of generated files are root > permission even for the log files. Never do

Re: [yocto] [meta-raspberrypi][PATCH 0/1] linux-rpi: clean .config in before do_configure step

On Thu, Dec 15, 2016 at 11:05 AM, Piotr Lewicki wrote: > Previously using bbappend files for linux-raspberrypi recipe did not allow to > use "kernel_configure_variable" function to set kernel config variables. > If user wanted to use it in his bbappend with

Re: [yocto] [meta-raspberrypi] How to set the kernel config variables in the recipe?

On 14.12.2016 21:26, Khem Raj wrote: On Wed, Dec 14, 2016 at 3:14 AM, Piotr Lewicki wrote: Hi, I need to set some kernel parameters and I thought that it would work with "do_configure_prepend()" task in my "linux-raspberrypi_%.bbappend" file. I have do configure like

[yocto] [meta-raspberrypi][PATCH 1/1] linux-rpi: clean .config in before do_configure step

Signed-off-by: Piotr Lewicki --- recipes-kernel/linux/linux-rpi.inc | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/recipes-kernel/linux/linux-rpi.inc b/recipes-kernel/linux/linux-rpi.inc index 95a9530..c665b9f 100644 ---

[yocto] [meta-raspberrypi][PATCH 0/1] linux-rpi: clean .config in before do_configure step

Previously using bbappend files for linux-raspberrypi recipe did not allow to use "kernel_configure_variable" function to set kernel config variables. If user wanted to use it in his bbappend with "do_configure_prepend" it was cleared afterwards. This patch moves cleaning to a separate step. I'm