[yocto] [meta-ivi][PATCH 1/3] qemux86.cfg: Activate ecryptfs
Signed-off-by: Andrei Gherzan --- recipes-kernel/linux/linux-yocto/qemux86.cfg |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/recipes-kernel/linux/linux-yocto/qemux86.cfg b/recipes-kernel/linux/linux-yocto/qemux86.cfg index ff828b9..6f6ea51 100644 --- a/recipes-kernel/linux/linux-yocto/qemux86.cfg +++ b/recipes-kernel/linux/linux-yocto/qemux86.cfg @@ -1,3 +1,9 @@ # config for adding support for AF_BUS sockets CONFIG_AF_BUS=y CONFIG_NETFILTER_DBUS=y + +# Activate ecryptfs +CONFIG_EXPERIMENTAL=y +CONFIG_KEYS=y +CONFIG_CRYPTO=y +CONFIG_ECRYPT_FS=y -- 1.7.5.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ivi][PATCH 2/3] vexpress_a9.cfg: Activate ecryptfs
Signed-off-by: Andrei Gherzan --- recipes-kernel/linux/linux-yocto/vexpress_a9.cfg |6 ++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/recipes-kernel/linux/linux-yocto/vexpress_a9.cfg b/recipes-kernel/linux/linux-yocto/vexpress_a9.cfg index 9c5052a..5bb37a2 100644 --- a/recipes-kernel/linux/linux-yocto/vexpress_a9.cfg +++ b/recipes-kernel/linux/linux-yocto/vexpress_a9.cfg @@ -831,3 +831,9 @@ CONFIG_AF_BUS=y CONFIG_NETFILTER_DBUS=y CONFIG_REGULATOR=n + +# Activate ecryptfs +CONFIG_EXPERIMENTAL=y +CONFIG_KEYS=y +CONFIG_CRYPTO=y +CONFIG_ECRYPT_FS=y -- 1.7.5.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-ivi][PATCH 3/3] linux-yocto: Add PRINC
Signed-off-by: Andrei Gherzan
---
recipes-kernel/linux/linux-yocto_3.4.bbappend |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/recipes-kernel/linux/linux-yocto_3.4.bbappend
b/recipes-kernel/linux/linux-yocto_3.4.bbappend
index ca9afbd..10327c3 100644
--- a/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ b/recipes-kernel/linux/linux-yocto_3.4.bbappend
@@ -1,3 +1,5 @@
+PRINC := "${@int(PRINC) + 1}"
+
# find defconfig path
FILESEXTRAPATHS := "${THISDIR}/${PN}"
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] pulseaudio madness
On 2013-02-05 06:52, Burton, Ross wrote: Hi Gary, On 5 February 2013 12:44, Gary Thomas wrote: I have a multi-media application/system (built with Poky/Yocto of course) that is currently using ALSA for the sound. This works great but now I'd like to be able to share some of the sound resources, in particular the audio output (speakers). To satisfy this, I looked at pulseaudio, but I'm overwhelmed by the package choices (there are 120 packages), not to mention what to do about configuration. I don't see any examples (images, etc) that use pulseaudio. Does anyone have any recommendations on what I might need to install, how to configure it, etc, to take over from my simple ALSA setup? The top tip is the PulseAudio documentation on the web site, that lists all the plugins and what they do. The pulseaudio-server package depends on all of the important plugins, so that gives you a working PA setup once you've started it. You might want to have a look at Guacamayo's use of PA, that uses it and will automatically switch output when new speakers are plugged in too.https://github.com/Guacamayo Thanks, that helped. I've built Guacamayo for my RaspberryPi and can see how it's set up. One thing I'm missing is how the pulseaudio server gets started? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Running Sato/X11 as non-root
In my attempt to get pulseaudio running, I need to bring up my X11 session with a user that is not root. The default (core-image-sato) always starts X11 as root. This yields these errors when starting (with pulseaudio installed): W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). E: [autospawn] core-util.c: Home directory /home/root not ours. W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). E: [autospawn] core-util.c: Home directory /home/root not ours. W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock So, I tried to make X run as user 'demo', which I created, by putting 'demo' in /etc/X11/Xusername. Now it seems to try and run as 'demo', but falls over quite quickly: Fatal server error: [2951371.651] xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) [2951371.651] [2951371.651] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [2951371.651] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [2951371.651] (EE) [2951371.652] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor [2951371.652] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor [2951371.652] Server terminated with error (1). Closing log file. Any ideas how I get this going? n.b. not only do I want to get this going for myself, but I think the discussion (and maybe subsequent documentation) is useful since this functionality is in OE-core (or is it only Poky/Yocto - hard to tell)... -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] pulseaudio madness
On 06/02/13 13:50, Gary Thomas wrote: > On 2013-02-05 06:52, Burton, Ross wrote: >> Hi Gary, >> >> On 5 February 2013 12:44, Gary Thomas wrote: >>> I have a multi-media application/system (built with Poky/Yocto of >>> course) >>> that is currently using ALSA for the sound. This works great but now >>> I'd like to be able to share some of the sound resources, in particular >>> the audio output (speakers). To satisfy this, I looked at pulseaudio, >>> but I'm overwhelmed by the package choices (there are 120 packages), >>> not to mention what to do about configuration. >>> >>> I don't see any examples (images, etc) that use pulseaudio. >>> >>> Does anyone have any recommendations on what I might need to install, >>> how to configure it, etc, to take over from my simple ALSA setup? >> >> The top tip is the PulseAudio documentation on the web site, that >> lists all the plugins and what they do. The pulseaudio-server package >> depends on all of the important plugins, so that gives you a working >> PA setup once you've started it. >> >> You might want to have a look at Guacamayo's use of PA, that uses it >> and will automatically switch output when new speakers are plugged in >> too.https://github.com/Guacamayo > > Thanks, that helped. I've built Guacamayo for my RaspberryPi and > can see how it's set up. > > One thing I'm missing is how the pulseaudio server gets started? Depends on the image type, either from /eta/xdg/autostart, or for the audiplayer image from the /etc/init.d/guacamayo-session-* script. Tomas ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Running Sato/X11 as non-root
On 06/02/13 14:40, Gary Thomas wrote: > In my attempt to get pulseaudio running, I need to bring up > my X11 session with a user that is not root. The default > (core-image-sato) always starts X11 as root. This yields > these errors when starting (with pulseaudio installed): > W: [pulseaudio] main.c: This program is not intended to be run as root > (unless --system is specified). > E: [autospawn] core-util.c: Home directory /home/root not ours. > W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. > E: [pulseaudio] main.c: Failed to acquire autospawn lock > W: [pulseaudio] main.c: This program is not intended to be run as root > (unless --system is specified). > E: [autospawn] core-util.c: Home directory /home/root not ours. > W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. > E: [pulseaudio] main.c: Failed to acquire autospawn lock > > So, I tried to make X run as user 'demo', which I created, by > putting 'demo' in /etc/X11/Xusername. Now it seems to try > and run as 'demo', but falls over quite quickly: > Fatal server error: > [2951371.651] xf86OpenConsole: Cannot open /dev/tty0 (No such file or > directory) > [2951371.651] > [2951371.651] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org for help. > [2951371.651] (EE) Please also check the log file at > "/var/log/Xorg.0.log" for additional information. > [2951371.651] (EE) > [2951371.652] (WW) xf86CloseConsole: KDSETMODE failed: Bad file > descriptor > [2951371.652] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file > descriptor > [2951371.652] Server terminated with error (1). Closing log file. > > Any ideas how I get this going? > > n.b. not only do I want to get this going for myself, but I think > the discussion (and maybe subsequent documentation) is useful since > this functionality is in OE-core (or is it only Poky/Yocto - hard > to tell)... The user that the rootless X in Poky is expecting is called xuser; if you use your own, you need to make sure that it's in all the appropriate groups the server needs it to be in, etc.; see the xserver-nodm-init recipe. Tomas -- http://sleepfive.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] systemtap fetch failure on 'danny' (cherry-pick fix from master)
Hi all, Using 'danny' branch to build a rootfs image i sometimes get a 'systemtap' fetch failure: ERROR: Fetcher failure: Fetch command failed with exit code 128, output: Cloning into bare repository '.../downloads/git2/sources.redhat.com.git.systemtap.git'... fatal: unable to connect to sources.redhat.com: sources.redhat.com[0: 209.132.183.64]: errno=Connection timed out This seems to be fixed in 'master' branch: commit f3f4ac33ee7fa9cd35d06821fc3e26077303998a Author: Maxin B. John Date: Fri Dec 14 13:00:28 2012 +0100 Update the SRC_URI in systemtap recipe Could that commit be cherry-picked to 'danny'? It doesn't seem to be very dangerous as it's only a SRC_URI change. - Javier Viguera Software Engineer Digi International® Spain S.A.U. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] systemtap fetch failure on 'danny' (cherry-pick fix from master)
On 6 February 2013 15:40, Javier Viguera wrote: > This seems to be fixed in 'master' branch: > > commit f3f4ac33ee7fa9cd35d06821fc3e26077303998a > Author: Maxin B. John > Date: Fri Dec 14 13:00:28 2012 +0100 > > Update the SRC_URI in systemtap recipe > > > Could that commit be cherry-picked to 'danny'? You'll be pleased to know it's in danny-next already, so should be hitting danny in the next day or so. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] systemtap fetch failure on 'danny' (cherry-pick fix from master)
On 02/06/2013 04:48 PM, Burton, Ross wrote: You'll be pleased to know it's in danny-next already, so should be hitting danny in the next day or so. Good to know. Thanks. - Javier Viguera Software Engineer Digi International® Spain S.A.U. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] User id/group not quite right?
Just checking on the X11 user 'xuser' which should be created
with a bunch of groups via this recipe snippet:
USERADD_PARAM_${PN} = "--create-home \
--groups video,tty,audio \
--user-group xuser"
However, when I log in as 'xuser', I don't see them?
login: xuser
$ id
uid=1001(xuser) gid=1001(xuser) groups=1001(xuser)
$ grep xuser /etc/group
tty:x:5:demo,xuser
audio:x:29:demo,xuser,pulse
video:x:44:demo,xuser
xuser:x:1001:
They do seem to be set though:
$ python
Python 2.7.3 (default, Jan 15 2013, 10:27:28)
[GCC 4.7.2] on linux2
T ype "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.getgroups()
[5, 29, 44, 1001]
Looks like the busybox 'id' applet is broken?
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] pulseaudio madness
On 2013-02-06 06:50, Gary Thomas wrote: On 2013-02-05 06:52, Burton, Ross wrote: Hi Gary, On 5 February 2013 12:44, Gary Thomas wrote: I have a multi-media application/system (built with Poky/Yocto of course) that is currently using ALSA for the sound. This works great but now I'd like to be able to share some of the sound resources, in particular the audio output (speakers). To satisfy this, I looked at pulseaudio, but I'm overwhelmed by the package choices (there are 120 packages), not to mention what to do about configuration. I don't see any examples (images, etc) that use pulseaudio. Does anyone have any recommendations on what I might need to install, how to configure it, etc, to take over from my simple ALSA setup? The top tip is the PulseAudio documentation on the web site, that lists all the plugins and what they do. The pulseaudio-server package depends on all of the important plugins, so that gives you a working PA setup once you've started it. You might want to have a look at Guacamayo's use of PA, that uses it and will automatically switch output when new speakers are plugged in too.https://github.com/Guacamayo Thanks, that helped. I've built Guacamayo for my RaspberryPi and can see how it's set up. That said, I've not had much luck actually getting anything out of the audio :-( I tried the guacamayo-image-mex-raspberrypi.rpi-sdimg which came up and gave me a nice display but it wasn't obvious how to import media and/or make it play. I tried copying some files manually to the SD card, but they wouldn't play either. Then I tried guacamayo-image-audioplayer-raspberrypi.rpi-sdimg and it was even less intuitive. Can you give me some guidance? All I'd like to do is play a simple (.wav) file on y RaspberryPi using pulseaudio. Thanks -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build issue on dlt-daemon
Dear dlt-daemon developer, I came across a build error while building Excalibur image. The exact error log is attached below. The situation of the issue is that at first I built Excalibur image with MACHINE=vexpressa9, then next time, change it to MACHINE=dm814x-evm and built it, then the error happened. It seems dlt-daemon's Makefile still referred previous sysroot. For a workaround, just clean the dlt-daemon, and rebuild again. I am not sure this is bug or not, but please check the clean sequence of dlt-daemon if MACHINE value changes. Sincerely, Kaz Nishimura --- Error log --- | /home/knishimu/working/excalibur/genivi-baseline/build/tmp-eglibc-eglibc/sysroots/i686-linux/usr/bin/armv7a-vfp-neon-oe-linux-gnueabi/arm-oe-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a9 --sysroot=/home/knishimu/working/excalibur/genivi-baseline/build/tmp-eglibc-eglibc/sysroots/vexpressa9 -O2 -g -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a9 --sysroot=/home/knishimu/working/excalibur/genivi-baseline/build/tmp-eglibc-eglibc/sysroots/vexpressa9 -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--as-needed -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--as-needed -o dlt-convert -rdynamic ../lib/libdlt.so.2.9.0 -lrt -lpthread -Wl,-rpath,/home/knishimu/working/excalibur/genivi-baseline/build/tmp-eglibc-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/dlt-daemon-2.9.0-r0/git/src/lib: | /home/knishimu/working/excalibur/genivi-baseline/build/tmp-eglibc-eglibc/sysroots/vexpressa9/usr/lib/crt1.o: In function `_start': | init.c:(.text+0x34): undefined reference to `main' | collect2: error: ld returned 1 exit status | make[2]: *** [src/console/dlt-convert] Error 1 --- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
