Hi Trevor
2017-02-17 11:33 GMT+08:00 Trevor Woerner :
> Hi Eddie (and the rest of the Rockchip team),
>
> First let me reiterate how happy I am to see that Rockchip is interested in
> supporting Yocto/OE builds, this is great! I hope this trend continues.
>
> Second, thank you so much for your pat
Hi,
I'm trying to include a third party package in my custom layer.
Unfortunately there is no new release of this third party package.
During the 'configure' stage I get this error:
configure.ac:15: error: possibly undefined macro: AM_PROG_LIBTOOL
I tried changing AM_PROG_LIBTOOL to AC_PROG_LIB
Le 15/02/2017 à 15:57, Patrick Ohly a écrit :
>
> Is that for partial updates with OSTree or something else?
Yes we use OSTree in AGL but the issue is very similar to the one faced
by Ostro.
Thanks to Joshua and Patrick for the pointers.
--
Dominig ar Foll
Senior Software Architect
Intel Open S
Hello, Yocto.
Maybe a basic question but I am being puzzled.
i) Recipe A builds module, and the module expects that xkbcommon.pc is
available (checked in autotool by calling pkg-config)
ii) module A build fails, since it cannot find xkbcommon.pc, according to the
config.log.
(in TEMPDIR/wor
Hi Eddie,
On Fri 2017-02-17 @ 04:56:28 PM, Eddie Cai wrote:
> 2017-02-17 11:33 GMT+08:00 Trevor Woerner :
> > You've put "morty" in the subject lines which to me means you're hoping
> > these
> > patches will be applied against the morty branch of meta-rockchip. Morty was
> > released in October
Current Dev Position: YP 2.3 M3
Next Deadline: YP 2.3 M3 by Feb. 27, 2017
*** FEATURE FREEZE for 2.3 in one week ***
SWAT team rotation: Juro -> Anibal on Feb. 17, 2017.
SWAT team rotation: Anibal -> Todor on Feb. 24, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
K
This set of patches adds to meta-rockchip the ability to create an update
image using the latest GPT-style image for flashing to a firefly-rk3288's
eMMC.
Jacob Chen (2):
u-boot-rockchip: add
rockchip-next-img: add image for rockchip next-dev u-boot
Trevor Woerner (1):
remove DEFAULTTUNEs
The DEFAULTTUNE configuration should not be set at the BSP layer but in a
DISTRO layer (or a user's conf/local.conf). Remove the two DEFAULTTUNEs that
are currently in the layer and add a note in the README to inform users of
this issue and potential settings.
Signed-off-by: Trevor Woerner
---
R
From: Jacob Chen
Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also
be an upstream tracking branch At present, this branch is just a rebased
upstream u-boot.
Reviewed-by: Trevor Woerner
Signed-off-by: Jacob Chen
---
conf/machine/firefly-rk3288.conf | 1 +
From: Jacob Chen
Being different from the previous rk-boot which use parameter, next-dev u-boot
use gpt partition, so it needs to generate a different image.
Reviewed-by: Trevor Woerner
Signed-off-by: Jacob Chen
---
classes/rockchip-next-img.bbclass | 130 +
The yocto-compat-layer script serves as a tool to validate the alignament
of a layer with YP Compatible Layers Programme [1], is based on an RFC
sent to the ML to enable automatic testing of layers [2] that wants to
be YP Compatible.
The tool takes an layer (or set of layers) via command line opti
On 02/13/2017 10:27 AM, Aníbal Limón wrote:
>
>
> On 02/11/2017 08:04 PM, Christopher Larson wrote:
>> On Sat, Feb 11, 2017 at 10:55 AM, Aníbal Limón >> wrote:
>>
>>> During the development of this script based on OEQA framework i found a
>>> bug causing don't display stack traces, i sent a fix
On Fri, Feb 17, 2017 at 2:26 PM, Aníbal Limón
wrote:
> +parser.add_argument('-l', '--layer', metavar='LAYER_DIR',
> +help='Layer to test compatibility with Yocto Project',
> +action='store', required=True)
>
The behavior of this argument is quite unintuitive. First, t
On Fri, Feb 17, 2017 at 3:39 PM, Christopher Larson
wrote:
> On Fri, Feb 17, 2017 at 2:26 PM, Aníbal Limón <
> anibal.li...@linux.intel.com> wrote:
>
>> +parser.add_argument('-l', '--layer', metavar='LAYER_DIR',
>> +help='Layer to test compatibility with Yocto Project',
>> +
On 2017-02-16 12:49, Andreas Müller wrote:
xorg-xserver recommends xf86-input-libinput since oe-core's commit
| commit 2d005faff6341a81a2afae28860101ba9db51ae8
| Author: Jussi Kukkonen
| Date: Wed Oct 26 11:37:38 2016 +0300
|
|conf: Use xf86-input-libinput by default
| ...
As nice side e
On 2017-02-17 03:09, Khem Raj wrote:
On 1/20/17 3:52 AM, Gary Thomas wrote:
On 2017-01-20 12:30, Gary Thomas wrote:
Can someone give me pointers to get the onboard WiFi on the
RaspberryPi3 going? What kernel settings/hoops I need to do,
what packages I might need, etc?
Thanks
Actually, I
16 matches
Mail list logo