Hi everyone
We have a new Intel Atom E3800 (Bay Trail) based board with 2 x HDMI ports.
We are using the edk2 firmware (used the minnowBoard MAX firmware source as
basis) but we can't seem to get the HDMI-2 port to be recognized by either
the firmware or our linux kernel (built with latest yocto
Well, I'm using Poky as a distribution, at least for my tests...
But there might be a reason why it's not included there, I believe.
The problem to include it at the distribution level is you need to make
assumptions as to what kind of network/network interfaces will be found.
On a raspberrypi,
On 23 July 2015 at 23:50, Herve Jourdain herve.jourd...@neuf.fr wrote:
This said, I - maybe wrongfully - assumed that anyone including the
meta-raspberrypi layer would actually want to run on a raspberrypi, which
does have an Ethernet interface I believe on all machines - I only have a
Qt3 is incredibly old and not required by LSB 5, so now is time to remove it
from the autobuilder.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
buildset-config.controller/minnow-lsb.conf | 5 +
buildset-config.controller/nightly-arm-lsb.conf | 5 +
Hi Ross,
Yes, this is exactly what I assumed – I know, too many assumptions…
The point is that many people are turning to Poky for generating their first
Yocto-based distribution for RaspberryPi. And out of the box, if using system,
the network part doesn’t work.
That’s why I was trying to
Hi Ross,
OK, I get it. I will be more careful in correctly restricting patches to the
machine targeted, if there are machine dependencies.
BR,
Herve
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: vendredi 24 juillet 2015 00:54
To: Herve Jourdain
Cc: Andreas Müller; Yocto
Many buildsets pull in meta-qt3 but don't use it, so remove the layer from those
buildsets.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
buildset-config.controller/minnow.conf | 3 ---
buildset-config.controller/nightly-arm.conf | 3 ---
Hi Gary,
Thanks for the help.
I executed the command
bitbake userland -c cleansstate
This completed successful.
5: userland-git-r5 do_compile (pid 17332)
Did not know how to apply the patch.
I tried in poky folder
patch --dry-run ~/Downloads/attachment-0001.bin
patch
On 2015-07-23 03:54, Burton, Ross wrote:
On 23 July 2015 at 01:23, Gary Thomas g...@mlbassoc.com
mailto:g...@mlbassoc.com wrote:
You must have added something to your image - core-image-sato does
not include libepoxy by default.
Well actually, if your using oe-core master and
On 15-07-23 09:31 AM, Gorny Krystian wrote:
So my drv_iointerrupt.c is a standard *.ko driver. It's still missing the
include files asm/atomic.h and linux/cdev.h when I try to build it ($bitbake
iointerrupt).
Can I compile and install the driver module to the kernel with normal *.bb
files
Am 21.07.2015 um 18:01 schrieb Matt Schuckmann:
If you are using systemd you can simply create a separate writeable partition
and then use the volatile_binds.bb recipe to map files or directories from the
read only rootfs to the writable partition via bind mounts.
How should one use the
---
.../kernel-cache/bsp/axxiapowerpc/axxiapowerpc.cfg |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/cfg/kernel-cache/bsp/axxiapowerpc/axxiapowerpc.cfg
b/meta/cfg/kernel-cache/bsp/axxiapowerpc/axxiapowerpc.cfg
index 689f887..ae23320 100644
---
On 23 July 2015 at 23:45, Herve Jourdain herve.jourd...@neuf.fr wrote:
But there might be a reason why it's not included there, I believe.
Because Poky is a reference distribution, primarily for QA, that doesn't
explicitly support the Raspberry Pi and certainly doesn't expect to be used
Indeed, it's a valid point, and I should probably be more cautious in the
naming of the bbappend.
This said, I - maybe wrongfully - assumed that anyone including the
meta-raspberrypi layer would actually want to run on a raspberrypi, which does
have an Ethernet interface I believe on all
On Wed, Jul 22, 2015 at 8:50 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Tuesday 21 July 2015 14:51:55 Victor Rodriguez wrote:
On Tue, Jul 21, 2015 at 12:41 PM, Leonardo Sandoval
leonardo.sandoval.gonza...@linux.intel.com wrote:
On 07/21/2015 10:45 AM, Victor Rodriguez wrote:
Hi,
Not sure if it’s the case, because the config.log might give more details, but
maybe you can try adding the following to your recipe :
EXTRA_OECONF += “-I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \
I figured this out in the end.
By default it looks like Fido, and at least the releases from Dizzy on
build Berkeley db version 6. Python 2.7 needs db version 5 in order to
build all of the components for python-bsddb. If you build using db
version 6, there aren't any warning messages that get
Hi,
Not sure if it’s the case, because the config.log might give more details, but
maybe you can try adding the following to your recipe :
EXTRA_OECONF += “-I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \
On 2015-07-23 08:37, Edward Vidal wrote:
Hi Gary,
Is this the log that you need?
I also ran the bitbake -DD core-image-sato and have the log for that run.
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runconf failed
| ERROR: Function failed: do_configure (log file is located at
I've merged this, and the meta changes to the 3.14 tree.
I won't be doing any SRCREV updates for the BSPs or META
right now, since the format has changed in master.
You can carry SRCREV changes (or use AUTOREV) in your
layers, and everything will be in place.
Cheers,
Bruce
On 15-07-21 05:40
Hi Gary,Is this the log that you need?I also ran the bitbake -DD
core-image-sato and have the log for that run.
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runconf failed
| ERROR: Function failed: do_configure (log file is located at
On 2015-07-23 09:53, Edward Vidal wrote:
i Gary,
I added to my the 2 lines mentioned in the e-mail to my conf/local.conf
PREFERRED_PROVIDER_virtual/egl ?= vc-graphics-hardfp
PREFERRED_PROVIDER_virtual/libgles2 ?= vc-graphics-hardfp
I had saved the original local.conf in ~/wkg/yocto/local.conf
On 2015-07-23 09:01, Herve Jourdain wrote:
Hi,
Not sure if it’s the case, because the config.log might give more details, but
maybe you can try adding the following to your recipe :
EXTRA_OECONF += “-I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \
This patch adds systemd-networkd for RaspberryPi in the meta-raspberrypi
layer, in order to have Ethernet and Networking work out of the box.
This said, Im not 100% sure if it should be enabled in meta-raspberrypi,
instead of another custom layer.
But something similar needs to be added
Hi Gary,
What worries me is I don't see that kind of paths in the log file that
Edward sent.
And I'm just thinking the package configuration itself might need to know
the where to find those headers - I believe I needed something similar for
QT.
This said, it's very difficult to know for sure
Em Thu, 23 Jul 2015 17:32:35 +0200
Herve Jourdain herve.jourd...@neuf.fr escreveu:
This patch adds systemd-networkd for RaspberryPi in the meta-raspberrypi
layer, in order to have Ethernet and Networking work out of the box.
This said, I’m not 100% sure if it should be enabled in
i Gary,
I added to my the 2 lines mentioned in the e-mail to my conf/local.conf
PREFERRED_PROVIDER_virtual/egl ?= vc-graphics-hardfp
PREFERRED_PROVIDER_virtual/libgles2 ?= vc-graphics-hardfp
I had saved the original local.conf in ~/wkg/yocto/local.conf before making any
changes.
diff -u
Hi Mauro,
Well, that's precisely one of my concerns. I believe that one of the Tizen
layers might do just that. Maybe it should be at the Yocto layer.
But it seems not to be with the one I'm using. And just enabling system - which
can be done at distro level - is not enough, there is a need for
On Thu, Jul 23, 2015 at 5:32 PM, Herve Jourdain herve.jourd...@neuf.fr wrote:
This patch adds systemd-networkd for RaspberryPi in the meta-raspberrypi
layer, in order to have Ethernet and Networking work out of the box.
This said, I’m not 100% sure if it should be enabled in
On 2015-07-23 06:35, Edward Vidal wrote:
bitbake core-image-sato failed with same error.
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runconf failed
| ERROR: Function failed: do_configure (log file is located at
Em Thu, 23 Jul 2015 18:25:29 +0200
Herve Jourdain herve.jourd...@neuf.fr escreveu:
Hi Mauro,
Well, that's precisely one of my concerns. I believe that one of the Tizen
layers might do just that.
Yes, it does. It is at the meta-tizen layer.
Maybe it should be at the Yocto layer.
But it
I didn’t find “rm_work” in any of my conf files so I don’t think that’s the
issue.
It appears that STAGING_KERNEL_DIR just doesn’t get rebuilt from sstate which I
can understand since it isn’t needed by default. I found a way to set up the
dependencies to build it when needed and I started a
Hi Mei,
On 07/15/2015 10:40 AM, Ng, Mei Yeen wrote:
Hi,
I need help for issue where packages in packagegroup that compiles perfectly
fine with core-images, but when verified in the image, they are not installed
for some reason.
My understanding was that packages listed under RDEPENDS in the
On 07/23/2015 10:59 AM, Randy Witt wrote:
Hi Mei,
On 07/15/2015 10:40 AM, Ng, Mei Yeen wrote:
Hi,
I need help for issue where packages in packagegroup that compiles perfectly
fine with core-images, but when verified in the image, they are not installed
for some reason.
My understanding was
Hi allCan anyone please tell how to interface raspberrypi with pitft 2.8
resistive screen. notro tft driver is available in stagging mode but how to use
that to make display functional, is not clear.Have any one succeeded in running
pitft with yocto ?
please help to make pitft display
On Thu, Jul 23, 2015 at 12:05 PM, Victor Rodriguez vm.ro...@gmail.com wrote:
On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador
otavio.salva...@ossystems.com.br wrote:
On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com
wrote:
Few weeks ago I was having some problems with
On Wed, Jul 22, 2015 at 7:35 AM, Otavio Salvador
otavio.salva...@ossystems.com.br wrote:
On Tue, Jul 21, 2015 at 11:57 AM, Victor Rodriguez vm.ro...@gmail.com wrote:
Few weeks ago I was having some problems with open CV receipt. In the
begining I toght I was adding opencv tro my
On 23 July 2015 at 01:23, Gary Thomas g...@mlbassoc.com wrote:
You must have added something to your image - core-image-sato does
not include libepoxy by default.
Well actually, if your using oe-core master and DISTRO_FEATURES includes
wayland then xserver-xorg will build the xwayland server,
38 matches
Mail list logo
