Re: [yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

2016-04-13 Thread Petter Mabäcker 
 

2016-04-14 00:04 skrev Trevor Woerner: 

> On Wed 2016-03-30 @
04:35:47 PM, Petter Mabäcker wrote:
> 
>> rpi-ft5406 is an enabler for
Official Raspberry Pi 7 inch touchscreen support.
> 
> I have an
official raspberry pi 7" touchscreen and it's not obvious to me how
> I
would go about enabling it in my config. If I had one of the others I
would
> simply add:
> 
> MACHINE_FEATURES += "pitft pitft22"
> 
> or
>

> MACHINE_FEATURES += "pitft pitft28r"
> 
> to my conf/local.conf, but
what do I do for the official touchscreen?
> 
> Also, by trial and error
I've discovered that my touchscreen comes up as
> /dev/fb0 and not
/dev/fb1. But the xorg config for touchscreen support assumes
>
/dev/fb1. Am I doing something wrong in my build or can anyone think of
a
> reason why my screen would be /dev/fb0 instead of /dev/fb1?
> 
> By
the way
> 
> MACHINE_FEATURES += "pitft pitft22"
> 
> seems to work for
me if I use /dev/fb0, but I'm not sure if that's a fluke?
> 
> Best
regards,
> Trevor

Hi Trevor, 

Actually it's very simple for the
Official rpi touchscreen. 

1. Ensure that you DON'T have pitft support
enabled when using this touchscreen! (PiTFT uses /dev/fb1, which isn't
the case for the official toucscreen). 

2. Build for example
'core-image-sato' 

3. Add: 

echo "dtoverlay=rpi-ft5406" >>
/path/to/sdcard/boot/config.txt 

...and you are done. 

Like stated in
the commit msg this is just an enabler for being able to configure
rpi-ft5406. When I have time I will send the complete solution for this,
perhaps a good idea is to do like a MACHINE_FEATURES as well, to make it
look similar to the PiTFT's usage? 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

2016-04-13 Thread Khem Raj 
On Apr 13, 2016 3:05 PM, "Trevor Woerner"  wrote:
>
> On Wed 2016-03-30 @ 04:35:47 PM, Petter Mabäcker wrote:
> > rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
> > touchscreen support.
>
> I have an official raspberry pi 7" touchscreen and it's not obvious to me
how
> I would go about enabling it in my config. If I had one of the others I
would
> simply add:
>
> MACHINE_FEATURES += "pitft pitft22"
>
> or
>
> MACHINE_FEATURES += "pitft pitft28r"
>
> to my conf/local.conf, but what do I do for the official touchscreen?
>
> Also, by trial and error I've discovered that my touchscreen comes up as
> /dev/fb0 and not /dev/fb1. But the xorg config for touchscreen support
assumes
> /dev/fb1. Am I doing something wrong in my build or can anyone think of a
> reason why my screen would be /dev/fb0 instead of /dev/fb1?
>
> By the way
>
> MACHINE_FEATURES += "pitft pitft22"
>
> seems to work for me if I use /dev/fb0, but I'm not sure if that's a
fluke?

Check the device trees. Are you using  4.1 kernel or some other
>
> Best regards,
> Trevor
> --
> ___
> 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] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

2016-04-13 Thread Trevor Woerner 
On Wed 2016-03-30 @ 04:35:47 PM, Petter Mabäcker wrote:
> rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch
> touchscreen support.

I have an official raspberry pi 7" touchscreen and it's not obvious to me how
I would go about enabling it in my config. If I had one of the others I would
simply add:

MACHINE_FEATURES += "pitft pitft22"

or

MACHINE_FEATURES += "pitft pitft28r"

to my conf/local.conf, but what do I do for the official touchscreen?

Also, by trial and error I've discovered that my touchscreen comes up as
/dev/fb0 and not /dev/fb1. But the xorg config for touchscreen support assumes
/dev/fb1. Am I doing something wrong in my build or can anyone think of a
reason why my screen would be /dev/fb0 instead of /dev/fb1?

By the way

MACHINE_FEATURES += "pitft pitft22"

seems to work for me if I use /dev/fb0, but I'm not sure if that's a fluke?

Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] something like kernel configuration fragments for device tree?

2016-04-13 Thread Daniel. 
Hi Robert,

I know that Raspberry Pi has "Device Tree Overlays", for other
platforms I don't know if that is possible. If you're using Pi you may
add DT Overlays by patching,
take a look at 
https://www.raspberrypi.org/documentation/configuration/device-tree.md
$ Part 2: Device Tree overlays. I think that this is applied by
Pi's boot loader, but I have no ideia if u-boot supports such thing,

Regards, and good luck
- dhs

2016-04-12 10:45 GMT-03:00  :
> Hi,
>
> I was wondering if there is something like kernel config fragments also
> available for device trees from the YP.
>
> It would be convenient, since kernel configuration and device tree might be
> related in some cases.
>
> Regards,
>
> Robert
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [psplash][PATCH 3/3] README: add "Contributing" guideline

2016-04-13 Thread Philip Balister 
On 04/13/2016 09:57 AM, Richard Leitner wrote:
> The "Contributing" guideline section should help people sending their
> patches correctly.
> 
> A similar section is available in nearly all
> layers/repositories hosted on yoctoproject.org. Therefore add it also
> the the psplash repository.
> 
> Signed-off-by: Richard Leitner 
> ---
>  README | 18 ++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/README b/README
> index 86ef6ba..8779a38 100644
> --- a/README
> +++ b/README
> @@ -8,3 +8,21 @@ rotation. Its visual look is configurable by basic source 
> changes.
>  
>  Also included is a 'client' command utility for sending information to
>  psplash such as boot progress information.
> +
> +Contributing
> +
> +To contribute to this layer you should submit the patches for review to the
> +mailing list (yocto@yoctoproject.org).
> +
> +Please refer to
> +http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
> +for some useful guidelines to be followed when submitting patches.
> +
> +Mailing list:
> +https://lists.yoctoproject.org/listinfo/yocto
> +
> +When creating patches, please use something like:
> +git format-patch -M -s --subject-prefix='psplash][PATCH' origin
> +
> +When sending patches, please use something like:
> +git send-email --to yocto@yoctoproject.org 
> 

I cut and paste this line from the meta-oe README for sending patches,
it is a bit simpler than the two step process:

https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/README#L9

Philip

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

[yocto] something like kernel configuration fragments for device tree?

2016-04-13 Thread gmane 

Hi,

I was wondering if there is something like kernel config fragments also 
available for device trees from the YP.


It would be convenient, since kernel configuration and device tree might 
be related in some cases.


Regards,

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

[yocto] [meta-raspberrypi][PATCH] serial console definition split

2016-04-13 Thread Trevor Woerner 
The latest raspberrypi3 puts its console on ttyS0 instead of ttyAMA0 (like all
the preceding boards). Therefore pull this definition out of the common
include file and add it separately for each MACHINE.

Signed-off-by: Trevor Woerner 
---
 conf/machine/include/rpi-base.inc | 2 --
 conf/machine/raspberrypi.conf | 2 ++
 conf/machine/raspberrypi0.conf| 2 ++
 conf/machine/raspberrypi2.conf| 2 ++
 conf/machine/raspberrypi3.conf| 2 ++
 5 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 34eb774..f64bc9d 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -7,8 +7,6 @@ include conf/machine/include/soc-family.inc
 
 IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"
 
-SERIAL_CONSOLE = "115200 ttyAMA0"
-
 XSERVER = " \
 xserver-xorg \
 xf86-input-evdev \
diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf
index e8516e7..0f95f1a 100644
--- a/conf/machine/raspberrypi.conf
+++ b/conf/machine/raspberrypi.conf
@@ -6,3 +6,5 @@ DEFAULTTUNE ?= "arm1176jzfshf"
 
 require conf/machine/include/tune-arm1176jzf-s.inc
 include conf/machine/include/rpi-base.inc
+
+SERIAL_CONSOLE = "115200 ttyAMA0"
diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf
index 58468ed..ccf9ae7 100644
--- a/conf/machine/raspberrypi0.conf
+++ b/conf/machine/raspberrypi0.conf
@@ -4,3 +4,5 @@
 
 MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
 include conf/machine/raspberrypi.conf
+
+SERIAL_CONSOLE = "115200 ttyAMA0"
diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf
index 30edae3..b6346e6 100644
--- a/conf/machine/raspberrypi2.conf
+++ b/conf/machine/raspberrypi2.conf
@@ -6,3 +6,5 @@ DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4"
 
 require conf/machine/include/tune-cortexa7.inc
 include conf/machine/include/rpi-base.inc
+
+SERIAL_CONSOLE = "115200 ttyAMA0"
diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 1b73f2f..cb6056e 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
 
 include conf/machine/raspberrypi2.conf
+
+SERIAL_CONSOLE = "115200 ttyS0"
-- 
2.7.0.rc3

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

Re: [linux-yocto] [PATCH 1/2] preempt-rt.cfg/standard.cfg: enable OVERLAY_FS

2016-04-13 Thread Bruce Ashfield 

On 2016-03-29 11:29 PM, Robert Yang wrote:



On 03/30/2016 11:19 AM, Bruce Ashfield wrote:

On 2016-03-29 9:51 PM, Robert Yang wrote:



On 03/30/2016 09:08 AM, Robert Yang wrote:



On 03/29/2016 08:40 PM, Bruce Ashfield wrote:

On 2016-03-29 3:23 AM, Robert Yang wrote:

Otherwise the live iso will be readonly.


Not true .. overlayfs is one way to have a read/write ISO, but
not the only.

This isn't something we bury in the middle of the ktypes. aufs
has always been a standalone configuration option, and one that
is enabled via KERNEL_FEATURES.

This is an alternative to the exiting aufs use case, and should
be treated a similar way (with a generic feature, an enable and
a disable). See the aufs fragments as a template to follow.


Sounds good, I will send a V2.


Hi Bruce,

After more investigations, linux-yocto 4.4 does have
features/aufs/aufs.scc,
but I can't find any source of aufs in kernel-source, I'm afraid that
linux-yocto doesn't merge aufs' patch. And when I added


aufs simply comes along later in the cycle. Since I do the
merges, I'd know if it was missed or not :)


Thanks, would you please ping me after merged so that I can check
whether live image + aufs works well or not.


FYI: my latest series contains these changes.

Bruce



// Robert




features/aufs/aufs.scc
to KERNEL_FEATURES, I got this in merge_log.txt:

Value requested for CONFIG_AUFS_FS not in final .config
Requested value:  CONFIG_AUFS_FS=y
Actual value:

Since overlayfs has been merged by mainline, maybe we can drop aufs
support ?


Nope .. aufs is still supported, since it has different features
than overlayfs. There is not "one union filesystem to rule them
all".

Bruce



// Robert



// Robert



Bruce



Signed-off-by: Robert Yang 
---
  ktypes/preempt-rt/preempt-rt.cfg | 2 ++
  ktypes/standard/standard.cfg | 2 ++
  2 files changed, 4 insertions(+)

diff --git a/ktypes/preempt-rt/preempt-rt.cfg
b/ktypes/preempt-rt/preempt-rt.cfg
index 4c62804..c4a5617 100644
--- a/ktypes/preempt-rt/preempt-rt.cfg
+++ b/ktypes/preempt-rt/preempt-rt.cfg
@@ -1116,3 +1116,5 @@ CONFIG_CRYPTO_TEST=m
  #
  CONFIG_LIBCRC32C=m
  CONFIG_ZLIB_DEFLATE=m
+
+CONFIG_OVERLAY_FS=y
diff --git a/ktypes/standard/standard.cfg
b/ktypes/standard/standard.cfg
index b3dbde5..4099fda 100644
--- a/ktypes/standard/standard.cfg
+++ b/ktypes/standard/standard.cfg
@@ -1108,3 +1108,5 @@ CONFIG_LIBCRC32C=m
  CONFIG_ZLIB_DEFLATE=m

  CONFIG_SHMEM=y
+
+CONFIG_OVERLAY_FS=y









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

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console

2016-04-13 Thread Trevor Woerner 
On Wed 2016-04-13 @ 04:20:36 AM, Andrei Gherzan wrote:
> On Mon, Apr 11, 2016 at 05:54:44PM -0400, Trevor Woerner wrote:
> > The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> > /dev/ttyAMA0.
> >
> > Signed-off-by: Trevor Woerner 
> > ---
> >  conf/machine/raspberrypi3.conf | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> > index 1b73f2f..cb6056e 100644
> > --- a/conf/machine/raspberrypi3.conf
> > +++ b/conf/machine/raspberrypi3.conf
> > @@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> >  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
> >
> >  include conf/machine/raspberrypi2.conf
> > +
> > +SERIAL_CONSOLE = "115200 ttyS0"
> 
> As this seems not to be unified anymore, would it make sense to remove
> it from rpi-base.inc and define it in every machine conf?

Sure, I can do that too, no problem. I'll start a new patch series for just
this one change since it is a different solution (therefore it won't be a v3
on this one).
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 2/2] userland: Make vchostif as shared library

2016-04-13 Thread Khem Raj 
Thats interesting, I will try to reproduce it

> On Apr 13, 2016, at 7:21 AM, Jonathan Liu  wrote:
> 
> On Thursday, 14 April 2016, Khem Raj  > wrote:
> On Wed, Apr 13, 2016 at 3:05 AM, Jonathan Liu  > wrote:
> > Hi Khem,
> >
> > On 3 April 2016 at 03:59, Khem Raj > 
> > wrote:
> >> This helps in using this library when building
> >> with PIE binaries
> >>
> >> Signed-off-by: Khem Raj >
> >> ---
> >>  .../0014-build-shared-library-for-vchostif.patch   | 28 
> >> ++
> >>  recipes-graphics/userland/userland_git.bb    
> >>|  1 +
> >>  2 files changed, 29 insertions(+)
> >>  create mode 100644 
> >> recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >>
> >> diff --git 
> >> a/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >>  
> >> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >> new file mode 100644
> >> index 000..ca7cb66
> >> --- /dev/null
> >> +++ 
> >> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >> @@ -0,0 +1,28 @@
> >> +From 4e9aa3fffb458ca4fafd2241c18e9c8008b66ad8 Mon Sep 17 00:00:00 2001
> >> +From: Khem Raj >
> >> +Date: Sat, 2 Apr 2016 10:37:24 -0700
> >> +Subject: [PATCH] build shared library for vchostif
> >> +
> >> +Fixes #149
> >> +
> >> +Signed-off-by: Khem Raj >
> >> +---
> >> + interface/vmcs_host/CMakeLists.txt | 2 +-
> >> + 1 file changed, 1 insertion(+), 1 deletion(-)
> >> +
> >> +diff --git a/interface/vmcs_host/CMakeLists.txt 
> >> b/interface/vmcs_host/CMakeLists.txt
> >> +index 22949a8..f8c2f2f 100755
> >> +--- a/interface/vmcs_host/CMakeLists.txt
> >>  b/interface/vmcs_host/CMakeLists.txt
> >> +@@ -17,7 +17,7 @@ set(VCHOSTIF_SOURCE
> >> + #${VMCS_TARGET}/vmcs_main.c
> >> + #  vc_vchi_haud.c
> >> +
> >> +-add_library(vchostif ${VCHOSTIF_SOURCE})
> >> ++add_library(vchostif SHARED ${VCHOSTIF_SOURCE})
> >> +
> >> + #add_library(bufmanvc_vchi_bufman.c)
> >> +
> >> +--
> >> +2.8.0
> >> +
> >> diff --git a/recipes-graphics/userland/userland_git.bb 
> >>  b/recipes-graphics/userland/userland_git.bb 
> >> 
> >> index efa2128..6ed8fcf 100644
> >> --- a/recipes-graphics/userland/userland_git.bb 
> >> +++ b/recipes-graphics/userland/userland_git.bb 
> >> @@ -33,6 +33,7 @@ SRC_URI = "\
> >>  file://0011-fix-cmake-dependency-race.patch \
> >>  file://0012-Fix-enum-conversion-warnings.patch \
> >>  file://0013-Fix-for-framerate-with-nested-composition.patch \
> >> +file://0014-build-shared-library-for-vchostif.patch \
> >>  file://0015-wl-dispmanx-buffer-wrapping.patch \
> >>  "
> >>  S = "${WORKDIR}/git"
> >> --
> >> 2.8.0
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org 
> >> https://lists.yoctoproject.org/listinfo/yocto 
> >> 
> >
> > This breaks omxplayer compilation when linking omxplayer.bin:
> > [...]/sysroots/x86_64-linux/usr/libexec/arm-custom-linux-gnueabi/gcc/arm-custom-linux-gnueabi/5.3.0/ld:
> > omxplayer.o: undefined reference to symbol
> > 'vc_dispmanx_resource_write_data'
> > [...]/sysroots/raspberrypi2/usr/lib/libvchostif.so: error adding
> > symbols: DSO missing from command line
> 
> Interestingly i dont see this error. Are you using gold ?
> see if this library is on linker cmdline or not
> Using whatever is the default for OE-core in master branch.
> 
>  | arm-custom-linux-gnueabi-g++  -march=armv7ve -marm
>  -mfpu=neon-vfpv4  -mfloat-abi=hard -mcpu=cortex-a7
> --sysroot=/home/build/git/pi2/build/tmp/sysroots/ra
> spberrypi2 -L/home/build/git/pi2/build/tmp/work/cor
> texa7hf-neon-vfpv4-custom-linux-gnueabi/omxplayer/gi
> t-r4/git/ffmpeg_compiled/usr/lib   -
> L/home/build/git/pi2/build/tmp/sysroots/raspberrypi
> 2/lib   -L/home/build/git/pi2/build
> /tmp/sysroots/raspberrypi2/usr/lib
>  -L./ -Lffmpeg_compiled/usr/lib/ -lc -lWFC -lGLESv2
> -lEGL -lbcm_host -lopenmaxil -lfreetype -lz -o omxpl
> ayer.bin linux/XMemUtils.o utils/log.o DynamicDll.o
> utils/PCMRemap.o utils/RegExp.o OMXSubtitleTagSami.o
>  OMXOverlayCodecText.o BitstreamConverter.o linux/RB
> P.o OMXThread.o OMXReader.o OMXStreamInfo.o OMXAudio
> CodecOMX.o OMXCore.o OMXVideo.o OMXAudio.o OMXClock.
> o File.o OMXPlayerVideo.o OMXPlayerAudio.o OMXPlayer
> Subtitles.o SubtitleRenderer.o Unicode.o Srt.o KeyCo
> nfig.o OMXControl.o Keyboard.o omxplayer.o -lvchiq_a
> rm -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec
>  -lavformat -lswscale -lswresample -lpcre
> | 
>

Re: [yocto] [psplash][PATCH 3/3] README: add "Contributing" guideline

2016-04-13 Thread Burton, Ross 
This series is now merged, thanks Richard.

Ross

On 13 April 2016 at 14:57, Richard Leitner 
wrote:

> The "Contributing" guideline section should help people sending their
> patches correctly.
>
> A similar section is available in nearly all
> layers/repositories hosted on yoctoproject.org. Therefore add it also
> the the psplash repository.
>
> Signed-off-by: Richard Leitner 
> ---
>  README | 18 ++
>  1 file changed, 18 insertions(+)
>
> diff --git a/README b/README
> index 86ef6ba..8779a38 100644
> --- a/README
> +++ b/README
> @@ -8,3 +8,21 @@ rotation. Its visual look is configurable by basic source
> changes.
>
>  Also included is a 'client' command utility for sending information to
>  psplash such as boot progress information.
> +
> +Contributing
> +
> +To contribute to this layer you should submit the patches for review to
> the
> +mailing list (yocto@yoctoproject.org).
> +
> +Please refer to
> +http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
> +for some useful guidelines to be followed when submitting patches.
> +
> +Mailing list:
> +https://lists.yoctoproject.org/listinfo/yocto
> +
> +When creating patches, please use something like:
> +git format-patch -M -s --subject-prefix='psplash][PATCH' origin
> +
> +When sending patches, please use something like:
> +git send-email --to yocto@yoctoproject.org 
> --
> 2.1.4
>
> --
> ___
> 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] [meta-raspberrypi][PATCH 2/2] userland: Make vchostif as shared library

2016-04-13 Thread Jonathan Liu 
On Thursday, 14 April 2016, Khem Raj  wrote:

> On Wed, Apr 13, 2016 at 3:05 AM, Jonathan Liu  > wrote:
> > Hi Khem,
> >
> > On 3 April 2016 at 03:59, Khem Raj >
> wrote:
> >> This helps in using this library when building
> >> with PIE binaries
> >>
> >> Signed-off-by: Khem Raj >
> >> ---
> >>  .../0014-build-shared-library-for-vchostif.patch   | 28
> ++
> >>  recipes-graphics/userland/userland_git.bb  |  1 +
> >>  2 files changed, 29 insertions(+)
> >>  create mode 100644
> recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >>
> >> diff --git
> a/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >> new file mode 100644
> >> index 000..ca7cb66
> >> --- /dev/null
> >> +++
> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> >> @@ -0,0 +1,28 @@
> >> +From 4e9aa3fffb458ca4fafd2241c18e9c8008b66ad8 Mon Sep 17 00:00:00 2001
> >> +From: Khem Raj >
> >> +Date: Sat, 2 Apr 2016 10:37:24 -0700
> >> +Subject: [PATCH] build shared library for vchostif
> >> +
> >> +Fixes #149
> >> +
> >> +Signed-off-by: Khem Raj >
> >> +---
> >> + interface/vmcs_host/CMakeLists.txt | 2 +-
> >> + 1 file changed, 1 insertion(+), 1 deletion(-)
> >> +
> >> +diff --git a/interface/vmcs_host/CMakeLists.txt
> b/interface/vmcs_host/CMakeLists.txt
> >> +index 22949a8..f8c2f2f 100755
> >> +--- a/interface/vmcs_host/CMakeLists.txt
> >>  b/interface/vmcs_host/CMakeLists.txt
> >> +@@ -17,7 +17,7 @@ set(VCHOSTIF_SOURCE
> >> + #${VMCS_TARGET}/vmcs_main.c
> >> + #  vc_vchi_haud.c
> >> +
> >> +-add_library(vchostif ${VCHOSTIF_SOURCE})
> >> ++add_library(vchostif SHARED ${VCHOSTIF_SOURCE})
> >> +
> >> + #add_library(bufmanvc_vchi_bufman.c)
> >> +
> >> +--
> >> +2.8.0
> >> +
> >> diff --git a/recipes-graphics/userland/userland_git.bb
> b/recipes-graphics/userland/userland_git.bb
> >> index efa2128..6ed8fcf 100644
> >> --- a/recipes-graphics/userland/userland_git.bb
> >> +++ b/recipes-graphics/userland/userland_git.bb
> >> @@ -33,6 +33,7 @@ SRC_URI = "\
> >>  file://0011-fix-cmake-dependency-race.patch \
> >>  file://0012-Fix-enum-conversion-warnings.patch \
> >>  file://0013-Fix-for-framerate-with-nested-composition.patch \
> >> +file://0014-build-shared-library-for-vchostif.patch \
> >>  file://0015-wl-dispmanx-buffer-wrapping.patch \
> >>  "
> >>  S = "${WORKDIR}/git"
> >> --
> >> 2.8.0
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org 
> >> https://lists.yoctoproject.org/listinfo/yocto
> >
> > This breaks omxplayer compilation when linking omxplayer.bin:
> >
> [...]/sysroots/x86_64-linux/usr/libexec/arm-custom-linux-gnueabi/gcc/arm-custom-linux-gnueabi/5.3.0/ld:
> > omxplayer.o: undefined reference to symbol
> > 'vc_dispmanx_resource_write_data'
> > [...]/sysroots/raspberrypi2/usr/lib/libvchostif.so: error adding
> > symbols: DSO missing from command line
>
> Interestingly i dont see this error. Are you using gold ?
> see if this library is on linker cmdline or not

Using whatever is the default for OE-core in master branch.

 | arm-custom-linux-gnueabi-g++  -march=armv7ve -marm
 -mfpu=neon-vfpv4  -mfloat-abi=hard -mcpu=cortex-a7
--sysroot=/home/build/git/pi2/build/tmp/sysroots/ra
spberrypi2 -L/home/build/git/pi2/build/tmp/work/cor
texa7hf-neon-vfpv4-custom-linux-gnueabi/omxplayer/gi
t-r4/git/ffmpeg_compiled/usr/lib   -
L/home/build/git/pi2/build/tmp/sysroots/raspberrypi
2/lib   -L/home/build/git/pi2/build
/tmp/sysroots/raspberrypi2/usr/lib
 -L./ -Lffmpeg_compiled/usr/lib/ -lc -lWFC -lGLESv2
-lEGL -lbcm_host -lopenmaxil -lfreetype -lz -o omxpl
ayer.bin linux/XMemUtils.o utils/log.o DynamicDll.o
utils/PCMRemap.o utils/RegExp.o OMXSubtitleTagSami.o
 OMXOverlayCodecText.o BitstreamConverter.o linux/RB
P.o OMXThread.o OMXReader.o OMXStreamInfo.o OMXAudio
CodecOMX.o OMXCore.o OMXVideo.o OMXAudio.o OMXClock.
o File.o OMXPlayerVideo.o OMXPlayerAudio.o OMXPlayer
Subtitles.o SubtitleRenderer.o Unicode.o Srt.o KeyCo
nfig.o OMXControl.o Keyboard.o omxplayer.o -lvchiq_a
rm -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec
 -lavformat -lswscale -lswresample -lpcre
|
/home/build/git/pi2/build/tmp/sysroots/x86_64-linux/usr/libexec/arm-custom-linux-gnueabi/gcc/arm-custom-linux-gnueabi/5.3.0/ld:
omxplayer.o: undefined reference to symbol 'vc_dispmanx_resource_write_data'
|
/home/build/git/pi2/build/tmp/sysroots/raspberrypi2/usr/lib/libvchostif.so:
error adding symbols: DSO
 missing from command line
| collect2: error: ld returned 1 exit status
| Makefile:53: recipe for target 'omxplayer.bin' failed
|

Re: [yocto] [meta-raspberrypi][PATCH 2/2] userland: Make vchostif as shared library

2016-04-13 Thread Khem Raj 
On Wed, Apr 13, 2016 at 3:05 AM, Jonathan Liu  wrote:
> Hi Khem,
>
> On 3 April 2016 at 03:59, Khem Raj  wrote:
>> This helps in using this library when building
>> with PIE binaries
>>
>> Signed-off-by: Khem Raj 
>> ---
>>  .../0014-build-shared-library-for-vchostif.patch   | 28 
>> ++
>>  recipes-graphics/userland/userland_git.bb  |  1 +
>>  2 files changed, 29 insertions(+)
>>  create mode 100644 
>> recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>>
>> diff --git 
>> a/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>>  
>> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>> new file mode 100644
>> index 000..ca7cb66
>> --- /dev/null
>> +++ 
>> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>> @@ -0,0 +1,28 @@
>> +From 4e9aa3fffb458ca4fafd2241c18e9c8008b66ad8 Mon Sep 17 00:00:00 2001
>> +From: Khem Raj 
>> +Date: Sat, 2 Apr 2016 10:37:24 -0700
>> +Subject: [PATCH] build shared library for vchostif
>> +
>> +Fixes #149
>> +
>> +Signed-off-by: Khem Raj 
>> +---
>> + interface/vmcs_host/CMakeLists.txt | 2 +-
>> + 1 file changed, 1 insertion(+), 1 deletion(-)
>> +
>> +diff --git a/interface/vmcs_host/CMakeLists.txt 
>> b/interface/vmcs_host/CMakeLists.txt
>> +index 22949a8..f8c2f2f 100755
>> +--- a/interface/vmcs_host/CMakeLists.txt
>>  b/interface/vmcs_host/CMakeLists.txt
>> +@@ -17,7 +17,7 @@ set(VCHOSTIF_SOURCE
>> + #${VMCS_TARGET}/vmcs_main.c
>> + #  vc_vchi_haud.c
>> +
>> +-add_library(vchostif ${VCHOSTIF_SOURCE})
>> ++add_library(vchostif SHARED ${VCHOSTIF_SOURCE})
>> +
>> + #add_library(bufmanvc_vchi_bufman.c)
>> +
>> +--
>> +2.8.0
>> +
>> diff --git a/recipes-graphics/userland/userland_git.bb 
>> b/recipes-graphics/userland/userland_git.bb
>> index efa2128..6ed8fcf 100644
>> --- a/recipes-graphics/userland/userland_git.bb
>> +++ b/recipes-graphics/userland/userland_git.bb
>> @@ -33,6 +33,7 @@ SRC_URI = "\
>>  file://0011-fix-cmake-dependency-race.patch \
>>  file://0012-Fix-enum-conversion-warnings.patch \
>>  file://0013-Fix-for-framerate-with-nested-composition.patch \
>> +file://0014-build-shared-library-for-vchostif.patch \
>>  file://0015-wl-dispmanx-buffer-wrapping.patch \
>>  "
>>  S = "${WORKDIR}/git"
>> --
>> 2.8.0
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> This breaks omxplayer compilation when linking omxplayer.bin:
> [...]/sysroots/x86_64-linux/usr/libexec/arm-custom-linux-gnueabi/gcc/arm-custom-linux-gnueabi/5.3.0/ld:
> omxplayer.o: undefined reference to symbol
> 'vc_dispmanx_resource_write_data'
> [...]/sysroots/raspberrypi2/usr/lib/libvchostif.so: error adding
> symbols: DSO missing from command line

Interestingly i dont see this error. Are you using gold ?
see if this library is on linker cmdline or not

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

[yocto] [psplash][PATCH 2/3] add initial .gitignore

2016-04-13 Thread Richard Leitner 
This initial version of .gitignore contains all files created during a
build.

Signed-off-by: Richard Leitner 
---
 .gitignore | 20 
 1 file changed, 20 insertions(+)
 create mode 100644 .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..7cf14ed
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,20 @@
+configure
+config.h
+config.h.in
+config.log
+config.status
+config.guess
+config.sub
+depcomp
+Makefile
+Makefile.in
+install-sh
+missing
+aclocal.m4
+autom4te.cache/
+.deps/
+*.o
+
+psplash
+psplash-write
+stamp-h1
-- 
2.1.4

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

[yocto] [psplash][PATCH 3/3] README: add "Contributing" guideline

2016-04-13 Thread Richard Leitner 
The "Contributing" guideline section should help people sending their
patches correctly.

A similar section is available in nearly all
layers/repositories hosted on yoctoproject.org. Therefore add it also
the the psplash repository.

Signed-off-by: Richard Leitner 
---
 README | 18 ++
 1 file changed, 18 insertions(+)

diff --git a/README b/README
index 86ef6ba..8779a38 100644
--- a/README
+++ b/README
@@ -8,3 +8,21 @@ rotation. Its visual look is configurable by basic source 
changes.
 
 Also included is a 'client' command utility for sending information to
 psplash such as boot progress information.
+
+Contributing
+
+To contribute to this layer you should submit the patches for review to the
+mailing list (yocto@yoctoproject.org).
+
+Please refer to
+http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
+for some useful guidelines to be followed when submitting patches.
+
+Mailing list:
+https://lists.yoctoproject.org/listinfo/yocto
+
+When creating patches, please use something like:
+git format-patch -M -s --subject-prefix='psplash][PATCH' origin
+
+When sending patches, please use something like:
+git send-email --to yocto@yoctoproject.org 
-- 
2.1.4

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

[yocto] [psplash][PATCH 1/3] AUTHORS: add list of git commit authors

2016-04-13 Thread Richard Leitner 
Added an initial AUTHORS list in alphabetical order, created with
following commandline:
git log --format='%aN <%aE>' | sort -u

Signed-off-by: Richard Leitner 
---
 AUTHORS | 13 +
 1 file changed, 13 insertions(+)

diff --git a/AUTHORS b/AUTHORS
index e69de29..953d867 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -0,0 +1,13 @@
+List of contributors (in alphabetical order):
+
+Aws Ismail 
+Juro Bystricky 
+Khem Raj 
+Matthew Allum 
+Olaf Mandel 
+Richard Purdie 
+Rob Bradford 
+Robert Bragg 
+Ross Burton 
+Samuel Ortiz 
+Tomas Frydrych 
-- 
2.1.4

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

[yocto] [meta-cgl][PATCH] linux-yocto: Update .bbappend recipe version

2016-04-13 Thread Adrian Dudau 
Signed-off-by: Adrian Dudau 
---
 .../linux/{linux-yocto_3.14.bbappend => linux-yocto_4.%.bbappend} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename meta-cgl-common/recipes-kernel/linux/{linux-yocto_3.14.bbappend => 
linux-yocto_4.%.bbappend} (100%)

diff --git a/meta-cgl-common/recipes-kernel/linux/linux-yocto_3.14.bbappend 
b/meta-cgl-common/recipes-kernel/linux/linux-yocto_4.%.bbappend
similarity index 100%
rename from meta-cgl-common/recipes-kernel/linux/linux-yocto_3.14.bbappend
rename to meta-cgl-common/recipes-kernel/linux/linux-yocto_4.%.bbappend
-- 
1.9.1

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

Re: [yocto] [meta-raspberrypi][PATCH 2/2] userland: Make vchostif as shared library

2016-04-13 Thread Jonathan Liu 
Hi Khem,

On 3 April 2016 at 03:59, Khem Raj  wrote:
> This helps in using this library when building
> with PIE binaries
>
> Signed-off-by: Khem Raj 
> ---
>  .../0014-build-shared-library-for-vchostif.patch   | 28 
> ++
>  recipes-graphics/userland/userland_git.bb  |  1 +
>  2 files changed, 29 insertions(+)
>  create mode 100644 
> recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>
> diff --git 
> a/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
>  
> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> new file mode 100644
> index 000..ca7cb66
> --- /dev/null
> +++ 
> b/recipes-graphics/userland/userland/0014-build-shared-library-for-vchostif.patch
> @@ -0,0 +1,28 @@
> +From 4e9aa3fffb458ca4fafd2241c18e9c8008b66ad8 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Sat, 2 Apr 2016 10:37:24 -0700
> +Subject: [PATCH] build shared library for vchostif
> +
> +Fixes #149
> +
> +Signed-off-by: Khem Raj 
> +---
> + interface/vmcs_host/CMakeLists.txt | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/interface/vmcs_host/CMakeLists.txt 
> b/interface/vmcs_host/CMakeLists.txt
> +index 22949a8..f8c2f2f 100755
> +--- a/interface/vmcs_host/CMakeLists.txt
>  b/interface/vmcs_host/CMakeLists.txt
> +@@ -17,7 +17,7 @@ set(VCHOSTIF_SOURCE
> + #${VMCS_TARGET}/vmcs_main.c
> + #  vc_vchi_haud.c
> +
> +-add_library(vchostif ${VCHOSTIF_SOURCE})
> ++add_library(vchostif SHARED ${VCHOSTIF_SOURCE})
> +
> + #add_library(bufmanvc_vchi_bufman.c)
> +
> +--
> +2.8.0
> +
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index efa2128..6ed8fcf 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -33,6 +33,7 @@ SRC_URI = "\
>  file://0011-fix-cmake-dependency-race.patch \
>  file://0012-Fix-enum-conversion-warnings.patch \
>  file://0013-Fix-for-framerate-with-nested-composition.patch \
> +file://0014-build-shared-library-for-vchostif.patch \
>  file://0015-wl-dispmanx-buffer-wrapping.patch \
>  "
>  S = "${WORKDIR}/git"
> --
> 2.8.0
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

This breaks omxplayer compilation when linking omxplayer.bin:
[...]/sysroots/x86_64-linux/usr/libexec/arm-custom-linux-gnueabi/gcc/arm-custom-linux-gnueabi/5.3.0/ld:
omxplayer.o: undefined reference to symbol
'vc_dispmanx_resource_write_data'
[...]/sysroots/raspberrypi2/usr/lib/libvchostif.so: error adding
symbols: DSO missing from command line

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

Re: [yocto] [PATCH 1/1] userland: In case of wayland configuration build needs wayland-native

2016-04-13 Thread Jonathan Liu 
Hi Andrei,

This is breaking non-Wayland builds... the second value in the
PACKAGECONFIG is the configure arguments for when the PACKAGECONFIG is
disabled.

I have sent a patch to fix it.

Regards,
Jonathan

On 13 April 2016 at 13:12, Andrei Gherzan  wrote:
> On Fri, Apr 01, 2016 at 01:37:11PM +0200, Andrei Gherzan wrote:
>> Building wayland support requires availability of wayland-scanner to avoid
>> build errors like:
>>
>> | /bin/sh:
>> | 
>> /home/andrei/work/yocto/build-rpi-master/tmp/sysroots/x86_64-linux/usr/bin/wayland-scanner:
>> | No such file or directory
>>
>> Signed-off-by: Andrei Gherzan 
>> ---
>>  recipes-graphics/userland/userland_git.bb | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/recipes-graphics/userland/userland_git.bb 
>> b/recipes-graphics/userland/userland_git.bb
>> index ca9123e..536c3ec 100644
>> --- a/recipes-graphics/userland/userland_git.bb
>> +++ b/recipes-graphics/userland/userland_git.bb
>> @@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
>> -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
>>
>>  PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
>> 'wayland', '', d)}"
>>
>> -PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
>> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland"
>> +PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
>> -DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
>>
>>  CFLAGS_append = " -fPIC"
>>
>> --
>> 2.7.4
>>
>
> Merged to master.
>
> --
> Andrei Gherzan
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] userland: fix wayland PACKAGECONFIG

2016-04-13 Thread Jonathan Liu 
The wayland-native dependency was not added correctly.

Signed-off-by: Jonathan Liu 
---
 recipes-graphics/userland/userland_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index ef06b12..2fdfeed 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -45,7 +45,7 @@ EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release 
-DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-a
 
 PACKAGECONFIG ?= "${@bb.utils.contains('DISTRO_FEATURES', 'wayland', 
'wayland', '', d)}"
 
-PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
-DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,wayland-native,wayland"
+PACKAGECONFIG[wayland] = "-DBUILD_WAYLAND=TRUE 
-DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner,,wayland
 wayland-native"
 
 CFLAGS_append = " -fPIC"
 
-- 
2.7.4

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

Re: [yocto] [meta-selinux][PATCH 2/3] Integrate selinux-config into refpolicy_common.

2016-04-13 Thread wenzong fan 

On 04/12/2016 10:05 PM, Joe MacDonald wrote:

Philip / Wenzong,

[Re: [yocto] [meta-selinux][PATCH 2/3] Integrate selinux-config into 
refpolicy_common.] On 16.04.12 (Tue 13:54) wenzong fan wrote:


On 04/12/2016 11:55 AM, Philip Tricca wrote:

Hello,

On 04/11/2016 05:54 AM, Joe MacDonald wrote:

This causes do_populate_sysroot error if build two or more types of
refpolicy:

$ bitbake refpolicy-minimum && bitbake refpolicy-mls

ERROR: refpolicy-mls-git-r0 do_populate_sysroot: The recipe refpolicy-mls is
trying to install files into a shared area when those files already exist.
Those files and their manifest location are:


I think this was always the intent with the series Philip submitted last
week (for reference, the thread is
https://www.mail-archive.com/yocto@yoctoproject.org/msg28530.html).
Isn't this (part of) the expected behaviour of the virtual provider
mechanism?


This is the question I think we need to figure out. My understanding
(quite possibly wrong) is that the virtual provider stuff would prevent
the installation of more than one provider. I hadn't considered the
implications for the sysroot.

Is the ability to install multiple providers in the sysroot expected? I
imagine that this problem must have been solved before in another
package with virtual providers that install the same file. I'm happy to
doing some digging here but if anyone knows of a good example I'd
appreciate a pointer.


We did discuss what it would mean to be trying out multiple
policies on a system at the same time and at the time it seemed like the
"just works" angle was more important than "buffet style" when it came
to providing policy on the image.


I guess the thing I like the most about setting the policy package up as
a virtual package is the ability to select the policy type as a distro
config. The virtual provider seemed like a natural fit as it's a pattern
that similar packages (kernel etc) use extensively.


It might be worth considering extending the changes to only do some
install steps at, say, do_rootfs but I don't know if that even makes
sense, this is really the first I've thought of it.  I think Philip's
original changes are good, though, for our maintenance and for clients
of meta-selinux.


There may be a middle ground and I think that would be leaving the
configuration file as a separate package. Personally I liked the idea of
rolling the config file into the policy package as it was always a bit
awkward requiring coordination of some variables across the policy and
the config package which made it a bit brittle.

Wenzong: A few questions: What's your use case for building multiple
policy packages? Would you suggest just backing out the removal of the
config package or the whole virtual provider thing?


Hi Philip,

The virtual provider is OK, just restore the config package is the simplest
ways for fixing such issue I think.

My use cases include:
a. update refpolicy and build each type to make sure patch/build/install
work;


That's not necessarily an argument against the change ...


b. run world build with meta-selinux layer.


... but I think this is.  Or, rather, I think what we have now makes more
sense from an end-user perspective, that your image wouldn't have more
than a single policy installed at a time and that if you tried to install
multiple policies for nearly everyone this represents a mistake and
undesirable behaviour so warnings / errors are appropriate.

But if this is breaking world builds with yocto+meta-selinux, that's
something I'd like to repair.  Though I'm surprised that what we have
right now would break the world builds.  Philip / Wenzong / Mark:  Do you
have publicly-accessible world builds right now?  I don't and I don't have
world builds for yocto+meta-selinux on my autobuilder, but I'll go set one
up if you don't have one.


Oh, it's my fault. I can't reproduce the issue with a fresh build now, 
it must be I had been run refpolicy-* build manually :(


I don't want to install multiple policies to target as well, so I have 
no objection now.


Thanks all for your patience.

Wenzong



-J.



Thanks
Wenzong



Thanks,
Philip


/buildarea/raid5/wfan/yocto/builds/selinux_sysvinit/tmp/sysroots/qemux86-64/etc/selinux/sepolgen.conf
  Matched in manifest-qemux86-64-refpolicy-minimum.populate_sysroot

/buildarea/raid5/wfan/yocto/builds/selinux_sysvinit/tmp/sysroots/qemux86-64/etc/selinux/config
  Matched in manifest-qemux86-64-refpolicy-minimum.populate_sysroot

/buildarea/raid5/wfan/yocto/builds/selinux_sysvinit/tmp/sysroots/qemux86-64/sysroot-providers/virtual_refpolicy
  Matched in manifest-qemux86-64-refpolicy-minimum.populate_sysroot
Please verify which recipe should provide the above files.

Philip,

Can you consider to withdraw the integration?

Thanks
Wenzong

On 04/04/2016 08:21 AM, Philip Tricca wrote:

With the virutal package there's no need for a separate recipe to build
the config. This can be generated and included as part of the policy
package.