[yocto] [meta-raspberrypi][PATCH 1/2] linux-raspberrypi_4.9.bb: Upgrade to 4.9.5

2017-01-26 Thread Khem Raj 
Signed-off-by: Khem Raj 
---
 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 cffea1a..1f8fe11 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.9.4"
+LINUX_VERSION ?= "4.9.5"
 
-SRCREV = "8b0be887f834e7eccf0de3edf630003880779a5f"
+SRCREV = "fd03479116aebe4a9faf64e108b3ab7eeb8cb71a"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
 "
 require linux-raspberrypi.inc
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 2/2] userland: Upgrade to latest and implement triple buffering for wayland

2017-01-26 Thread Khem Raj 
Signed-off-by: Khem Raj 
---
 ...13-Implement-triple-buffering-for-wayland.patch | 85 ++
 recipes-graphics/userland/userland_git.bb  |  3 +-
 2 files changed, 87 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-graphics/userland/userland/0013-Implement-triple-buffering-for-wayland.patch

diff --git 
a/recipes-graphics/userland/userland/0013-Implement-triple-buffering-for-wayland.patch
 
b/recipes-graphics/userland/userland/0013-Implement-triple-buffering-for-wayland.patch
new file mode 100644
index 000..8703296
--- /dev/null
+++ 
b/recipes-graphics/userland/userland/0013-Implement-triple-buffering-for-wayland.patch
@@ -0,0 +1,85 @@
+From 81f421b051c726bbe180ee5f7d93cf13a3935904 Mon Sep 17 00:00:00 2001
+From: Jeff Wannamaker 
+Date: Thu, 19 Jan 2017 18:56:07 +
+Subject: [PATCH 13/13] Implement triple buffering for wayland
+
+Change from double to triple buffering for wayland.  This enables higher frame 
rates without tearing artifacts by allowing both the glFinish and the buffer 
release interlock to operate without pushing the frame period to two vertical 
intervals
+
+Signed-off-by: Jeff Wannamaker 
+---
+ interface/khronos/egl/egl_client.c |  3 ++-
+ interface/khronos/egl/egl_client_surface.c |  8 
+ interface/khronos/egl/egl_client_surface.h | 11 +++
+ 3 files changed, 21 insertions(+), 1 deletion(-)
+
+diff --git a/interface/khronos/egl/egl_client.c 
b/interface/khronos/egl/egl_client.c
+index 13a110c..0380274 100644
+--- a/interface/khronos/egl/egl_client.c
 b/interface/khronos/egl/egl_client.c
+@@ -2323,7 +2323,8 @@ EGLAPI EGLBoolean EGLAPIENTRY eglSwapBuffers(EGLDisplay 
dpy, EGLSurface surf)
+ 
+   buffer_temp = surface->front_wl_buffer;
+   surface->front_wl_buffer = surface->back_wl_buffer;
+-  surface->back_wl_buffer = buffer_temp;
++  surface->back_wl_buffer = surface->middle_wl_buffer;
++  surface->middle_wl_buffer = buffer_temp;
+ 
+   configid = egl_config_to_id(surface->config);
+   color = egl_config_get_color_format(configid);
+diff --git a/interface/khronos/egl/egl_client_surface.c 
b/interface/khronos/egl/egl_client_surface.c
+index 9a9582c..10b3b04 100644
+--- a/interface/khronos/egl/egl_client_surface.c
 b/interface/khronos/egl/egl_client_surface.c
+@@ -402,12 +402,14 @@ EGL_SURFACE_T *egl_surface_create(
+if (type == WINDOW && wl_display) {
+   surface->wl_egl_window = (struct wl_egl_window*)win;
+   surface->front_wl_buffer = NULL;
++  surface->middle_wl_buffer = NULL;
+   surface->back_wl_buffer = allocate_wl_buffer(
+ surface->wl_egl_window, color);
+   resource = surface->back_wl_buffer->resource;
+} else {
+   surface->wl_egl_window = NULL;
+   surface->front_wl_buffer = NULL;
++  surface->middle_wl_buffer = NULL;
+   surface->back_wl_buffer = NULL;
+   resource = DISPMANX_NO_HANDLE;
+}
+@@ -696,6 +698,12 @@ void egl_surface_free(EGL_SURFACE_T *surface)
+  surface->back_wl_buffer = 0;
+   }
+ 
++  if (surface->middle_wl_buffer) {
++ wl_buffer_destroy(surface->middle_wl_buffer->wl_buffer);
++ free(surface->middle_wl_buffer);
++ surface->middle_wl_buffer = 0;
++  }
++
+   if (surface->front_wl_buffer) {
+  wl_buffer_destroy(surface->front_wl_buffer->wl_buffer);
+  free(surface->front_wl_buffer);
+diff --git a/interface/khronos/egl/egl_client_surface.h 
b/interface/khronos/egl/egl_client_surface.h
+index e328b77..58a3184 100644
+--- a/interface/khronos/egl/egl_client_surface.h
 b/interface/khronos/egl/egl_client_surface.h
+@@ -313,6 +313,17 @@ typedef struct {
+struct wl_dispmanx_client_buffer *front_wl_buffer;
+ 
+/*
++  middle_wl_buffer
++
++  Validity:
++  type == WINDOW
++
++  Invariant:
++  client-side information about the wl_buffer in the middle
++   */
++   struct wl_dispmanx_client_buffer *middle_wl_buffer;
++
++   /*
+   back_wl_buffer
+ 
+   Validity:
+-- 
+2.7.1
+
diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index a37249c..cec591d 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -16,7 +16,7 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 SRCBRANCH = "master"
 SRCFORK = "raspberrypi"
-SRCREV = "bb15afe33b313fe045d52277a78653d288e04f67"
+SRCREV = "0f015eaa17add5bca00ecf8a354ea62e19bd7920"
 
 SRC_URI = "\
 git://github.com/${SRCFORK}/userland.git;protocol=git;branch=${SRCBRANCH} \
@@ -32,6 +32,7 @@ SRC_URI = "\
 file://0010-Fix-for-framerate-with-nested-composition.patch \
 file://0011-build-shared-library-for-vchostif.patch \
 file://0012-implement-buffer-wrapping-interface-for-dispmanx.patch \
+

Re: [yocto] QEMU with host USB serial

2017-01-26 Thread colin.helliwell 
Hi,
That gives:

Continuing with the following parameters:
KERNEL:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/bzImage-qemux86-64.bin]
ROOTFS:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4]
FSTYPE: [ext4]
Setting up tap interface under sudo
[sudo] password for colin:
Acquiring lockfile for tap0...
Interrupt character is '^]'
-net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no
-cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware   -nographic
-serial stdio  -m 256
Running qemu-system-x86_64...
/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/sysroots/x86_64-linux/u
sr/bin/qemu-system-x86_64 -kernel
/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-6
4/bzImage-qemux86-64.bin -net nic,model=virtio -net
tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot
-nographic -serial stdio -m 256 -serial null --append "vga=0
uvesafb.mode_option=640x480-32 root=/dev/vda rw mem=256M
ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 rootfstype=ext4
console=ttyS0 console=ttyS0"
QEMU 2.4.0 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: -serial stdio: cannot use stdio by multiple
character devices
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'


-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Khem Raj
Sent: 27 January 2017 02:10
To: yocto@yoctoproject.org
Subject: Re: [yocto] QEMU with host USB serial

On 1/26/17 6:22 AM, colin.helliw...@ln-systems.com wrote:
> I'm investigating using qemu to give us some test capability, for 
> which we need to use the host's serial devices.
> 
> I have a qemu build which boots up fine; I'm trying to give it access 
> to the host USB. To keep it simple(r), I've seen mention of FTDI's 
> device
> (0403:6001) in the qemu source so that's what I've plugged in. I've 
> done a 'chmod me:me' on the relevant /dev/bus/usb/xxx/yyy node.
> 
>  
> 
> I can't though figure out what options I should be passing to runqemu 
> to hook this in. I daresay I may need bootparams too, but am first 
> just trying to get past 'qemuparams'.
> 
> As a starting point, I'm trying things like
> 
> runqemu qemux86-64 nographic qemuparams="-usbdevice serial"

can you try with

runqemu qemux86-64 nographic serial

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QEMU with host USB serial

2017-01-26 Thread Khem Raj 


On 1/26/17 6:22 AM, colin.helliw...@ln-systems.com wrote:
> I’m investigating using qemu to give us some test capability, for which
> we need to use the host’s serial devices.
> 
> I have a qemu build which boots up fine; I’m trying to give it access to
> the host USB. To keep it simple(r), I’ve seen mention of FTDI’s device
> (0403:6001) in the qemu source so that’s what I’ve plugged in. I’ve done
> a ‘chmod me:me’ on the relevant /dev/bus/usb/xxx/yyy node.
> 
>  
> 
> I can’t though figure out what options I should be passing to runqemu to
> hook this in. I daresay I may need bootparams too, but am first just
> trying to get past ‘qemuparams’.
> 
> As a starting point, I’m trying things like
> 
> runqemu qemux86-64 nographic qemuparams="-usbdevice serial"

can you try with

runqemu qemux86-64 nographic serial

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Exception in bitbake during build of openjdk-8 using meta-linaro

2017-01-26 Thread Khem Raj 


On 1/26/17 5:54 AM, SMITH Peter T wrote:
> Hi, I am trying to build openjdk-8 from the meta-linaro layer (I’m
> specifically interested in building for aarch64), everything proceeds
> well with gathering and building the dependencies until poky/bitbake
> attempts to fetch sources using hg when I see the error below. Anyone
> seen this before or can offer a pointer to what might be wrong?
> 
>  

if you could nail it down the particular recipe which is using hg
fetcher then it would be easy to proceed further. Secondly, also include
your build configuration that bitbake spits at very beginning of build,
that also helps.

> 
>  
> 
> DEBUG: Executing python function do_fetch
> 
> DEBUG: Executing python function base_do_fetch
> 
> ERROR: Error executing a python function in exec_python_func()
> autogenerated:
> 
>  
> 
> The stack trace of python calls that resulted in this exception/failure was:
> 
> File: 'exec_python_func() autogenerated', lineno: 2, function: 
> 
>  0001:
> 
> *** 0002:base_do_fetch(d)
> 
>  0003:
> 
> File: '/sdd/peter/Yocto/TEST/sources/poky/meta/classes/base.bbclass',
> lineno: 134, function: base_do_fetch
> 
>  0130:if len(src_uri) == 0:
> 
>  0131:return
> 
>  0132:
> 
>  0133:try:
> 
> *** 0134:fetcher = bb.fetch2.Fetch(src_uri, d)
> 
>  0135:fetcher.download()
> 
>  0136:except bb.fetch2.BBFetchException as e:
> 
>  0137:bb.fatal(str(e))
> 
>  0138:}
> 
> File:
> '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py',
> lineno: 1535, function: __init__
> 
>  1531:
> 
>  1532:for url in urls:
> 
>  1533:if url not in self.ud:
> 
>  1534:try:
> 
> *** 1535:self.ud[url] = FetchData(url, d, localonly)
> 
>  1536:except NonLocalMethod:
> 
>  1537:if localonly:
> 
>  1538:self.ud[url] = None
> 
>  1539:pass
> 
> File:
> '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py',
> lineno: 1214, function: __init__
> 
>  1210:logger.warning('Consider updating %s recipe to use
> "protocol" not "proto" in SRC_URI.', d.getVar('PN'))
> 
>  1211:self.parm["protocol"] = self.parm.get("proto", None)
> 
>  1212:
> 
>  1213:if hasattr(self.method, "urldata_init"):
> 
> *** 1214:self.method.urldata_init(self, d)
> 
>  1215:
> 
>  1216:if "localpath" in self.parm:
> 
>  1217:# if user sets localpath for file, use it instead.
> 
>  1218:self.localpath = self.parm["localpath"]
> 
> File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/hg.py',
> lineno: 70, function: urldata_init
> 
>  0066:ud.proto = 'file'
> 
>  0067:else:
> 
>  0068:ud.proto = "hg"
> 
>  0069:
> 
> *** 0070:ud.setup_revisons(d)
> 
>  0071:
> 
>  0072:if 'rev' in ud.parm:
> 
>  0073:ud.revision = ud.parm['rev']
> 
>  0074:elif not ud.revision:
> 
> File:
> '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py',
> lineno: 1244, function: setup_revisons
> 
>  1240:
> 
>  1241:def setup_revisons(self, d):
> 
>  1242:self.revisions = {}
> 
>  1243:for name in self.names:
> 
> *** 1244:self.revisions[name] = srcrev_internal_helper(self,
> d, name)
> 
>  1245:
> 
>  1246:# add compatibility code for non name specified case
> 
>  1247:if len(self.names) == 1:
> 
>  1248:self.revision = self.revisions[self.names[0]]
> 
> File:
> '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py',
> lineno: 1109, function: srcrev_internal_helper
> 
>  1105:
> 
>  1106:if srcrev == "INVALID" or not srcrev:
> 
>  1107:raise FetchError("Please set a valid SRCREV for url %s
> (possible key names are %s, or use a ;rev=X URL parameter)" %
> (str(attempts), ud.url), ud.url)
> 
>  1108:if srcrev == "AUTOINC":
> 
> *** 1109:srcrev = ud.method.latest_revision(ud, d, name)
> 
>  1110:
> 
>  :return srcrev
> 
>  1112:
> 
>  1113:def get_checksum_file_list(d):
> 
> File:
> '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py',
> lineno: 1500, function: latest_revision
> 
>  1496:if not hasattr(self, "_latest_revision"):
> 
>  1497:raise ParameterError("The fetcher for this URL
> does not support _latest_revision", url)
> 
>  1498:
> 
>  1499:revs = bb.persist_data.persist('BB_URI_HEADREVS', d)
> 
> *** 1500:key = self.generate_revision_key(ud, d, name)
> 
>  1501:try:
> 
>  1502:return revs[key]
> 
>  1503:except KeyError:
> 
>  1504:revs[key] = rev =

Re: [yocto] mips64 with 'seh' instruction?

2017-01-26 Thread Khem Raj 


On 1/26/17 2:26 AM, Jason Cooper wrote:
> Folks,
> 
> I'm trying to build a mips64 toolchain and qemu runtime. I can build and
> run code but if I link with a third-party library that contains the
> 'seh' assembly instruction the executable is killed with SIGILL Illegal
> Instruction, when run with qemu.
> 
> If I run the program on the target it works fine. Looking at the
> disassembly shows me that this is when qemu is trying to execute the
> 'seh' instruction. This is Krogoth 2.1.2 with:
> 
> MACHINE = "qemumips64"
> TARGET_FPU = "soft"
> DEFAULTTUNE = "mips64-nf"
> TUNE_FEATURES = "n64 bigendian"
> 
> The 'seh' instruction was introduced in mips32 Release 2, I believe. I
> tried a DEFAULTTUNE of "mips32r2" and a few others but they did not
> help... or perhaps I should be looking at the qemu code?

Right. qemu supports seh/seb for long time for mips32r2, so I believe
first you should see if we are invoking qemu with right machine type
which is based on mips32r2 architecture. A quick look into runqemu code
shows that we are using -machine malta which may be mips32r1 emulation

> 
> Thanks
> 
> Jason
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Is it possible NOT to split kernel modules in multiple packages

2017-01-26 Thread Khem Raj 


On 1/25/17 11:29 PM, Prasant J wrote:
> Hi,
> 
> I'm using Morty release to create my custom BSP package for cortex-a5
> based processor.
> 
> I'm using my own custom kernel recipe that inherits kernel.bbclass
> (which inherits kernel-module-split.bbclass)
> 
> 
> All the modules are split in their own rpm packages. Is it possible
> that  only one RPM package is created for all kernel modules and there
> is no split?
> 

I guess you want to include all the modules into your image. In that
case you can add

MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"

in your machine config.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] OpenEmbedded Stand at FOSDEM

2017-01-26 Thread Andreas Müller 
On Thu, Jan 5, 2017 at 4:30 PM, Philip Balister  wrote:
> On 01/03/2017 08:13 PM, Andreas Müller wrote:
>> On Tue, Jan 3, 2017 at 4:32 PM, Philip Balister  wrote:
>>> Every year since 2007, OpenEmbedded has a stand at FOSDEM
>>> (http://www.fosdem.org)
>>>
>>> From the first year:
>>>
>>> https://www.flickr.com/photos/32615155@N00/405229708/in/album-72157594561002629/
>>>
>>> Belen and I are sort of organizing this, but both of us are also
>>> involved in devrooms, so we will need a lot of help manning the stand
>>> and getting some demos together.
>>>
>>> Demos should try and show how the project makes embedded work easier, by
>>> showing tools and/or cool examples of devices using Linux built with
>>> OpenEmbedded. In previous years, we've shown toaster with data collected
>>> from demos on the table. Collections of devices running images built
>>> from the same recipe and interesting products using Linux by OpenEmbedded.
>>>
>>> I'm happy to try and organize demos and staffing, but I could really use
>>> some help this year, so if you are in a position to tak ethe lead on
>>> operating the stand, that would be a huge help to me and the rest of the
>>> project.
>>>
>>> Thanks,
>>>
>>> Philip
Nobody?

Andreas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH] pthreads-win32: fix dependencies

2017-01-26 Thread Juro Bystricky 
This commit fixes the build error:

make[1]: x86_64-pokysdk-mingw32-gcc: Command not found

The build error appeared after oe-core switched to Recipe
Specific Sysroots.

[YOCTO#10971]

Signed-off-by: Juro Bystricky 
---
 recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb 
b/recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb
index 68291b9..e4a0f80 100644
--- a/recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb
+++ b/recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb
@@ -21,7 +21,7 @@ SRC_URI[sha256sum] = 
"e6aca7aea8de33d9c8580bcb3a0ea3ec0a7ace4ba3f4e263ac7c7b66bc
 S = "${WORKDIR}/pthreads-w32-${PVdash}-release"
 
 INHIBIT_DEFAULT_DEPS = "1"
-DEPENDS = "virtual/${SDK_PREFIX}gcc-initial libgcc virtual/libc"
+DEPENDS = "virtual/${SDK_PREFIX}gcc libgcc virtual/libc"
 
 do_configure_prepend() {
 ## First reset all permissions because all are executable
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QEMU with host USB serial

2017-01-26 Thread colin.helliwell 
'chown' that is, not 'chmod'!

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of colin.helliw...@ln-systems.com
Sent: 26 January 2017 14:22
To: 'Yocto discussion list' 
Subject: [yocto] QEMU with host USB serial

 

.. I've done a 'chmod me:me' on the relevant /dev/bus/usb/xxx/yyy node.

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QEMU with host USB serial

2017-01-26 Thread colin.helliwell 
I'm investigating using qemu to give us some test capability, for which we
need to use the host's serial devices.

I have a qemu build which boots up fine; I'm trying to give it access to the
host USB. To keep it simple(r), I've seen mention of FTDI's device
(0403:6001) in the qemu source so that's what I've plugged in. I've done a
'chmod me:me' on the relevant /dev/bus/usb/xxx/yyy node.

 

I can't though figure out what options I should be passing to runqemu to
hook this in. I daresay I may need bootparams too, but am first just trying
to get past 'qemuparams'.

As a starting point, I'm trying things like

runqemu qemux86-64 nographic qemuparams="-usbdevice serial"

 

which reports

 

Continuing with the following parameters:

KERNEL:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/bzImage-qemux86-64.bin]

ROOTFS:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4]

FSTYPE: [ext4]

Setting up tap interface under sudo

Acquiring lockfile for tap0...

-net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no
-cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware   -nographic
-usbdevice serial -m 256

Running qemu-system-x86_64...

/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/sysroots/x86_64-linux/u
sr/bin/qemu-system-x86_64 -kernel
/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-6
4/bzImage-qemux86-64.bin -net nic,model=virtio -net
tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot
-nographic -usbdevice serial -m 256 -serial mon:stdio -serial null --append
"vga=0 uvesafb.mode_option=640x480-32 root=/dev/vda rw mem=256M
ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 rootfstype=ext4
console=ttyS0"

qemu-system-x86_64: -usbdevice serial: character device specification needed

qemu-system-x86_64: -usbdevice serial: Failed to create USB device
'usb-serial'

qemu: could not add USB device 'serial'

Set 'tap0' nonpersistent

Releasing lockfile of preconfigured tap device 'tap0'

 

Or

   runqemu qemux86-64 nographic qemuparams="-device
usb-serial,vendorid=0403,productid=6001"

 

which reports

 

Please use simplified serial or kvm options instead

Continuing with the following parameters:

KERNEL:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/bzImage-qemux86-64.bin]

ROOTFS:
[/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-
64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4]

FSTYPE: [ext4]

Setting up tap interface under sudo

Acquiring lockfile for tap0...

-net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no
-cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware   -nographic
-device usb-serial,vendorid=0403,productid=6001 -m 256

Running qemu-system-x86_64...

/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/sysroots/x86_64-linux/u
sr/bin/qemu-system-x86_64 -kernel
/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemux86-6
4/bzImage-qemux86-64.bin -net nic,model=virtio -net
tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu core2duo -drive
file=/home/colin/100051-karo/fsl-community-bsp/buildq/tmp/deploy/images/qemu
x86-64/core-image-qemu-qemux86-64-20170124145819.rootfs.ext4,if=virtio,forma
t=raw -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot
-nographic -device usb-serial,vendorid=0403,productid=6001 -m 256 -serial
null --append "vga=0 uvesafb.mode_option=640x480-32 root=/dev/vda rw
mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1
rootfstype=ext4 console=ttyS0"

QEMU 2.4.0 monitor - type 'help' for more information

(qemu) usb_device_add 1 'wacom-tablet'

usb_device_add success 'wacom-tablet'

qemu-system-x86_64: -device usb-serial,vendorid=0403,productid=6001:
Property '.vendorid' not found

Set 'tap0' nonpersistent

Releasing lockfile of preconfigured tap device 'tap0'

 

 

Can someone clue me in on the correct syntax please!

Thanks

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Exception in bitbake during build of openjdk-8 using meta-linaro

2017-01-26 Thread SMITH Peter T 
Hi, I am trying to build openjdk-8 from the meta-linaro layer (I'm specifically 
interested in building for aarch64), everything proceeds well with gathering 
and building the dependencies until poky/bitbake attempts to fetch sources 
using hg when I see the error below. Anyone seen this before or can offer a 
pointer to what might be wrong?


DEBUG: Executing python function do_fetch
DEBUG: Executing python function base_do_fetch
ERROR: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
*** 0002:base_do_fetch(d)
 0003:
File: '/sdd/peter/Yocto/TEST/sources/poky/meta/classes/base.bbclass', lineno: 
134, function: base_do_fetch
 0130:if len(src_uri) == 0:
 0131:return
 0132:
 0133:try:
*** 0134:fetcher = bb.fetch2.Fetch(src_uri, d)
 0135:fetcher.download()
 0136:except bb.fetch2.BBFetchException as e:
 0137:bb.fatal(str(e))
 0138:}
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1535, function: __init__
 1531:
 1532:for url in urls:
 1533:if url not in self.ud:
 1534:try:
*** 1535:self.ud[url] = FetchData(url, d, localonly)
 1536:except NonLocalMethod:
 1537:if localonly:
 1538:self.ud[url] = None
 1539:pass
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1214, function: __init__
 1210:logger.warning('Consider updating %s recipe to use 
"protocol" not "proto" in SRC_URI.', d.getVar('PN'))
 1211:self.parm["protocol"] = self.parm.get("proto", None)
 1212:
 1213:if hasattr(self.method, "urldata_init"):
*** 1214:self.method.urldata_init(self, d)
 1215:
 1216:if "localpath" in self.parm:
 1217:# if user sets localpath for file, use it instead.
 1218:self.localpath = self.parm["localpath"]
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/hg.py', lineno: 
70, function: urldata_init
 0066:ud.proto = 'file'
 0067:else:
 0068:ud.proto = "hg"
 0069:
*** 0070:ud.setup_revisons(d)
 0071:
 0072:if 'rev' in ud.parm:
 0073:ud.revision = ud.parm['rev']
 0074:elif not ud.revision:
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1244, function: setup_revisons
 1240:
 1241:def setup_revisons(self, d):
 1242:self.revisions = {}
 1243:for name in self.names:
*** 1244:self.revisions[name] = srcrev_internal_helper(self, d, 
name)
 1245:
 1246:# add compatibility code for non name specified case
 1247:if len(self.names) == 1:
 1248:self.revision = self.revisions[self.names[0]]
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1109, function: srcrev_internal_helper
 1105:
 1106:if srcrev == "INVALID" or not srcrev:
 1107:raise FetchError("Please set a valid SRCREV for url %s 
(possible key names are %s, or use a ;rev=X URL parameter)" % (str(attempts), 
ud.url), ud.url)
 1108:if srcrev == "AUTOINC":
*** 1109:srcrev = ud.method.latest_revision(ud, d, name)
 1110:
 :return srcrev
 1112:
 1113:def get_checksum_file_list(d):
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1500, function: latest_revision
 1496:if not hasattr(self, "_latest_revision"):
 1497:raise ParameterError("The fetcher for this URL does not 
support _latest_revision", url)
 1498:
 1499:revs = bb.persist_data.persist('BB_URI_HEADREVS', d)
*** 1500:key = self.generate_revision_key(ud, d, name)
 1501:try:
 1502:return revs[key]
 1503:except KeyError:
 1504:revs[key] = rev = self._latest_revision(ud, d, name)
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/__init__.py', 
lineno: 1512, function: generate_revision_key
 1508:latest_rev = self._build_revision(ud, d, name)
 1509:return True, str(latest_rev)
 1510:
 1511:def generate_revision_key(self, ud, d, name):
*** 1512:key = self._revision_key(ud, d, name)
 1513:return "%s-%s" % (key, d.getVar("PN") or "")
 1514:
 1515:class Fetch(object):
 1516:def __init__(self, urls, d, cache = True, localonly = False, 
connection_cache = None):
File: '/sdd/peter/Yocto/TEST/sources/poky/bitbake/lib/bb/fetch2/hg.py', lineno: 
235, function: _revision_key
 0231:

[linux-yocto] [PATCH 3/4] Filesystem encryption support

2017-01-26 Thread Jussi Laako 
This patch enables ext4 filesystem encryption and also layered
filesystem encryption.

Signed-off-by: Jussi Laako 
---
 cfg/fs/ext4.cfg  | 2 ++
 ktypes/preempt-rt/preempt-rt.cfg | 8 
 ktypes/standard/standard.cfg | 8 
 3 files changed, 18 insertions(+)

diff --git a/cfg/fs/ext4.cfg b/cfg/fs/ext4.cfg
index bc5d70b7..75d10881 100644
--- a/cfg/fs/ext4.cfg
+++ b/cfg/fs/ext4.cfg
@@ -2,3 +2,5 @@ CONFIG_EXT4_FS=y
 CONFIG_EXT4_USE_FOR_EXT23=y
 CONFIG_EXT4_FS_POSIX_ACL=y
 CONFIG_EXT4_FS_SECURITY=y
+CONFIG_EXT4_ENCRYPTION=y
+CONFIG_EXT4_FS_ENCRYPTION=y
diff --git a/ktypes/preempt-rt/preempt-rt.cfg b/ktypes/preempt-rt/preempt-rt.cfg
index 4c62804a..7215ed3c 100644
--- a/ktypes/preempt-rt/preempt-rt.cfg
+++ b/ktypes/preempt-rt/preempt-rt.cfg
@@ -1108,6 +1108,14 @@ CONFIG_CRYPTO_CRC32C=m
 CONFIG_CRYPTO_TEST=m
 
 #
+# Layered filesystem encryption
+#
+CONFIG_FS_ENCRYPTION=y
+CONFIG_ENCRYPTED_KEYS=y
+CONFIG_CRYPTO_SEQIV=y
+CONFIG_CRYPTO_CTR=y
+
+#
 # Hardware crypto devices
 #
 
diff --git a/ktypes/standard/standard.cfg b/ktypes/standard/standard.cfg
index b3dbde50..c99ab8a8 100644
--- a/ktypes/standard/standard.cfg
+++ b/ktypes/standard/standard.cfg
@@ -1098,6 +1098,14 @@ CONFIG_CRYPTO_CRC32C=m
 CONFIG_CRYPTO_TEST=m
 
 #
+# Layered filesystem encryption
+#
+CONFIG_FS_ENCRYPTION=y
+CONFIG_ENCRYPTED_KEYS=y
+CONFIG_CRYPTO_SEQIV=y
+CONFIG_CRYPTO_CTR=y
+
+#
 # Hardware crypto devices
 #
 
-- 
2.11.0

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 4/4] Add support and drivers for CAN bus as feature

2017-01-26 Thread Jussi Laako 
This feature adds support for CAN bus and drivers for CAN bus adapters.

Signed-off-by: Jussi Laako 
---
 features/can/can.cfg | 32 
 features/can/can.scc |  4 
 2 files changed, 36 insertions(+)
 create mode 100644 features/can/can.cfg
 create mode 100644 features/can/can.scc

diff --git a/features/can/can.cfg b/features/can/can.cfg
new file mode 100644
index ..950fb59a
--- /dev/null
+++ b/features/can/can.cfg
@@ -0,0 +1,32 @@
+# platform and USB devices
+CONFIG_CAN=m
+CONFIG_CAN_VCAN=m
+CONFIG_CAN_CALC_BITTIMING=y
+CONFIG_CAN_SJA1000=m
+CONFIG_CAN_SJA1000_PLATFORM=m
+CONFIG_CAN_C_CAN=m
+CONFIG_CAN_C_CAN_PLATFORM=m
+CONFIG_CAN_CC770=m
+CONFIG_CAN_CC770_PLATFORM=m
+CONFIG_CAN_SOFTING=m
+CONFIG_CAN_SLCAN=m
+CONFIG_CAN_IFI_CANFD=m
+CONFIG_CAN_M_CAN=m
+CONFIG_CAN_EMS_USB=m
+CONFIG_CAN_ESD_USB2=m
+CONFIG_CAN_GS_USB=m
+CONFIG_CAN_KVASER_USB=m
+CONFIG_CAN_PEAK_USB=m
+CONFIG_CAN_8DEV_USB=m
+# x86 PCH
+#CONFIG_PCH_CAN=m
+# drivers for ISA/PCI cards
+CONFIG_CAN_C_CAN_PCI=m
+# Philips/NXP SJA1000 based PCI(e)
+CONFIG_CAN_EMS_PCI=m
+CONFIG_CAN_PEAK_PCI=m
+CONFIG_CAN_PEAK_PCIEC=m
+CONFIG_CAN_KVASER_PCI=m
+CONFIG_CAN_PLX_PCI=m
+# SPI bus devices
+CONFIG_CAN_MCP251X=m
diff --git a/features/can/can.scc b/features/can/can.scc
new file mode 100644
index ..caaf117a
--- /dev/null
+++ b/features/can/can.scc
@@ -0,0 +1,4 @@
+define KFEATURE_DESCRIPTION "Enable Controller Area Network (CAN bus) support"
+define KFEATURE_COMPATIBILITY board
+
+kconf hardware can.cfg
-- 
2.11.0

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 2/4] Update NFC support

2017-01-26 Thread Jussi Laako 
Update set of NFC drivers. Also correct scc and module dependencies.

Signed-off-by: Jussi Laako 
---
 features/nfc/nfc-generic.cfg |  3 +++
 features/nfc/nfc-vendor.cfg  | 25 +
 features/nfc/nfc-vendor.scc  |  2 +-
 3 files changed, 29 insertions(+), 1 deletion(-)

diff --git a/features/nfc/nfc-generic.cfg b/features/nfc/nfc-generic.cfg
index fc62c7b9..3bb00882 100644
--- a/features/nfc/nfc-generic.cfg
+++ b/features/nfc/nfc-generic.cfg
@@ -3,3 +3,6 @@ CONFIG_NFC_NCI=m
 CONFIG_NFC_NCI_SPI=m
 CONFIG_NFC_HCI=m
 CONFIG_NFC_SHDLC=y
+# required support items
+CONFIG_CRC_ITU_T=m
+CONFIG_CRC_CCITT=m
diff --git a/features/nfc/nfc-vendor.cfg b/features/nfc/nfc-vendor.cfg
index eacccf21..e48bcb91 100644
--- a/features/nfc/nfc-vendor.cfg
+++ b/features/nfc/nfc-vendor.cfg
@@ -1,5 +1,30 @@
+CONFIG_NFC_MEI_PHY=m
 CONFIG_NFC_PN533=m
 CONFIG_NFC_PN533_I2C=m
 CONFIG_NFC_PN533_USB=m
+CONFIG_NFC_PORT100=m
 CONFIG_NFC_MRVL=m
 CONFIG_NFC_MRVL_USB=m
+CONFIG_NFC_MRVL_I2C=m
+CONFIG_NFC_MRVL_SPI=m
+CONFIG_NFC_MICROREAD=m
+CONFIG_NFC_MICROREAD_I2C=m
+CONFIG_NFC_MICROREAD_MEI=m
+CONFIG_NFC_PN544=m
+CONFIG_NFC_PN544_I2C=m
+CONFIG_NFC_PN544_MEI=m
+CONFIG_NFC_ST21NFCA=m
+CONFIG_NFC_ST21NFCA_I2C=m
+CONFIG_NFC_ST21NFCB=m
+CONFIG_NFC_ST21NFCB_I2C=m
+CONFIG_NFC_TRF7970A=m
+CONFIG_NFC_FDP=m
+CONFIG_NFC_FDP_I2C=m
+CONFIG_NFC_ST_NCI=m
+CONFIG_NFC_ST_NCI_I2C=m
+CONFIG_NFC_ST_NCI_SPI=m
+CONFIG_NFC_NXP_NCI=m
+CONFIG_NFC_NXP_NCI_I2C=m
+CONFIG_NFC_S3FWRN5=m
+CONFIG_NFC_S3FWRN5_I2C=m
+CONFIG_NFC_ST95HF=m
diff --git a/features/nfc/nfc-vendor.scc b/features/nfc/nfc-vendor.scc
index 2bfac10d..087cc78a 100644
--- a/features/nfc/nfc-vendor.scc
+++ b/features/nfc/nfc-vendor.scc
@@ -1,6 +1,6 @@
 define KFEATURE_DESCRIPTION "Enable vendor-specific NFC hardware modules"
 define KFEATURE_COMPATIBILITY board
 
-include nfc.scc
+include nfc-generic.scc
 
 kconf hardware nfc-vendor.cfg
-- 
2.11.0

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 1/4] Add eCryptFS filesystem feature

2017-01-26 Thread Jussi Laako 
Add layered encrypted filesystem eCryptFS support feature.

Signed-off-by: Jussi Laako 
---
 features/ecryptfs/ecryptfs.cfg | 2 ++
 features/ecryptfs/ecryptfs.scc | 4 
 2 files changed, 6 insertions(+)
 create mode 100644 features/ecryptfs/ecryptfs.cfg
 create mode 100644 features/ecryptfs/ecryptfs.scc

diff --git a/features/ecryptfs/ecryptfs.cfg b/features/ecryptfs/ecryptfs.cfg
new file mode 100644
index ..07e7ee86
--- /dev/null
+++ b/features/ecryptfs/ecryptfs.cfg
@@ -0,0 +1,2 @@
+CONFIG_ECRYPT_FS=m
+CONFIG_ECRYPT_FS_MESSAGING=y
diff --git a/features/ecryptfs/ecryptfs.scc b/features/ecryptfs/ecryptfs.scc
new file mode 100644
index ..6c246f1a
--- /dev/null
+++ b/features/ecryptfs/ecryptfs.scc
@@ -0,0 +1,4 @@
+define KFEATURE_DESCRIPTION "Layered encrypted eCryptFS filesystem support"
+define KFEATURE_COMPATIBILITY all
+
+kconf non-hardware ecryptfs.cfg
-- 
2.11.0

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [yocto-kernel-cache] [PATCH] Updates from Ostro project

2017-01-26 Thread Jussi Laako 
This set of patches targets yocto-kernel-cache master/4.9 branches.

This is part of ongoing effort to update some parts of yocto-kernel-cache
based on refreshed items from the Ostro project.

1: Adds eCryptFS layered filesystem encryption support as a feature
2: Updates NFC support feature and chains the dependencies correctly
3: Enables new ext4 and layered filesystem encryption features
4: Adds support and drivers for CAN-bus as a feature

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] mips64 with 'seh' instruction?

2017-01-26 Thread Jason Cooper 

Folks,

I'm trying to build a mips64 toolchain and qemu runtime. I can build and 
run code but if I link with a third-party library that contains the 
'seh' assembly instruction the executable is killed with SIGILL Illegal 
Instruction, when run with qemu.


If I run the program on the target it works fine. Looking at the 
disassembly shows me that this is when qemu is trying to execute the 
'seh' instruction. This is Krogoth 2.1.2 with:


MACHINE = "qemumips64"
TARGET_FPU = "soft"
DEFAULTTUNE = "mips64-nf"
TUNE_FEATURES = "n64 bigendian"

The 'seh' instruction was introduced in mips32 Release 2, I believe. I 
tried a DEFAULTTUNE of "mips32r2" and a few others but they did not 
help... or perhaps I should be looking at the qemu code?


Thanks

Jason

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] kernel-yocto: Update source tree with kgit-meta

2017-01-26 Thread David Vincent 
kgit-meta processes a file called meta-series to update the source tree
(create, merge branches, ...). This fixes the merging of feature
branches using the new merge command of yocto-kernel-tools.

Signed-off-by: David Vincent 
---
 meta/classes/kernel-yocto.bbclass | 13 +
 1 file changed, 13 insertions(+)

diff --git a/meta/classes/kernel-yocto.bbclass 
b/meta/classes/kernel-yocto.bbclass
index 5cfd8aff50..b37ac01a84 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -162,6 +162,19 @@ do_kernel_metadata() {
bbfatal_log "Could not generate configuration queue for 
${KMACHINE}."
fi
fi
+
+   # Update git repository by running kgit-meta
+   cd ${S}
+
+   check_git_config
+   meta_dir=$(kgit --meta)
+   if [ -f "${meta_dir}/meta-series" ]; then
+   kgit-meta ${meta_dir}/meta-series
+   if [ $? -ne 0 ]; then
+   bberror "Could not apply metadata for ${KMACHINE}."
+   bbfatal_log "Failures can be resolved in the linux 
source directory ${S})"
+   fi
+   fi
 }
 
 do_patch() {
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Is it possible NOT to split kernel modules in multiple packages

2017-01-26 Thread Prasant J 
Hi,

I'm using Morty release to create my custom BSP package for cortex-a5
based processor.

I'm using my own custom kernel recipe that inherits kernel.bbclass
(which inherits kernel-module-split.bbclass)


All the modules are split in their own rpm packages. Is it possible
that  only one RPM package is created for all kernel modules and there
is no split?



Regards, Pj
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto