On Thu, Jan 19, 2017 at 2:53 PM, Ronald Oakes wrote:
> I need to label a release of my image, including all of the Open Source
> components and the ones I've added in a way that I can both reproduce the
> exact build at any point in the future, and I can give something relitively
> compact to our
It's not a standard module from apache httpd. The original upstream is old
(2005) and on sourceforge. There is a newer upstream, by the same author
apparently, 2 years old at https://github.com/gavincarr/mod_auth_tkt
Why not just "devtool add https://github.com/gavincarr/mod_auth_tkt"; and
see wha
On 01/19/2017 06:06 PM, colin.helliw...@ln-systems.com wrote:
Thanks Chen.
Currently looking into getting networkd hooked in. (no luck yet!)
I’ll also look into moving stuff from local.conf to elsewhere, but
where you say “Distro conf files are not suitable for such kinds of
modification”, I
What's the correct way to use a custom bsp .scc file located in my
custom bsp layer? For purposes of this email let's say it's name is
myplatform-preempt-rt.scc. If I specifically add it to the
yocto-linux-rt_4.4 SRC_URI it appears to get processed twice by scc
according to the meta-series output f
On 2017-01-19 6:20 PM, George McCollister wrote:
What's the correct way to use a custom bsp .scc file located in my
custom bsp layer? For purposes of this email let's say it's name is
myplatform-preempt-rt.scc. If I specifically add it to the
yocto-linux-rt_4.4 SRC_URI it appears to get processed
I need to label a release of my image, including all of the Open Source
components and the ones I've added in a way that I can both reproduce the
exact build at any point in the future, and I can give something relitively
compact to our general configuration manager (who is not used to doing CM
on
unsubscribe
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
This patch adds newlib libraries for cortex-m3, x86, IAMCU and ARC toolchains.
[YOCTO#10662]
Signed-off-by: Juro Bystricky
---
conf/distro/zephyr.conf| 1 +
recipes-core/newlib/newlib/assert-fiprintf.patch | 23 ++
.../newlib/newlib/gettimeofday-header-fix.patch
New class to support commands such as:
$ MACHINE=xxx bitbake yyy -c menuconfig
$ MACHINE=xxx bitbake yyy -c devshell
Kernel options are typically configured via menuconfig.
The file "prj.conf" must be edited manually, hence the need for devshell.
Once in devshell, user can use their favorite edit
MACHINE definition for Zephyr BOARD qemu_x86
Signed-off-by: Juro Bystricky
---
conf/machine/qemu-x86.conf | 11 +++
1 file changed, 11 insertions(+)
create mode 100644 conf/machine/qemu-x86.conf
diff --git a/conf/machine/qemu-x86.conf b/conf/machine/qemu-x86.conf
new file mode 100644
i
Signed-off-by: Juro Bystricky
---
recipes-devtools-arc/gcc/gcc-6.x.arc.inc | 2 --
1 file changed, 2 deletions(-)
diff --git a/recipes-devtools-arc/gcc/gcc-6.x.arc.inc
b/recipes-devtools-arc/gcc/gcc-6.x.arc.inc
index 5453373..adad25a 100644
--- a/recipes-devtools-arc/gcc/gcc-6.x.arc.inc
+++ b/r
This set of patches provides:
1. Support for Zephyr menuconfig and devshell.
These are meant to modify project settings: menuconfig is used to change
kernel configuration, devshell makes it easier to manually edit Zephyr
prj.conf files
2. New MACHINE qemu-x86, corresponding to the zephyr
Signed-off-by: Juro Bystricky
---
conf/machine/qemu-cortex-m3.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/conf/machine/qemu-cortex-m3.conf b/conf/machine/qemu-cortex-m3.conf
index 13f76af..aeb9a69 100644
--- a/conf/machine/qemu-cortex-m3.conf
+++ b/conf/machine/qe
Sure Anibal, see my response inline.
> -Original Message-
> From: Aníbal Limón [mailto:anibal.li...@linux.intel.com]
> Sent: Thursday, January 19, 2017 11:42 AM
> To: Pascal Bach ; yocto@yoctoproject.org;
> Christian Schuler ; Esquivel, Benjamin
>
> Subject: Re: [yocto] [ptest-runner][PAT
Hi Pascal and Christian,
Your patch looks good at first look, only a few comments about the code
inline.
We are trying to standardize the results output format across our
testing components in order to build up-on a Test reporting tool, so let
us review the XML format.
Benjamin do you have a wik
2017-01-19 1:35 GMT+01:00 Terry Farnham :
> Curious if anyone has ever built googles flatbuffers for embedded and
> whether or not they might share their recipe?
>
Hi,
you could try a patch for meta-oe that is added as attachment.
The recipes compile but I had no time to runtest them yet.
--
R
You need to send to Romain Perier(romain.per...@gmail.com, Project
leader of meta-rockchip), Trevor Woerner (twoer...@gmail.com,
Maintainer of meta-rockchip)
2017-01-19 22:04 GMT+08:00 Jacob Chen :
> This series of patches add below features, will add more supports in the
> future(medias, more ch
From: Monserrat Sedeno
The new nightly-oe-build-perf-test buildset executes the
build-perf-test-wrapper.sh into a worker and publish the results to
specified folder by AB config.
When the performance script finish it sends an notifcation email to
yocto alias users, the worker machine needs to co
Sometimes is a good idea to could specify a machine to build via a build
property/web interface input.
Without this patch if you specify the machine via a build property/web
interface input, the machine is overwrite taking only into account the
default machine set in the buildset.
Signed-off-by:
Hi
2017-01-19 18:09 GMT+08:00 Jacob Chen :
> This is the kernel vendor that supports all hw components for this board,
> so we use it by default.
The title and commit message didn't match the your content. Linux
rockchip should refer to http://github.com/linux-rockchip.
firefly-rk3288.conf already
Hi,
The problem with 4.8 is that because of the constant rebasing in the
downstream, it will get broken fast.
So someone will have to maintain it and constantly update it, and if we don't
do it for master, it's unlikely to be done on Morty.
At some point, 4.8 will stop changing, but we're not th
Hi Jacob,
On Thu, Jan 19, 2017 at 11:09 AM, Jacob Chen wrote:
> This series of patches add below features, will add more supports in the
> future(medias, more chips).
> 1
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel, will be an upstream tracking branch.
Sorry for sending without prefix, and make you guys confused.
This series patches is sending for meta-rockchip, not core meta data.
I'm new to here, and I just fllow readme in meta-rockchip to send patches.
-- Original --
From: "Bruce Ashfield";;
Date: Thu, Jan 1
Thanks for reminding, I've already added them.
But it seems I forgot to add the prefix "meta-rockchip"
-- Original --
From: "Burton, Ross";;
Date: Thu, Jan 19, 2017 07:30 PM
To: "Jacob Chen";
Cc: "yocto@yoctoproject.org";
"eddie.cai";
"romain.perier"; "Tr
Sorry for bothring : ).
2017-01-19 21:55 GMT+08:00 Jacob Chen :
> Sorry for sending without prefix, and make you guys confused.
> This series patches is sending for meta-rockchip, not core meta data.
>
> I will resend it and add prefix.
>
> 2017-01-19 20:49 GMT+08:00 Gary Thomas :
>> On 2017-0
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.
Signed-off-by: Jacob Chen
---
classes/rockchip-next-image.bbclass | 130
1 file changed, 130 insertions(+)
create m
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.
Signed-off-by: Jacob Chen
---
recipes-bsp/u-boot/u-boot-rockchip_next.bb | 17 +
1 file changed, 17 insertions
change tune to cortexa17hf-neon:
Using the soft floating point abi is incompatible with some binary libaries.
Set preferred mali version to t76x.
Add APPEND which will be used in extlinux.conf.
Add SOC_FAMILY to help add chip specific changes.
Add SPL_BINARY to support build u-boot spl
Signed-
Add support for mali userspace which are binaries that can be run
with weston and X11.
Signed-off-by: Jacob Chen
---
recipes-graphics/mali-userspace/mali-userspace.inc | 57 ++
.../mali-userspace/mali-userspace_t76x.bb | 18 +++
recipes-graphics/mesa/mesa_%.bbapp
This is the kernel vendor that supports all hw components for this board,
so we use it by default.
Signed-off-by: Jacob Chen
---
conf/machine/firefly-rk3288.conf | 4
1 file changed, 4 insertions(+)
diff --git a/conf/machine/firefly-rk3288.conf b/conf/machine/firefly-rk3288.conf
index 8fa0
Evb-rk3288 is the offical evaluate board, add it to help myself develop.
Fennec-rk3288 and Tinker-rk3288 is rk3288 based SBCs.
.
Tinker Boards:
http://www.cnx-software.com/2017/01/05/asus-tinker-board-is-a-raspberry-pi-3-alternative-based-on-rockchip-rk3288-processor/
Signed-off-by: Jacob Che
Rockchip 4.4 kernel is currently the latest version of the rockchip offical
kernel,
will be an upstream tracking branch.
We regularly release the kernel through github.
It support all rockchip 64-bit chips and a few 32-bit chips.
Signed-off-by: Jacob Chen
---
recipes-kernel/linux/linux-rockchip
This series of patches add below features, will add more supports in the
future(medias, more chips).
1. rockchip 4.4 kernel
Rockchip 4.4 kernel is currently the latest version of the rockchip offical
kernel, will be an upstream tracking branch.
We regularly release the kernel through github. It
Sorry for sending without prefix, and make you guys confused.
This series patches is sending for meta-rockchip, not core meta data.
I will resend it and add prefix.
2017-01-19 20:49 GMT+08:00 Gary Thomas :
> On 2017-01-19 12:30, Burton, Ross wrote:
>>
>> (CCing the layer maintainers as listed in
From: Christian Schuler
add a feature that allows the user to generate an XUnit xml-file.
This file shows if the ptests run correctly or not. e.g. bash, zlib.
It doesn't list the underlaying tests of the package.
The feature is activated by console input -x .
Unit-tests of the feature are include
On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen wrote:
> This series of patches add below features, will add more supports in the
> future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel, will be an upstream trac
Supports different EGLFS_DEVICE_INTEGRATION for userland or vc4
Signed-off-by: Herve Jourdain
---
recipes-qt/qt5/qtbase_%.bbappend | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 recipes-qt/qt5/qtbase_%.bbappend
diff --git a/recipes-qt/qt5/qtbase_%.bbappend b/recipes-qt/qt
On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen wrote:
> Rockchip 4.4 kernel is currently the latest version of the rockchip
> offical kernel,
> will be an upstream tracking branch.
> We regularly release the kernel through github.
> It support all rockchip 64-bit chips and a few 32-bit chips.
>
If
On Thu, Jan 19, 2017 at 12:41 PM, Paul Barker wrote:
> On 19 January 2017 12:07:11 GMT+00:00, Andrei Gherzan
> wrote:
>>On Thu, Jan 19, 2017 at 12:03 PM, Paul Barker
>>wrote:
>>> On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan
>> wrote:
From: Paul Barker
Signed-off-by: Paul
On 2017-01-19 12:30, Burton, Ross wrote:
(CCing the layer maintainers as listed in the README to ensure this gets
noticed)
Shouldn't this have [meta-rockchip] (or some such) in the subject? - it's
certainly
not OE-core or even Poky AFAICT
On 19 January 2017 at 10:09, Jacob Chen mailto:jac
When building weston with userland, there is an error at configuration time:
| checking for DRM_COMPOSITOR... no
| configure: error: Package requirements (libudev >= 136 libdrm >= 2.4.30 gbm
mtdev >= 1.1.0) were not met:
|
| No package 'gbm' found
This is due to kms being enabled by default in th
On 19 January 2017 12:07:11 GMT+00:00, Andrei Gherzan wrote:
>On Thu, Jan 19, 2017 at 12:03 PM, Paul Barker
>wrote:
>> On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan
> wrote:
>>>From: Paul Barker
>>>
>>>Signed-off-by: Paul Barker
>>>---
>>> recipes-kernel/linux/linux-raspberrypi_4.8.bb |
On Thu, Jan 19, 2017 at 12:03 PM, Paul Barker wrote:
> On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan
> wrote:
>>From: Paul Barker
>>
>>Signed-off-by: Paul Barker
>>---
>> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8
>> 1 file changed, 8 deletions(-)
>> delete mode 100644
On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan wrote:
>From: Paul Barker
>
>Signed-off-by: Paul Barker
>---
> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8
> 1 file changed, 8 deletions(-)
> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
>
>diff --git a/reci
i was looking for this a while ago with no luck ... still
interested ... am i just being clueless in not seeing where to get it?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
Signed-off-by: Andrei Gherzan
---
recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
index 20f43aa..cffea1a 100644
--- a/recipes-kernel
Signed-off-by: Andrei Gherzan
---
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 3317c02..0f78225 100644
--- a/recipes-kernel
From: Paul Barker
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8
1 file changed, 8 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
b/recipes-kernel/linux/linux
From: Paul Barker
Signed-off-by: Paul Barker
---
.../0001-fix-dtbo-rules.patch | 44 --
recipes-kernel/linux/linux-raspberrypi_4.7.bb | 9 -
2 files changed, 53 deletions(-)
delete mode 100644
recipes-kernel/linux/linux-raspberrypi-4.7/0001-f
From: Paul Barker
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 35a72d7..3317c02 100644
---
From: Paul Barker
The linux-raspberrypi 4.1 recipe has been broken for a while, probably since
09b76a43f6f6852406de385a45f472c52b6a8571. It should now be safe to drop this
version.
Signed-off-by: Paul Barker
---
.../0001-dts-add-overlay-for-pitft22.patch | 110 -
..
Hi Rick,
Patches for oe-core should go to the
openembedded-c...@lists.openembedded.org mailing list, yocto@ is for user
support and smaller layers that don't need their own list. Can you resend
it?
On 19 January 2017 at 01:52, Rick Altherr wrote:
> Change-Id: I0717c2ab04d13e58c2b91a829063c2d0f
(CCing the layer maintainers as listed in the README to ensure this gets
noticed)
On 19 January 2017 at 10:09, Jacob Chen wrote:
> This series of patches add below features, will add more supports in the
> future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is curren
On Wed, 2017-01-18 at 18:13 +, Joshua Lock wrote:
> On Mon, 2017-01-16 at 10:25 -0600, Aníbal Limón wrote:
> >
> > Sometimes is a good idea to could specify a machine to build via a
> > build
> > property.
> Why's that? I can guess but the commit log should really tell me what
> the motivation
2017-01-19 18:09 GMT+08:00 Jacob Chen :
> This series of patches add below features, will add more supports in the
> future(medias, more chips).
>
> 1. rockchip 4.4 kernel
>
> Rockchip 4.4 kernel is currently the latest version of the rockchip offical
> kernel, will be an upstream tracking branch
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.
Signed-off-by: Jacob Chen
---
classes/rockchip-next-image.bbclass | 130
1 file changed, 130 insertions(+)
create m
change tune to cortexa17hf-neon:
Using the soft floating point abi is incompatible with some binary libaries.
Set preferred mali version to t76x.
Add APPEND which will be used in extlinux.conf.
Add SOC_FAMILY to help add chip specific changes.
Add SPL_BINARY to support build u-boot spl
Signed-
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.
Signed-off-by: Jacob Chen
---
recipes-bsp/u-boot/u-boot-rockchip_next.bb | 17 +
1 file changed, 17 insertions
Add support for mali userspace which are binaries that can be run
with weston and X11.
Signed-off-by: Jacob Chen
---
recipes-graphics/mali-userspace/mali-userspace.inc | 57 ++
.../mali-userspace/mali-userspace_t76x.bb | 18 +++
recipes-graphics/mesa/mesa_%.bbapp
This is the kernel vendor that supports all hw components for this board,
so we use it by default.
Signed-off-by: Jacob Chen
---
conf/machine/firefly-rk3288.conf | 4
1 file changed, 4 insertions(+)
diff --git a/conf/machine/firefly-rk3288.conf b/conf/machine/firefly-rk3288.conf
index 8fa0
Evb-rk3288 is the offical evaluate board, add it to help myself develop.
Fennec-rk3288 and Tinker-rk3288 is rk3288 based SBCs.
.
Tinker Boards:
http://www.cnx-software.com/2017/01/05/asus-tinker-board-is-a-raspberry-pi-3-alternative-based-on-rockchip-rk3288-processor/
Signed-off-by: Jacob Che
Rockchip 4.4 kernel is currently the latest version of the rockchip offical
kernel,
will be an upstream tracking branch.
We regularly release the kernel through github.
It support all rockchip 64-bit chips and a few 32-bit chips.
Signed-off-by: Jacob Chen
---
recipes-kernel/linux/linux-rockchip
This series of patches add below features, will add more supports in the
future(medias, more chips).
1. rockchip 4.4 kernel
Rockchip 4.4 kernel is currently the latest version of the rockchip offical
kernel, will be an upstream tracking branch.
We regularly release the kernel through github. I
Thanks Chen.
Currently looking into getting networkd hooked in. (no luck yet!)
I'll also look into moving stuff from local.conf to elsewhere, but where you
say "Distro conf files are not suitable for such kinds of modification", I'm
wondering what sort of modifications they *are* suitable/intende
On 18-01-17 16:10, colin.helliw...@ln-systems.com wrote:
We have a configuration for our embedded system which is working via SysV, but
we’re investigating moving over to systemd.
Not sure if this is ‘wise’ – if anyone has technological arguments for/against
then I’d be interested – but I wante
On Tue, 17 Jan 2017 20:54:14 Joshua Watt wrote:
> > external SDK:
> > everything the same as above, but for some packages there should be
> > only libraries - no header files.
>
> Is there a reason why you want the libraries without the headers? It
> doesn't seem particularly useful to be able to
Hi Colin,
For the dhcp problem, what you need is a network manager. Any network
manager that supports dhcp would do the job. systemd-networkd might be
sufficient in your case.
For the local.conf problem, you could use a layer to manage all common
things shared by the team.
For the package
Yes, I’d agree with that, Rick.
We run automated regression builds from a fresh version control checkout – but
because local.conf is generated when the build environment is set up, it isn’t
suitable for version control. So any mods to it found during development have
to be (remembered to be) pu
On 18/01/17 16:10, colin.helliw...@ln-systems.com wrote:
> We have a configuration for our embedded system which is working via
> SysV, but we’re investigating moving over to systemd.
>
> Not sure if this is ‘wise’ – if anyone has technological arguments
> for/against then I’d be interested – but
69 matches
Mail list logo
