[yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix sdimg generation
Track changes in OE-core variable names - needed to be able to
build an rpi-sdimg image file.
Signed-off-by: Gary Thomas
---
classes/sdcard_image-rpi.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 388398b..ad245f3 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -47,7 +47,7 @@ IMAGE_ROOTFS_ALIGNMENT = "4096"
# Use an uncompressed ext3 by default as rootfs
SDIMG_ROOTFS_TYPE ?= "ext3"
-SDIMG_ROOTFS = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
+SDIMG_ROOTFS = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
IMAGE_DEPENDS_rpi-sdimg = " \
parted-native \
@@ -59,7 +59,7 @@ IMAGE_DEPENDS_rpi-sdimg = " \
"
# SD card image name
-SDIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
+SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
# Compression method to apply to SDIMG after it has been created. Supported
# compression formats are "gzip", "bzip2" or "xz". The original .rpi-sdimg file
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix sdimg generation
On Wed, Sep 21, 2016 at 9:26 AM, Gary Thomas wrote:
> Track changes in OE-core variable names - needed to be able to
> build an rpi-sdimg image file.
>
> Signed-off-by: Gary Thomas
> ---
> classes/sdcard_image-rpi.bbclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/classes/sdcard_image-rpi.bbclass
> b/classes/sdcard_image-rpi.bbclass
> index 388398b..ad245f3 100644
> --- a/classes/sdcard_image-rpi.bbclass
> +++ b/classes/sdcard_image-rpi.bbclass
> @@ -47,7 +47,7 @@ IMAGE_ROOTFS_ALIGNMENT = "4096"
>
> # Use an uncompressed ext3 by default as rootfs
> SDIMG_ROOTFS_TYPE ?= "ext3"
> -SDIMG_ROOTFS =
> "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
> +SDIMG_ROOTFS = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
>
> IMAGE_DEPENDS_rpi-sdimg = " \
> parted-native \
> @@ -59,7 +59,7 @@ IMAGE_DEPENDS_rpi-sdimg = " \
> "
>
> # SD card image name
> -SDIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
> +SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
>
> # Compression method to apply to SDIMG after it has been created. Supported
> # compression formats are "gzip", "bzip2" or "xz". The original .rpi-sdimg
> file
> --
> 2.7.4
>
Isn't that the same as [1]?
[1] https://lists.yoctoproject.org/pipermail/yocto/2016-September/031961.html
Andreas
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix sdimg generation
On 2016-09-21 09:54, Andreas Müller wrote:
On Wed, Sep 21, 2016 at 9:26 AM, Gary Thomas wrote:
Track changes in OE-core variable names - needed to be able to
build an rpi-sdimg image file.
Signed-off-by: Gary Thomas
---
classes/sdcard_image-rpi.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 388398b..ad245f3 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -47,7 +47,7 @@ IMAGE_ROOTFS_ALIGNMENT = "4096"
# Use an uncompressed ext3 by default as rootfs
SDIMG_ROOTFS_TYPE ?= "ext3"
-SDIMG_ROOTFS = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
+SDIMG_ROOTFS = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
IMAGE_DEPENDS_rpi-sdimg = " \
parted-native \
@@ -59,7 +59,7 @@ IMAGE_DEPENDS_rpi-sdimg = " \
"
# SD card image name
-SDIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
+SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
# Compression method to apply to SDIMG after it has been created. Supported
# compression formats are "gzip", "bzip2" or "xz". The original .rpi-sdimg file
--
2.7.4
Isn't that the same as [1]?
[1] https://lists.yoctoproject.org/pipermail/yocto/2016-September/031961.html
Yes, it looks like it is, but that one is still not in master :-(
so I thought I'd give it a nudge!
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix sdimg generation
On Wed, Sep 21, 2016 at 9:58 AM, Gary Thomas wrote:
> On 2016-09-21 09:54, Andreas Müller wrote:
>>
>> On Wed, Sep 21, 2016 at 9:26 AM, Gary Thomas wrote:
>>>
>>> Track changes in OE-core variable names - needed to be able to
>>> build an rpi-sdimg image file.
>>>
>>> Signed-off-by: Gary Thomas
>>> ---
>>> classes/sdcard_image-rpi.bbclass | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/classes/sdcard_image-rpi.bbclass
>>> b/classes/sdcard_image-rpi.bbclass
>>> index 388398b..ad245f3 100644
>>> --- a/classes/sdcard_image-rpi.bbclass
>>> +++ b/classes/sdcard_image-rpi.bbclass
>>> @@ -47,7 +47,7 @@ IMAGE_ROOTFS_ALIGNMENT = "4096"
>>>
>>> # Use an uncompressed ext3 by default as rootfs
>>> SDIMG_ROOTFS_TYPE ?= "ext3"
>>> -SDIMG_ROOTFS =
>>> "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
>>> +SDIMG_ROOTFS =
>>> "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.${SDIMG_ROOTFS_TYPE}"
>>>
>>> IMAGE_DEPENDS_rpi-sdimg = " \
>>> parted-native \
>>> @@ -59,7 +59,7 @@ IMAGE_DEPENDS_rpi-sdimg = " \
>>> "
>>>
>>> # SD card image name
>>> -SDIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.rpi-sdimg"
>>> +SDIMG = "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
>>>
>>> # Compression method to apply to SDIMG after it has been created.
>>> Supported
>>> # compression formats are "gzip", "bzip2" or "xz". The original
>>> .rpi-sdimg file
>>> --
>>> 2.7.4
>>>
>> Isn't that the same as [1]?
>>
>> [1]
>> https://lists.yoctoproject.org/pipermail/yocto/2016-September/031961.html
>
>
> Yes, it looks like it is, but that one is still not in master :-(
> so I thought I'd give it a nudge!
>
Yes - there are many things missing in master e.g VC4...
Andreas
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/1] bcm2835: Compile examples correct LDFLAGS to avoid HASH errors
On Fri, Sep 16, 2016 at 05:54:36PM +0100, Andrei Gherzan wrote:
> ERROR: bcm2835-1.50-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/spi'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/event'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/gpio'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/i2c'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/blink'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/spin'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/input'
> No GNU_HASH in the elf binary:
> 'build-rpi-master/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/bcm2835/1.50-r0/packages-split/bcm2835-tests/usr/lib/bcm2835/pwm'
> [ldflags]
>
> Signed-off-by: Andrei Gherzan
> ---
> recipes-devtools/bcm2835/bcm2835_1.50.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-devtools/bcm2835/bcm2835_1.50.bb
> b/recipes-devtools/bcm2835/bcm2835_1.50.bb
> index 634dac8..9cf6f48 100644
> --- a/recipes-devtools/bcm2835/bcm2835_1.50.bb
> +++ b/recipes-devtools/bcm2835/bcm2835_1.50.bb
> @@ -21,7 +21,7 @@ do_compile_append() {
> # Now compiling the examples provided by the package
> mkdir -p ${B}/examples
> for file in `ls ${S}/examples`; do
> -${CC} ${S}/examples/${file}/${file}.c -o ${B}/examples/${file}
> -Bstatic -L${B}/src -lbcm2835 -I${S}/src
> +${CC} ${LDFLAGS} ${S}/examples/${file}/${file}.c -o
> ${B}/examples/${file} -Bstatic -L${B}/src -lbcm2835 -I${S}/src
> done
> }
>
> --
> 2.9.3
>
Merged to master.
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 1/3] wiringpi: Update to 2.32
On Fri, Sep 16, 2016 at 05:34:35PM +0100, Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan
> ---
> recipes-devtools/wiringPi/wiringpi_git.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-devtools/wiringPi/wiringpi_git.bb
> b/recipes-devtools/wiringPi/wiringpi_git.bb
> index 9d2206b..f2cacd3 100644
> --- a/recipes-devtools/wiringPi/wiringpi_git.bb
> +++ b/recipes-devtools/wiringPi/wiringpi_git.bb
> @@ -4,8 +4,8 @@ SECTION = "devel/libs"
> LICENSE = "LGPLv3+"
> LIC_FILES_CHKSUM =
> "file://COPYING.LESSER;md5=e6a600fd5e1d9cbde2d983680233ad02"
>
> -# tag 2.29
> -SRCREV = "d79506694d7ba1c3da865d095238289d6175057d"
> +# tag 2.32
> +SRCREV = "b0a60c3302973ca1878d149d61f2f612c8f27fac"
>
> S = "${WORKDIR}/git"
>
> --
> 2.9.3
>
Merged to master.
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA Test Report for Yocto Project 2.2 M3 rc1
Hi Here is the report for QA Cycle on 2.2 M3 rc1 Full Report : https://wiki.yoctoproject.org/wiki/WW38_-_2016-09-09_-_Full_Test_Cycle_2.2_M3.rc1 Summary There were 15 ne bugs found on this test cycle, 3 of them High that were triaged on time and now all of them have the fixes under review. There were a little increase on Performance times for kernel building the other measurements were stable with exception of roofs that was not giving correct measurements due a bug on qemuboot. Bugs *New High and M+ - 10274 - Missing build-appliance image for 2.2 M3 rc1 - High [1] - 10275 - Missing i686 toolchain sdk for 2.2 M3 rc1 - High [2] - 10285 - qemuboot.conf has the incorrect values for image_name and qb_default_kernel - High [3] - 10262 - SD card not being recognized when trying to install the image - Medium+ [4] - 10272 - Wav and Ogg files are not able to play - Medium+ [5] - 10301 - Update yocto-bsp script for kernel 4.8 - Medium+ [6] - 10265 - nativesdk-qemu-helper: runqemu in sdk should check OECORE_NATIVE_SYSROOT and OECORE_TARGET_SYSROOT - Medium+ [7] Full List of bugs : https://wiki.yoctoproject.org/wiki/WW38_-_2016-09-09_-_Full_Test_Cycle_2.2_M3.rc1#New_and_notable_issues_Found_during_QA_Test_.26_Community *Old New High and M+ - 9285 - Failed to build gobject-introspection for qemumips64 on i686 hosts - Medium+ [8] - 9287 - Failed to build nativesdk-glibc for qemumips and qemumips64 on Fedora 23 i686 - Medium+ [9] *Old Medium Low Full list of bugs: https://wiki.yoctoproject.org/wiki/WW38_-_2016-09-09_-_Full_Test_Cycle_2.2_M3.rc1#Other_Bugs_found_during_QA_Test_.28NOT_NEW.29 Performance -core-image-sato rm-work was in the normal average times on Fedora and Ubuntu machines -Kernel has little increase on average times about 4% on Ubuntu and 7% on Fedora [10] -core-image-sato rootfs was giving incorrect measurements due bug 10285 -Full list of charts [11] Links 1- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10274 2- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10275 3- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10285 4- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10262 5- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10272 6- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10301 7- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10265 8- https://bugzilla.yoctoproject.org/show_bug.cgi?id=9285 9- https://bugzilla.yoctoproject.org/show_bug.cgi?id=9287 10- https://wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-virtual-kernel.html 11- https://wiki.yoctoproject.org/charts/perf_milestone_GDC/performance_test.html Regards, José -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] FrameBuffer support
Hi,
I'm trying to make framebuffers work on imx6(ul) using yocto.
I suppose I need to make changes in the following:
1) Kernel modules
2) Device tree
3) U-Boot bootargs
I've build my kernel with the following modules
FB_TFT=y
CONFIG_FB_TFT_ILI9325=m
I added the following to the device tree
/ {
itdb28 {
compatible = "ilitek,ili9325";
status = "okay";
rotate = <0>;
bgr;
buswidth = <8>;
reset-gpios = <&gpio3 23 0>;
dc-gpios = <&gpio3 5 0>;
cs-gpios = <&gpio3 1 0>;
wr-gpios = <&gpio3 0 0>;
db-gpios = <&gpio3 7 0>,
<&gpio3 8 0>,
<&gpio3 9 0>,
<&gpio3 10 0>,
<&gpio3 11 0>,
<&gpio3 15 0>,
<&gpio3 16 0>,
<&gpio3 17 0>;
/* LED pin drives backlight directly. Use transistor (50mA) */
/* led-gpios = <&gpio 4 1>; */
debug = <7>;
};
framebuffer {
compatible = "simple-framebuffer";
reg = <0x1d385000 (240 * 320 * 2)>;
width = <240>;
height = <320>;
stride = <(240 * 2)>;
format = "r5g6b5";
};
};
When I boot, I get the following error:
Error opening /dev/fb0: No such file or directory
Did I forget something or is there a decent manual available?
Thanks!
Jonathan.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ptest-runner][PATCH] Added error coverage to support when launching child process fails.
From: Edwin Plauchu
[YOCTO #9752]
Signed-off-by: Edwin Plauchu
---
utils.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/utils.c b/utils.c
index 6991af1..2ebfb04 100644
--- a/utils.c
+++ b/utils.c
@@ -249,7 +249,7 @@ run_child(char *run_ptest, int fd_stdout, int fd_stderr)
dup2(fd_stderr, STDERR_FILENO);
execv(run_ptest, argv);
- exit(0);
+ exit(1);
}
static inline int
@@ -336,6 +336,7 @@ run_ptests(struct ptest_list *head, int timeout, const char
*progname,
child = fork();
if (child == -1) {
+ fprintf(stderr, "ERROR: Fork fatal\n");
rc = -1;
break;
} else if (child == 0) {
@@ -351,6 +352,7 @@ run_ptests(struct ptest_list *head, int timeout, const char
*progname,
status = wait_child(ptest_dir, p->run_ptest,
child,
timeout, fds, fps);
if (status)
+ fprintf(stderr, "ERROR: Program child
error\n");
rc += 1;
fprintf(fp, "END: %s\n", ptest_dir);
--
2.9.3
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FrameBuffer support
Hi Jonathan,
On Mon, Sep 19, 2016 at 11:01 AM, Jonathan Vervaeke
wrote:
> Hi,
>
>
>
> I'm trying to make framebuffers work on imx6(ul) using yocto.
>
>
>
> I suppose I need to make changes in the following:
>
> 1) Kernel modules
>
> 2) Device tree
>
> 3) U-Boot bootargs
>
>
>
> I've build my kernel with the following modules
>
>
>
>
> FB_TFT=y
>
> CONFIG_FB_TFT_ILI9325=m
>
>
>
>
> I added the following to the device tree
>
>
>
>
>
> / {
> itdb28 {
> compatible = "ilitek,ili9325";
> status = "okay";
>
> rotate = <0>;
> bgr;
> buswidth = <8>;
> reset-gpios = <&gpio3 23 0>;
> dc-gpios = <&gpio3 5 0>;
> cs-gpios = <&gpio3 1 0>;
> wr-gpios = <&gpio3 0 0>;
> db-gpios = <&gpio3 7 0>,
><&gpio3 8 0>,
><&gpio3 9 0>,
><&gpio3 10 0>,
><&gpio3 11 0>,
><&gpio3 15 0>,
><&gpio3 16 0>,
><&gpio3 17 0>;
> /* LED pin drives backlight directly. Use transistor (50mA) */
> /* led-gpios = <&gpio 4 1>; */
> debug = <7>;
> };
>
>
> framebuffer {
> compatible = "simple-framebuffer";
> reg = <0x1d385000 (240 * 320 * 2)>;
> width = <240>;
> height = <320>;
> stride = <(240 * 2)>;
> format = "r5g6b5";
> };
> };
>
>
>
>
> When I boot, I get the following error:
>
>
>
>
>
> Error opening /dev/fb0: No such file or directory
>
>
>
>
> Did I forget something or is there a decent manual available?
>
> Thanks!
>
> Jonathan.
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
Looks to me like the driver hasn't loaded due to error or maybe
compatible string mismatch. Have you included the simple framebuffer
in the kernel configuration? Is there anything in dmesg?
Cheers, Martin.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH v4 00/12] Support for VC4 graphics driver
On Thu, Jul 21, 2016 at 08:32:05PM +0800, Herve Jourdain wrote:
> v4 series:
> a. rebased
> b. Upstream-Status added to the patch to the VC4 driver (needed only for
> kernel 4.4, accepted upstream in 4.7)
>
> v3 series:
> a. patch rebased
> b. new revision of kernel, to get a version of the VC4 graphics driver that
> handles render nodes
> c. patch to the VC4 driver to enable proper working of the render nodes (need
> to add authorization for IOCTLs)
>
> v2 series:
> a. Fix the 4.4.10 kernel revision
> b. Effectively add vc4-kms-v3d overlay to the list of overlays to build
> (forgotten previously)
> c. Make the parameter to the v4c-kms-v3d overlay configurable
> d. Add default values for the cma parameter to the v4c-kms-v3d overlay,
> depending on the board (and the memory it has)
>
> This patch series enables the support for the VC4 graphics driver from Eric
> Anholt.
> There was a previous patch series by Javier Martinez Canillas, but it
> required use of a different kernel.
> VC4 is now supported in the raspberrypi official kernel, at least for 4.4.9+.
> The support in 4.1 exists, but it is NOT STABLE, so it has been deemed
> unreasonable to support VC4 with 4.1 kernels.
>
> THEREFORE, VC4 graphics is supported ONLY for kernel versions 4.4.9 and later.
>
> This patch series proposes to support VC4 by only adding 'vc4graphics' to
> MACHINE_FEATURES, for raspberrypi. If this is set, it will trigger all the
> necessary configuration/changes to use the VC4 driver, including
> mesa/wayland/weston currently, and adding the overlay required.
> In order for this series to work, some previous patches are needed (support
> for .dtbo, and fix of the mesa packaging when there is no DRI driver).
> The memory reserved for the VC4 driver has default values depending on the
> version of the board used, but it can be configured by setting VC4_CMA_SIZE
> to a value supported by the overlay ('cma-256', 'cma-192', 'cma-128',
> 'cma-96', 'cma-64').
> 'cma-256' is the recommended value, but it might not be possible on boards
> with 512MB or DRAM, or less...
> 'cma-64' is known to not being able to support FHD/1080p.
>
> It was tested with wayland/weston, without the support for X11.
>
> This patch series depends on two other patch series previously posted, that
> enable the support for .dtbo overlay files.
>
> Herve Jourdain (12):
> rpi-default-providers.inc: change default providers to support
> vc4graphics
> rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics
> raspberrypi.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support
> vc4graphics
> rpi-config_git.bb: add v4c overlay to config.txt to support
> vc4graphics
> wayland/weston_%.bbappend: modify configuration options to support
> vc4graphics
> weston/weston_%.bbappend: modify configuration options to support
> vc4graphics
> mesa_%.bbappend: new file to add the correct configuration options to
> support vc4graphics
> linux-rpi.inc: add the configuration options required to support
> vc4graphics
> linux-raspberrypi-4.4: add patch to enable proper operation of
> renderD128 device
>
> conf/machine/include/rpi-base.inc | 1 +
> conf/machine/include/rpi-default-providers.inc | 8 +++---
> conf/machine/raspberrypi.conf | 2 ++
> conf/machine/raspberrypi0.conf | 2 ++
> conf/machine/raspberrypi2.conf | 2 ++
> conf/machine/raspberrypi3.conf | 2 ++
> recipes-bsp/bootfiles/rpi-config_git.bb| 10 +++-
> recipes-graphics/mesa/mesa_%.bbappend | 4 +++
> recipes-graphics/wayland/weston_%.bbappend | 6 ++---
> recipes-graphics/weston/weston_%.bbappend | 13 +-
> .../0002-vc4-ioctl-rendering-allow.patch | 29
> ++
> recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
> recipes-kernel/linux/linux-rpi.inc | 10
> 13 files changed, 75 insertions(+), 15 deletions(-)
> create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
> create mode 100644
> recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
>
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
The entire patch set was merged to master. Thanks.
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH v6 0/4] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+
On Thu, Jul 21, 2016 at 06:00:35AM +0800, Herve Jourdain wrote: > v6: rebased > > v5: modifications after more review > * Added an Upstream-Status to the kernel patch > * Only one instance of KERNEL_DEVICETREE defined (with the new .dtbo syntax) > * Modification of the KERNEL_DEVICETREE is done in > linux-raspberry-base.bbclass, based on the kernel version > > v4: rebased > For kernels 4.4.9+, the behavior for the device tree overlays loading has > been modified on RaspberryPi. > For overlays, it loads .dtbo files, not .dtb anymore. > Also, it does not check for -overlay extension, so the name of the overlay > that is placed in the "overlays" directory must be .dtbo, > instead of -overlay.dtb. > > This patch addresses the issue for kernels 4.4+, while keeping the same > behavior for older kernels. > This patch must be used in conjunction with another patch to > meta/recipes-kernel/linux-dtb.inc, which will allow the processing of .dtbo > files for overlays, instead of only .dtb like before. > > .dtb are still in use, but only for the "real" device trees (not the > overlays). > > Herve Jourdain (4): > linux-raspberrypi_4.4.bb: support for .dtbo files for dtb overlays > rpi-base.inc: support for .dtbo files for dtb overlays > linux-raspberrypi-base.bbclass: support for .dtbo files for dtb > overlays > sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays > > classes/linux-raspberrypi-base.bbclass | 19 ++ > classes/sdcard_image-rpi.bbclass | 15 +--- > conf/machine/include/rpi-base.inc | 30 +++ > .../0001-fix-dtbo-rules.patch | 44 > ++ > recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 + > 5 files changed, 81 insertions(+), 28 deletions(-) > create mode 100644 > recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch > > -- > 2.7.4 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto The entire patchset was merged to master. Thanks. -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Cortex-M4 build support
You can also have a look at the Zephyr project https://www.zephyrproject.org/ Zephyr Project is a small, scalable real-time operating system for use on resource-constrained systems supporting multiple architectures. It does come with Cortex m0,m1,m2,m3,m4 baremetal Yocto based toolchain. https://gerrit.zephyrproject.org/r/p/meta-zephyr-sdk.git > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Zhenhua Luo > Sent: Tuesday, September 20, 2016 7:39 AM > To: Trevor Woerner ; Khem Raj > Cc: robert.berger@gmane ; > yocto@yoctoproject.org; yocto-EtnWKYl6rD/WsZ/bqmp...@public.gmane.org > > Subject: Re: [yocto] Cortex-M4 build support > > Thank you so much for your suggestion, Trevor. > > > Best Regards, > > Zhenhua > > > -Original Message- > > From: yocto-boun...@yoctoproject.org [mailto:yocto- > > boun...@yoctoproject.org] On Behalf Of Trevor Woerner > > Sent: Friday, September 16, 2016 4:07 AM > > To: Khem Raj > > Cc: robert.berger@gmane ; > > yocto@yoctoproject.org; yocto- > > EtnWKYl6rD/WsZ/bqmp...@public.gmane.org > EtnWKYl6rD/WsZ/bqmp...@plane.gmane.org> > > Subject: Re: [yocto] Cortex-M4 build support > > > > On Tue 2016-09-13 @ 01:15:49 PM, Khem Raj wrote: > > > > > > > On Sep 13, 2016, at 10:31 AM, robert.berger@gmane > > wrote: > > > > > > > > Hi, > > > > > > > > Shouldn't it be possible to build a bare-metal Cortex-M4 compiler > with the YP > > and build a small RTOS like FreeRTOS with this compiler? > > > > > > > > > > yes it should be possible. you can also look into meta-ti where I > > > think they try to have their DSP toolchain build some code using OE > > > recipe model > > > > Perhaps other things to consider (I'm not entirely sure if these apply, > but maybe > > worth investigating?) > > > > The ROS project has a meta layer: > > https://layers.openembedded.org/layerindex/branch/master/layer/meta-ros/ > > > > If your CortexM board has enough RAM (e.g. http://www.emcraft.com/) you > > can run (a version of) Linux (uClinux) right on your CortexM target: > > https://github.com/EmcraftSystems/linux-emcraft > > > > The Emcraft website appears to provide Linux support for NXP-based > CortexM > > boards too: http://www.emcraft.com/products/456 > > http://www.emcraft.com/products/88 > > -- > > ___ > > 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 17/23] linux-raspberrypi_4.4: upgrade to 4.4.16
On Thu, Aug 11, 2016 at 06:06:02PM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index 8fe5330..9a49dc1 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -1,8 +1,8 @@
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> -LINUX_VERSION ?= "4.4.13"
> +LINUX_VERSION ?= "4.4.16"
>
> -SRCREV = "680be5e27a9593cf26079c6e5744a04cc2809d13"
> +SRCREV = "cff67c7e03f4333149f2a8f6eafd3bc44475114a"
> SRC_URI =
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
> file://0001-fix-dtbo-rules.patch \
> file://0002-vc4-ioctl-rendering-allow.patch \
> --
> 2.9.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Merged paches 17-24 form this set. All the rest where already in master
from previous merged. Thanks.
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] OpenEmbedded Metadata: Recipe update broken
On 09/20/2016 07:29 PM, Paul Eggleton wrote: > On Thu, 25 Aug 2016 18:14:23 Andreas Müller wrote: >> seems layer list update is broken again e.g I am committing on >> meta-qt5-extra regularly but last commit reported is one month ago. > > OK, finally we should be back up and running with updates. We're still fixing > an issue to do with registering new accounts but that too should be sorted in > the next day or so. Sorry about the delay. I'm working on PyQt5, does that belong in meta-qt5 or meta-qt5-extras? Philip PS: Checking commit og in case it is in -extras already :) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Meta layer for pine64
On Fri, Sep 16, 2016 at 2:01 PM, Mont3z Claros wrote: > Hi all, > > I just finished a first beta version of a meta layer for SBC pine64. > You can find it in https://github.com/mont3z/meta-pine64 > > I'd appreciate if anyone has any comments on possible improvements. A > major problem I had was the necessity of two toolchains: one for > compiling u-boot (32 bits) and another for compiling all other > components (64 bis). At the moment I have a very ugly hack to do it. > The 32 bit toolchain is an external toolchain and I set PATH > environmental variable in u-boot recipe. I think it would be desirable to have single toolchain, u-boot is a stand alone app in general, if your compiler can do multilib builds for 32bit then it would be possible to build it. May be you should work with the toolchain team for pine64 to see if that can be done. It will simplify using this layer. Other option I would suggest to build u-boot externally for your SoC, we do not necessarily need a bootloader for building final images anyway. > > Cheers, > Montez > -- > ___ > 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] OpenEmbedded Metadata: Recipe update broken
On Wed, Sep 21, 2016 at 7:05 PM, Philip Balister wrote: > On 09/20/2016 07:29 PM, Paul Eggleton wrote: >> On Thu, 25 Aug 2016 18:14:23 Andreas Müller wrote: >>> seems layer list update is broken again e.g I am committing on >>> meta-qt5-extra regularly but last commit reported is one month ago. >> >> OK, finally we should be back up and running with updates. We're still fixing >> an issue to do with registering new accounts but that too should be sorted in >> the next day or so. Sorry about the delay. > > I'm working on PyQt5, does that belong in meta-qt5 or meta-qt5-extras? > > Philip > > PS: Checking commit og in case it is in -extras already :) I'd prefer putting them to meta-qt5. There they are under the quality hood of Martin's world Andreas -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ptest-runner][PATCH V4] Added error coverage to support when launching child process fails.
From: Edwin Plauchu
An error message is required when detecting one or more
ptest are not launched.
[YOCTO #9752]
Signed-off-by: Edwin Plauchu
---
tests/data/fail/ptest/run-ptest | 0
tests/utils.c | 149 +++-
utils.c | 8 ++-
3 files changed, 121 insertions(+), 36 deletions(-)
create mode 100644 tests/data/fail/ptest/run-ptest
diff --git a/tests/data/fail/ptest/run-ptest b/tests/data/fail/ptest/run-ptest
new file mode 100644
index 000..e69de29
diff --git a/tests/utils.c b/tests/utils.c
index 5d9a909..c68a636 100644
--- a/tests/utils.c
+++ b/tests/utils.c
@@ -37,13 +37,14 @@ extern char *opts_directory;
static char *ptests_found[] = {
"bash",
+"fail",
"gcc",
"glibc",
"hang",
"python",
NULL
};
-static int ptests_found_length = 5;
+static int ptests_found_length = 6;
static char *ptests_not_found[] = {
"busybox",
"perl",
@@ -136,6 +137,101 @@ START_TEST(test_filter_ptests)
ptest_list_free_all(head_new);
END_TEST
+static inline void
+find_word(int *found, const char *line, const char *word) {
+
+ char *pivot = NULL;
+
+ pivot = strdup(line);
+ pivot[strlen(word)] = '\0';
+ if (strcmp(pivot, word) == 0) { *found = 1; }
+ free(pivot);
+}
+
+
+static void
+search_for_fail(const int rp, FILE *fp_stdout, FILE *fp_stderr)
+{
+const char *fail_str = "ERROR";
+char line_buf[PRINT_PTEST_BUF_SIZE];
+int found_fail = 0;
+char *line = NULL;
+
+ck_assert(rp != 0);
+
+while ((line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stdout)) !=
NULL) {
+ find_word(&found_fail, line, fail_str);
+}
+
+ck_assert(found_fail == 1);
+}
+
+
+static void
+search_for_timeout(const int rp, FILE *fp_stdout, FILE *fp_stderr)
+{
+const char *ptest_hang = "hang";
+const char *timeout_str = "TIMEOUT";
+char line_buf[PRINT_PTEST_BUF_SIZE];
+ int found_hang = 0;
+ int found_timeout = 0;
+ int next = 0;
+ char *line = NULL;
+
+ ck_assert(rp != 0);
+
+ while ((line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stdout)) !=
NULL) {
+ if (next) {
+find_word(&found_timeout, line, timeout_str);
+} else {
+find_word(&next, line, ptest_hang); // XXX: Only
compare the name part
+}
+ }
+
+ ck_assert(found_timeout == 1);
+
+/* Test stderr output */
+line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stderr);
+find_word(&found_hang, line, ptest_hang);
+
+ ck_assert(found_hang == 1);
+}
+
+
+static void
+run_specific_one(struct ptest_list *head, const int timeout, char *progname,
+ void (*h_analizer)(const int, FILE *, FILE *))
+{
+char *buf_stdout;
+size_t size_stdout = PRINT_PTEST_BUF_SIZE;
+FILE *fp_stdout;
+char *buf_stderr;
+size_t size_stderr = PRINT_PTEST_BUF_SIZE;
+FILE *fp_stderr;
+
+fp_stdout = open_memstream(&buf_stdout, &size_stdout);
+ck_assert(fp_stdout != NULL);
+fp_stderr = open_memstream(&buf_stderr, &size_stderr);
+ck_assert(fp_stderr != NULL);
+
+ {
+ struct ptest_list *filtered = filter_ptests(head, &progname, 1);
+ ck_assert(ptest_list_length(filtered) == 1);
+
+ h_analizer(
+ run_ptests(filtered, timeout, progname, fp_stdout,
fp_stderr),
+ fp_stdout, fp_stderr
+ );
+
+ PTEST_LIST_FREE_ALL_CLEAN(filtered);
+ }
+
+fclose(fp_stdout);
+free(buf_stdout);
+fclose(fp_stderr);
+free(buf_stderr);
+}
+
START_TEST(test_run_ptests)
struct ptest_list *head;
int timeout = 1;
@@ -148,13 +244,6 @@ START_TEST(test_run_ptests)
size_t size_stderr = PRINT_PTEST_BUF_SIZE;
FILE *fp_stderr;
- int found_timeout = 0;
- int next = 0;
- const char *ptest_hang = "hang";
- const char *timeout_str = "TIMEOUT";
- char *line;
- char line_buf[PRINT_PTEST_BUF_SIZE];
-
fp_stdout = open_memstream(&buf_stdout, &size_stdout);
ck_assert(fp_stdout != NULL);
fp_stderr = open_memstream(&buf_stderr, &size_stderr);
@@ -162,39 +251,33 @@ START_TEST(test_run_ptests)
head = get_available_ptests(opts_directory);
ptest_list_remove(head, "hang", 1);
+ ptest_list_remove(head, "fail", 1);
rc = run_ptests(head, timeout, "test_run_ptests", fp_stdout, fp_stderr);
ck_assert(rc == 0);
ptest_list_free_all(head);
- head = get_available_ptests(opts_directory);
- rc = run_ptests(head, timeout, "test_run_ptests", fp_stdout, fp_stderr);
+fclose(fp_stdout);
+free(buf_stdout);
+fclose(fp_stderr);
+
[yocto] [ptest-runner][PATCH V5] Added error coverage to support when launching child process fails.
From: Edwin Plauchu
An error message is required when detecting one or more
ptest are not launched.
[YOCTO #9752]
Signed-off-by: Edwin Plauchu
---
tests/data/fail/ptest/run-ptest | 0
tests/utils.c | 149 +++-
utils.c | 8 ++-
3 files changed, 121 insertions(+), 36 deletions(-)
create mode 100644 tests/data/fail/ptest/run-ptest
diff --git a/tests/data/fail/ptest/run-ptest b/tests/data/fail/ptest/run-ptest
new file mode 100644
index 000..e69de29
diff --git a/tests/utils.c b/tests/utils.c
index 5d9a909..c68a636 100644
--- a/tests/utils.c
+++ b/tests/utils.c
@@ -37,13 +37,14 @@ extern char *opts_directory;
static char *ptests_found[] = {
"bash",
+"fail",
"gcc",
"glibc",
"hang",
"python",
NULL
};
-static int ptests_found_length = 5;
+static int ptests_found_length = 6;
static char *ptests_not_found[] = {
"busybox",
"perl",
@@ -136,6 +137,101 @@ START_TEST(test_filter_ptests)
ptest_list_free_all(head_new);
END_TEST
+static inline void
+find_word(int *found, const char *line, const char *word) {
+
+ char *pivot = NULL;
+
+ pivot = strdup(line);
+ pivot[strlen(word)] = '\0';
+ if (strcmp(pivot, word) == 0) { *found = 1; }
+ free(pivot);
+}
+
+
+static void
+search_for_fail(const int rp, FILE *fp_stdout, FILE *fp_stderr)
+{
+const char *fail_str = "ERROR";
+char line_buf[PRINT_PTEST_BUF_SIZE];
+int found_fail = 0;
+char *line = NULL;
+
+ck_assert(rp != 0);
+
+while ((line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stdout)) !=
NULL) {
+ find_word(&found_fail, line, fail_str);
+}
+
+ck_assert(found_fail == 1);
+}
+
+
+static void
+search_for_timeout(const int rp, FILE *fp_stdout, FILE *fp_stderr)
+{
+const char *ptest_hang = "hang";
+const char *timeout_str = "TIMEOUT";
+char line_buf[PRINT_PTEST_BUF_SIZE];
+ int found_hang = 0;
+ int found_timeout = 0;
+ int next = 0;
+ char *line = NULL;
+
+ ck_assert(rp != 0);
+
+ while ((line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stdout)) !=
NULL) {
+ if (next) {
+find_word(&found_timeout, line, timeout_str);
+} else {
+find_word(&next, line, ptest_hang); // XXX: Only
compare the name part
+}
+ }
+
+ ck_assert(found_timeout == 1);
+
+/* Test stderr output */
+line = fgets(line_buf, PRINT_PTEST_BUF_SIZE, fp_stderr);
+find_word(&found_hang, line, ptest_hang);
+
+ ck_assert(found_hang == 1);
+}
+
+
+static void
+run_specific_one(struct ptest_list *head, const int timeout, char *progname,
+ void (*h_analizer)(const int, FILE *, FILE *))
+{
+char *buf_stdout;
+size_t size_stdout = PRINT_PTEST_BUF_SIZE;
+FILE *fp_stdout;
+char *buf_stderr;
+size_t size_stderr = PRINT_PTEST_BUF_SIZE;
+FILE *fp_stderr;
+
+fp_stdout = open_memstream(&buf_stdout, &size_stdout);
+ck_assert(fp_stdout != NULL);
+fp_stderr = open_memstream(&buf_stderr, &size_stderr);
+ck_assert(fp_stderr != NULL);
+
+ {
+ struct ptest_list *filtered = filter_ptests(head, &progname, 1);
+ ck_assert(ptest_list_length(filtered) == 1);
+
+ h_analizer(
+ run_ptests(filtered, timeout, progname, fp_stdout,
fp_stderr),
+ fp_stdout, fp_stderr
+ );
+
+ PTEST_LIST_FREE_ALL_CLEAN(filtered);
+ }
+
+fclose(fp_stdout);
+free(buf_stdout);
+fclose(fp_stderr);
+free(buf_stderr);
+}
+
START_TEST(test_run_ptests)
struct ptest_list *head;
int timeout = 1;
@@ -148,13 +244,6 @@ START_TEST(test_run_ptests)
size_t size_stderr = PRINT_PTEST_BUF_SIZE;
FILE *fp_stderr;
- int found_timeout = 0;
- int next = 0;
- const char *ptest_hang = "hang";
- const char *timeout_str = "TIMEOUT";
- char *line;
- char line_buf[PRINT_PTEST_BUF_SIZE];
-
fp_stdout = open_memstream(&buf_stdout, &size_stdout);
ck_assert(fp_stdout != NULL);
fp_stderr = open_memstream(&buf_stderr, &size_stderr);
@@ -162,39 +251,33 @@ START_TEST(test_run_ptests)
head = get_available_ptests(opts_directory);
ptest_list_remove(head, "hang", 1);
+ ptest_list_remove(head, "fail", 1);
rc = run_ptests(head, timeout, "test_run_ptests", fp_stdout, fp_stderr);
ck_assert(rc == 0);
ptest_list_free_all(head);
- head = get_available_ptests(opts_directory);
- rc = run_ptests(head, timeout, "test_run_ptests", fp_stdout, fp_stderr);
+fclose(fp_stdout);
+free(buf_stdout);
+fclose(fp_stderr);
+
Re: [yocto] [meta-cgl][PATCH] libmailtools-perl: 2.13 -> 2.18
ping
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Dai Caiyun
Sent: Monday, August 22, 2016 1:43 PM
To: yocto@yoctoproject.org
Cc: Dai, Caiyun/戴 彩云
Subject: [yocto] [meta-cgl][PATCH] libmailtools-perl: 2.13 -> 2.18
Upgrade libmailtools-perl from 2.13 to 2.18.
Signed-off-by: Dai Caiyun
---
.../perl/{libmailtools-perl_2.13.bb => libmailtools-perl_2.18.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-) rename
meta-cgl-common/recipes-perl/perl/{libmailtools-perl_2.13.bb =>
libmailtools-perl_2.18.bb} (81%)
diff --git a/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.13.bb
b/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
similarity index 81%
rename from meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.13.bb
rename to meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
index 29e5bed..7afcb05 100644
--- a/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.13.bb
+++ b/meta-cgl-common/recipes-perl/perl/libmailtools-perl_2.18.bb
@@ -17,8 +17,8 @@ BBCLASSEXTEND = "native"
PR = "r1"
SRC_URI =
"http://search.cpan.org/CPAN/authors/id/M/MA/MARKOV/MailTools-${PV}.tar.gz";
-SRC_URI[md5sum] = "5d6fbdc56c6e1208e684012437b67e30"
-SRC_URI[sha256sum] =
"7216404681bebce4e09651e1619c3e1eebe2a7e3856f1233af0dd9660ba052b6"
+SRC_URI[md5sum] = "972468ab5207b90398d77bed4ffc361d"
+SRC_URI[sha256sum] =
"dfee9e770257371112f20d978e637759e81bc4f19e97b083585c71ecab37b527"
S = "${WORKDIR}/MailTools-${PV}"
--
2.7.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-cgl][PATCH] pacemaker: 1.1.13 -> 1.1.15
ping
-Original Message-
From: Wang, Xin/王 鑫
Sent: Sunday, September 11, 2016 10:58 PM
To: yocto@yoctoproject.org
Cc: Wang, Xin/王 鑫
Subject: [yocto][meta-cgl][PATCH] pacemaker: 1.1.13 -> 1.1.15
1) Upgrade pacemaker from 1.1.13 to 1.1.15.
2) Modify patch, since the data has been changed.
0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
Signed-off-by: Wang Xin
---
.../0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch | 2 +-
.../pacemaker/{pacemaker_1.1.13.bb => pacemaker_1.1.15.bb}| 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-) rename
meta-cgl-common/recipes-cgl/pacemaker/{pacemaker_1.1.13.bb =>
pacemaker_1.1.15.bb} (96%)
diff --git
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
index 0831fda..3104512 100755
---
a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-search-header-from-STAGING_INCDIR-to-walka.patch
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0002-pacemaker-sea
+++ rch-header-from-STAGING_INCDIR-to-walka.patch
@@ -27,7 +27,7 @@ index 08b4611..6fcd1aa 100644
dnl Eventually remove this
if test "$cross_compiling" != "yes"; then
-- CFLAGS="$CFLAGS -I${prefix}/include/heartbeat"
+- CPPFLAGS="$CPPFLAGS -I${prefix}/include/heartbeat"
+ CFLAGS="$CFLAGS -I${STAGING_INCDIR}/heartbeat"
+ CPPFLAGS="$CPPFLAGS -I${STAGING_INCDIR}/heartbeat"
fi
diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
similarity index 96%
rename from meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
rename to meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
index d2e2395..17c9fe4 100755
--- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.13.bb
+++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_1.1.15.bb
@@ -23,8 +23,8 @@ SRC_URI =
"https://github.com/ClusterLabs/${PN}/archive/Pacemaker-${PV}.zip \
file://volatiles \
file://tmpfiles \
"
-SRC_URI[md5sum] = "d84a5173306727a981a4f87e36007595"
-SRC_URI[sha256sum] =
"e963bc59a5d98a3e3441ea5cccb42aa67f9d7934b80c8818e19ae91c5da48331"
+SRC_URI[md5sum] = "3721971f8adba248076b43f97c4571ab"
+SRC_URI[sha256sum] =
"0787cbc18d1f1b360a11eb7ccb6714042360d4948b2517a9fe43daf9e839af66"
inherit autotools-brokensep pkgconfig systemd python-dir useradd
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cgl][PATCH] resource-agents: 3.9.6 -> 3.9.7
ping
-Original Message-
From: Wang, Xin/王 鑫
Sent: Thursday, September 01, 2016 12:24 PM
To: yocto@yoctoproject.org
Cc: Wang, Xin/王 鑫
Subject: [yocto][meta-cgl][PATCH] resource-agents: 3.9.6 -> 3.9.7
Upgrade resource-agents from 3.9.6 to 3.9.7.
Signed-off-by: Wang Xin
---
.../{resource-agents_3.9.6.bb => resource-agents_3.9.7.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-) rename
meta-cgl-common/recipes-cgl/cluster-resource-agents/{resource-agents_3.9.6.bb
=> resource-agents_3.9.7.bb} (95%)
diff --git
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
similarity index 95%
rename from
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
rename to
meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
index 18ef1e8..a0d4e1f 100644
---
a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agent
+++ s_3.9.7.bb
@@ -20,8 +20,8 @@ SRC_URI =
"https://codeload.github.com/ClusterLabs/resource-agents/tar.gz/v${PV}
file://03-fix-header-defs-lookup.patch \
"
-SRC_URI[md5sum] = "6873d5a217aee3026193fb85bfa18a4a"
-SRC_URI[sha256sum] =
"39722cdee68ff96d06788f05f325bd21ec2fc59c59d847e5e4b23c6df23bf678"
+SRC_URI[md5sum] = "c59096b1bacc704e8a5a285f15729109"
+SRC_URI[sha256sum] =
"e5bd62658fbc236acb83b709f64b2cd9fae52aa4a420a44fed5eb667e928b152"
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
file://COPYING.LGPL;md5=4fbd65380cdd255951079008b364516c \
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH v2] samhain: 4.1.4 -> 4.1.5
ping
-Original Message-
From: Wang, Xin/王 鑫
Sent: Monday, September 19, 2016 3:33 PM
To: yocto@yoctoproject.org
Cc: Wang, Xin/王 鑫
Subject: [yocto][meta-security][PATCH v2] samhain: 4.1.4 -> 4.1.5
1) Upgrade samhain from 4.1.4 to 4.1.5.
2) Add TARGET_CC_ARCH.Fix error.
ERROR: samhain-server-4.1.5-r0 do_package_qa: QA Issue: No GNU_HASH in the
elf binary:
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yule_setpwd'
No GNU_HASH in the elf binary:
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yulectl'
[ldflags]
Signed-off-by: Wang Xin
---
.../samhain/{samhain-client_4.1.4.bb => samhain-client_4.1.5.bb} | 0
.../samhain/{samhain-server_4.1.4.bb => samhain-server_4.1.5.bb} | 2 ++
recipes-security/samhain/samhain.inc | 4 ++--
3 files changed, 4 insertions(+), 2 deletions(-) rename
recipes-security/samhain/{samhain-client_4.1.4.bb => samhain-client_4.1.5.bb}
(100%) rename recipes-security/samhain/{samhain-server_4.1.4.bb =>
samhain-server_4.1.5.bb} (97%)
diff --git a/recipes-security/samhain/samhain-client_4.1.4.bb
b/recipes-security/samhain/samhain-client_4.1.5.bb
similarity index 100%
rename from recipes-security/samhain/samhain-client_4.1.4.bb
rename to recipes-security/samhain/samhain-client_4.1.5.bb
diff --git a/recipes-security/samhain/samhain-server_4.1.4.bb
b/recipes-security/samhain/samhain-server_4.1.5.bb
similarity index 97%
rename from recipes-security/samhain/samhain-server_4.1.4.bb
rename to recipes-security/samhain/samhain-server_4.1.5.bb
index df78f63..0d76b9a 100644
--- a/recipes-security/samhain/samhain-server_4.1.4.bb
+++ b/recipes-security/samhain/samhain-server_4.1.5.bb
@@ -21,6 +21,8 @@ PACKAGECONFIG[acl] = " --enable-posix-acl ,
--disable-posix-acl"
SRC_URI += "file://samhain-server-volatiles"
+TARGET_CC_ARCH += "${LDFLAGS}"
+
EXTRA_OECONF += " \
--with-config-file=REQ_FROM_SERVER/etc/samhainrc \
--with-data-file=REQ_FROM_SERVER/var/lib/samhain/samhain_file \ diff --git
a/recipes-security/samhain/samhain.inc b/recipes-security/samhain/samhain.inc
index 907f431..5bf2ee7 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -9,8 +9,8 @@ SRC_URI =
"http://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
file://${INITSCRIPT_NAME}.default \
"
-SRC_URI[md5sum] = "1ab697b7000d0a272d9ade05bb1bc6e0"
-SRC_URI[sha256sum] =
"32ee7477af11d9f2f64f30b9cb316c351897c1c994c7b98b0ef17fc0ca5e1d1a"
+SRC_URI[md5sum] = "bdb6d2653d706f3180e37ef3d95c824d"
+SRC_URI[sha256sum] =
"4ff4c38765c942abbaac2577df4c8c4940482a1bffc4a719f181c4fca6f173a7"
S = "${WORKDIR}/samhain-${PV}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH v2] samhain: 4.1.4 -> 4.1.5
merged.
thanks,
Armin
On 09/21/2016 06:52 PM, Wang, Xin wrote:
ping
-Original Message-
From: Wang, Xin/王 鑫
Sent: Monday, September 19, 2016 3:33 PM
To: yocto@yoctoproject.org
Cc: Wang, Xin/王 鑫
Subject: [yocto][meta-security][PATCH v2] samhain: 4.1.4 -> 4.1.5
1) Upgrade samhain from 4.1.4 to 4.1.5.
2) Add TARGET_CC_ARCH.Fix error.
ERROR: samhain-server-4.1.5-r0 do_package_qa: QA Issue: No GNU_HASH in the
elf binary:
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yule_setpwd'
No GNU_HASH in the elf binary:
'/yocto/work001/fnst/wangx/poky/build/tmp/work/i586-poky-linux/samhain-server/4.1.5-r0/packages-split/samhain-server/usr/sbin/yulectl'
[ldflags]
Signed-off-by: Wang Xin
---
.../samhain/{samhain-client_4.1.4.bb => samhain-client_4.1.5.bb} | 0
.../samhain/{samhain-server_4.1.4.bb => samhain-server_4.1.5.bb} | 2 ++
recipes-security/samhain/samhain.inc | 4 ++--
3 files changed, 4 insertions(+), 2 deletions(-) rename
recipes-security/samhain/{samhain-client_4.1.4.bb => samhain-client_4.1.5.bb}
(100%) rename recipes-security/samhain/{samhain-server_4.1.4.bb =>
samhain-server_4.1.5.bb} (97%)
diff --git a/recipes-security/samhain/samhain-client_4.1.4.bb
b/recipes-security/samhain/samhain-client_4.1.5.bb
similarity index 100%
rename from recipes-security/samhain/samhain-client_4.1.4.bb
rename to recipes-security/samhain/samhain-client_4.1.5.bb
diff --git a/recipes-security/samhain/samhain-server_4.1.4.bb
b/recipes-security/samhain/samhain-server_4.1.5.bb
similarity index 97%
rename from recipes-security/samhain/samhain-server_4.1.4.bb
rename to recipes-security/samhain/samhain-server_4.1.5.bb
index df78f63..0d76b9a 100644
--- a/recipes-security/samhain/samhain-server_4.1.4.bb
+++ b/recipes-security/samhain/samhain-server_4.1.5.bb
@@ -21,6 +21,8 @@ PACKAGECONFIG[acl] = " --enable-posix-acl ,
--disable-posix-acl"
SRC_URI += "file://samhain-server-volatiles"
+TARGET_CC_ARCH += "${LDFLAGS}"
+
EXTRA_OECONF += " \
--with-config-file=REQ_FROM_SERVER/etc/samhainrc \
--with-data-file=REQ_FROM_SERVER/var/lib/samhain/samhain_file \ diff
--git a/recipes-security/samhain/samhain.inc
b/recipes-security/samhain/samhain.inc
index 907f431..5bf2ee7 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -9,8 +9,8 @@ SRC_URI =
"http://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
file://${INITSCRIPT_NAME}.default \
"
-SRC_URI[md5sum] = "1ab697b7000d0a272d9ade05bb1bc6e0"
-SRC_URI[sha256sum] =
"32ee7477af11d9f2f64f30b9cb316c351897c1c994c7b98b0ef17fc0ca5e1d1a"
+SRC_URI[md5sum] = "bdb6d2653d706f3180e37ef3d95c824d"
+SRC_URI[sha256sum] =
"4ff4c38765c942abbaac2577df4c8c4940482a1bffc4a719f181c4fca6f173a7"
S = "${WORKDIR}/samhain-${PV}"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 0/6] Kernel update + VC4-enhancements
Patches I am using for a while. If my images don't break for other issues I am able to run X11 and weston accelerated in one image. Had never a machine before able to do that. Andreas Müller (6): mesa: align for vc4 xorg align for vc4 vc4: why no framebuffer device? linux-raspberrypi: update to 4.4.21 eglinfo-x11: align to VC4 rpi-base.inc: build vc4-fkms-v3d.dtbo conf/machine/include/rpi-base.inc | 1 + recipes-graphics/eglinfo/eglinfo-x11_%.bbappend| 2 +- recipes-graphics/mesa/mesa_%.bbappend | 1 + .../xorg-xserver/xserver-xorg_%.bbappend | 9 +++ .../0002-vc4-ioctl-rendering-allow.patch | 29 -- recipes-kernel/linux/linux-raspberrypi_4.4.bb | 5 ++-- recipes-kernel/linux/linux-rpi.inc | 2 +- 7 files changed, 15 insertions(+), 34 deletions(-) create mode 100644 recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend delete mode 100644 recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch -- 2.5.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 1/6] mesa: align for vc4
Signed-off-by: Andreas Müller --- recipes-graphics/mesa/mesa_%.bbappend | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-graphics/mesa/mesa_%.bbappend b/recipes-graphics/mesa/mesa_%.bbappend index 9c5df99..e789022 100644 --- a/recipes-graphics/mesa/mesa_%.bbappend +++ b/recipes-graphics/mesa/mesa_%.bbappend @@ -1,2 +1,3 @@ PACKAGECONFIG_append_rpi = " gallium" GALLIUMDRIVERS_rpi = "vc4" +DRIDRIVERS_rpi = "" -- 2.5.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 2/6] xorg align for vc4
Signed-off-by: Andreas Müller
---
recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend | 9 +
1 file changed, 9 insertions(+)
create mode 100644 recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
diff --git a/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
new file mode 100644
index 000..a5a6af3
--- /dev/null
+++ b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
@@ -0,0 +1,9 @@
+OPENGL_PKGCFG = "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', 'dri3
xshmfence glamor', '', d)}"
+
+# slightly modified to oe-core's default: add ${OPENGL_PKGCFG}
+PACKAGECONFIG_rpi ?= " \
+dri2 udev ${XORG_CRYPTO} \
+${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'dri glx
${OPENGL_PKGCFG}', '', d)} \
+${@bb.utils.contains("DISTRO_FEATURES", "wayland", "xwayland", "", d)} \
+${@bb.utils.contains("DISTRO_FEATURES", "systemd", "systemd", "", d)} \
+"
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 3/6] vc4: why no framebuffer device?
Signed-off-by: Andreas Müller
---
recipes-kernel/linux/linux-rpi.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-rpi.inc
b/recipes-kernel/linux/linux-rpi.inc
index 3eeefee..95a9530 100644
--- a/recipes-kernel/linux/linux-rpi.inc
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -116,7 +116,7 @@ do_configure_prepend() {
if [ ${VC4GRAPHICS} = "1" ]; then
kernel_configure_variable I2C_BCM2835 y
kernel_configure_variable DRM y
-kernel_configure_variable DRM_FBDEV_EMULATION n
+kernel_configure_variable DRM_FBDEV_EMULATION y
kernel_configure_variable DRM_VC4 y
kernel_configure_variable FB_BCM2708 n
fi
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 4/6] linux-raspberrypi: update to 4.4.21
This version contains vc4_firmware_kms [1]
https://github.com/raspberrypi/linux/commit/598f79fb5a7ea1a6fbd37b9849e097dd0bea70fc
Signed-off-by: Andreas Müller
---
.../0002-vc4-ioctl-rendering-allow.patch | 29 --
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 5 ++--
2 files changed, 2 insertions(+), 32 deletions(-)
delete mode 100644
recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
diff --git
a/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
b/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
deleted file mode 100644
index 59d0ed7..000
---
a/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-This patch has been accepted upstream in kernel 4.7-rc3
-But it has not yet been backported to 4.4...
-Upstream-Status: Accepted
[http://www.gossamer-threads.com/lists/linux/kernel/2459302]
-Signed-off-by: Herve Jourdain
-
-diff --git a/drivers/gpu/drm/vc4/vc4_drv.c b/drivers/gpu/drm/vc4/vc4_drv.c
-index a5b68c1..14b5ec1 100644
a/drivers/gpu/drm/vc4/vc4_drv.c
-+++ b/drivers/gpu/drm/vc4/vc4_drv.c
-@@ -75,12 +75,12 @@ static const struct file_operations vc4_drm_fops = {
- };
-
- static const struct drm_ioctl_desc vc4_drm_ioctls[] = {
-- DRM_IOCTL_DEF_DRV(VC4_SUBMIT_CL, vc4_submit_cl_ioctl, 0),
-- DRM_IOCTL_DEF_DRV(VC4_WAIT_SEQNO, vc4_wait_seqno_ioctl, 0),
-- DRM_IOCTL_DEF_DRV(VC4_WAIT_BO, vc4_wait_bo_ioctl, 0),
-- DRM_IOCTL_DEF_DRV(VC4_CREATE_BO, vc4_create_bo_ioctl, 0),
-- DRM_IOCTL_DEF_DRV(VC4_MMAP_BO, vc4_mmap_bo_ioctl, 0),
-- DRM_IOCTL_DEF_DRV(VC4_CREATE_SHADER_BO, vc4_create_shader_bo_ioctl, 0),
-+ DRM_IOCTL_DEF_DRV(VC4_SUBMIT_CL, vc4_submit_cl_ioctl,
0|DRM_RENDER_ALLOW),
-+ DRM_IOCTL_DEF_DRV(VC4_WAIT_SEQNO, vc4_wait_seqno_ioctl,
0|DRM_RENDER_ALLOW),
-+ DRM_IOCTL_DEF_DRV(VC4_WAIT_BO, vc4_wait_bo_ioctl, 0|DRM_RENDER_ALLOW),
-+ DRM_IOCTL_DEF_DRV(VC4_CREATE_BO, vc4_create_bo_ioctl,
0|DRM_RENDER_ALLOW),
-+ DRM_IOCTL_DEF_DRV(VC4_MMAP_BO, vc4_mmap_bo_ioctl, 0|DRM_RENDER_ALLOW),
-+ DRM_IOCTL_DEF_DRV(VC4_CREATE_SHADER_BO, vc4_create_shader_bo_ioctl,
0|DRM_RENDER_ALLOW),
- DRM_IOCTL_DEF_DRV(VC4_GET_HANG_STATE, vc4_get_hang_state_ioctl,
- DRM_ROOT_ONLY),
- };
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 9a49dc1..81e32c0 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,10 +1,9 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
-LINUX_VERSION ?= "4.4.16"
+LINUX_VERSION ?= "4.4.21"
-SRCREV = "cff67c7e03f4333149f2a8f6eafd3bc44475114a"
+SRCREV = "9669a50a3a8e4f33b4fe138277bc4407e1eab9b2"
SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-fix-dtbo-rules.patch \
- file://0002-vc4-ioctl-rendering-allow.patch \
"
require linux-raspberrypi.inc
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 6/6] rpi-base.inc: build vc4-fkms-v3d.dtbo
For those who want to run closed source driver with mesa. See further details at [1] [1] http://anholt.livejournal.com/47717.html Signed-off-by: Andreas Müller --- conf/machine/include/rpi-base.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc index 69774f4..737e842 100644 --- a/conf/machine/include/rpi-base.inc +++ b/conf/machine/include/rpi-base.inc @@ -38,6 +38,7 @@ KERNEL_DEVICETREE ?= " \ overlays/w1-gpio-pullup.dtbo \ overlays/pi3-miniuart-bt.dtbo \ overlays/vc4-kms-v3d.dtbo \ +overlays/vc4-fkms-v3d.dtbo \ " KERNEL_IMAGETYPE ?= "Image" -- 2.5.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 5/6] eglinfo-x11: align to VC4
Signed-off-by: Andreas Müller
---
recipes-graphics/eglinfo/eglinfo-x11_%.bbappend | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-graphics/eglinfo/eglinfo-x11_%.bbappend
b/recipes-graphics/eglinfo/eglinfo-x11_%.bbappend
index fd32abc..2d720ba 100644
--- a/recipes-graphics/eglinfo/eglinfo-x11_%.bbappend
+++ b/recipes-graphics/eglinfo/eglinfo-x11_%.bbappend
@@ -1,2 +1,2 @@
-EGLINFO_DEVICE_rpi = "raspberrypi"
+EGLINFO_DEVICE_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics',
'generic', 'raspberrypi', d)}"
ASNEEDED = ""
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
