> On Jul 22, 2016, at 6:16 AM, Martin Bergek wrote:
>
> Paul,
>
> I am having stability issues with the USB subsystem on Raspberry Pi 3 under
> 4.4 that I can’t reproduce under 4.1. I assume 4.1 will still remain in the
> recipe when 4.4 is made the default option. How long would the 4.1 vers
> On Jul 20, 2016, at 3:00 PM, Herve Jourdain wrote:
>
> v6: rebased
>
> v5: modifications after more review
> * Added an Upstream-Status to the kernel patch
> * Only one instance of KERNEL_DEVICETREE defined (with the new .dtbo syntax)
> * Modification of the KERNEL_DEVICETREE is done in
> li
> On Jul 22, 2016, at 9:41 AM, Carlos Alberto Lopez Perez
> wrote:
>
> On 21/07/16 14:32, Herve Jourdain wrote:
>> v4 series:
>> a. rebased
>> b. Upstream-Status added to the patch to the VC4 driver (needed only for
>> kernel 4.4, accepted upstream in 4.7)
>>
>> v3 series:
>> a. patch rebased
> On Jul 21, 2016, at 5:32 AM, Herve Jourdain wrote:
>
> v4 series:
> a. rebased
> b. Upstream-Status added to the patch to the VC4 driver (needed only for
> kernel 4.4, accepted upstream in 4.7)
>
> v3 series:
> a. patch rebased
> b. new revision of kernel, to get a version of the VC4 graphic
Please post this patch against OE-Core
> On Jul 20, 2016, at 11:10 AM, Herve Jourdain wrote:
>
> Signed-off-by: Herve Jourdain
> ---
> .../0001-gl-implement-GstGlMemoryEGL.patch | 494 +
> .../gstreamer1.0-plugins-bad_1.8.2.bbappend| 6 +
> 2 files changed, 5
On krogoth branch of poky trying to create a multilib sdk (aarch64
aarch64_ilp32)
Using the below local.conf
CONF_VERSION = "1"
MACHINE = "TestMachine"
CORE_IMAGE_EXTRA_INSTALL_append += " openssl"
PREFERRED_VERSION_linux-thunderx-81xx = "4.4.3"
BB_NUMBER_THREADS="32"
PREFERRED_PROVIDER_virtual
Hello Ross,
I am using my own kernel [3.18] + oe-core's perf recipe to build the perf
utility. Thanks.
Cheers
Vijay
On Thu, Jul 28, 2016 at 2:17 AM, Burton, Ross wrote:
>
> On 27 July 2016 at 22:53, Vijayakumar Badiger
> wrote:
>
>> We have a requirement here to set up the perf tool through
Here is the final QA Report for Yocto Project 2.2 M2 rc1
https://wiki.yoctoproject.org/wiki/WW30_-_2016-07-21_-_Full_Test_Cycle_2.2_M2.rc1
Summary
There are a total of 40 bugs reported in this test cycle, 19 new and 21 that
were raised in previous Milestones/Releases and appeared also in M2. No
python-native should not assume that prefix points to the native
sysroot, and instead use STAGING_LIBDIR to determine prefix, since
python-native may be used to compile non-native python modules for the
target sysroot.
Computing an incorrect prefix causes unintended build behavior,
especially on s
On 2016-07-28 12:00 AM, Zhenhua Luo wrote:
Hi,
I want to understand the kernel version selection criteria of Yocto
release, can somebody please help to comment on it? I recall that Yocto
uses the LTSI kernel, may I know if this is still the case?
I was about to describe the process .. but the
On 27 July 2016 at 22:53, Vijayakumar Badiger
wrote:
> We have a requirement here to set up the perf tool through our Yocto frame
> work.
> As Perf source comes with linux kernel under tools/perf ,so I added this
> perf tool to be installed
> as part of my rootfs image.
>
> But when I build the i
Hi Oliver,
The following line in shadow-sysroot.bb disables the final binary packages
generation. You can try to add bbappend for shadow to do the customization.
# don't create any packages
# otherwise: dbus-dev depends on shadow-sysroot-dev which depends on
shadow-sysroot
# and this has anot
Hello list,
i'm trying to replace /etc/login.defs on the target with my own one. So
I created a shadow-sysroot_%.bbappend file with this content:
FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
# As we're overriding login.defs_shadow-sysroot we have to readd the checksum
for it here
# as it's c
13 matches
Mail list logo
