Re: [yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
Hello.
I'm new here and I didn't know how to prepare patch correctly- I just
used instructions from meta-raspberrypi README.
I can resend it if you want. Especially now when the patch is not
necessary anymore, because Andrei Gherzan has merged latest revision of
omxplayer to master (patch with explicit linking vchostif lib was taken
from there).
Please provide me with instruction on how to create a patch properly.
Thank you,
Piotr Lewicki
On 22.04.2016 05:01, Gary Thomas wrote:
On 2016-04-22 02:44, Mark Hatle wrote:
On 4/21/16 6:31 PM, Khem Raj wrote:
resend this patch to OE-Core mailing list. and also add
Upstream-Status: to patch
I don't see a "why" anywhere.
Something wrong with libav, something better with ffmpeg, etc?
libav was replaced in OE-core by ffmpeg
On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki
wrote:
---
.../omxplayer/explicitly_link_with_vchostif_library.patch | 13
+
recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644
recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
diff --git
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
new file mode 100644
index 000..642f63a
--- /dev/null
+++
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
b/Makefile
+@@ -51,7 +51,7 @@ version:
+ bash gen_version.sh > version.h
+
+ omxplayer.bin: version $(OBJS)
+- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat
-lswscale -lswresample -lpcre
++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm
-lvchostif -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec
-lavformat -lswscale -lswresample -lpcre
+ $(STRIP) omxplayer.bin
+
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl
samba libssh"
-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl
samba libssh"
+PR = "r5"
SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
\
@@ -19,6 +19,7 @@ SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+ file://explicitly_link_with_vchostif_library.patch \
"
S = "${WORKDIR}/git"
--
2.5.0
--
___
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] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
On 2016-04-22 02:44, Mark Hatle wrote:
On 4/21/16 6:31 PM, Khem Raj wrote:
resend this patch to OE-Core mailing list. and also add
Upstream-Status: to patch
I don't see a "why" anywhere.
Something wrong with libav, something better with ffmpeg, etc?
libav was replaced in OE-core by ffmpeg
On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki wrote:
---
.../omxplayer/explicitly_link_with_vchostif_library.patch | 13 +
recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644
recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
diff --git
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
new file mode 100644
index 000..642f63a
--- /dev/null
+++
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
b/Makefile
+@@ -51,7 +51,7 @@ version:
+ bash gen_version.sh > version.h
+
+ omxplayer.bin: version $(OBJS)
+- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos -ldbus-1
-lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample -lpcre
++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale
-lswresample -lpcre
+ $(STRIP) omxplayer.bin
+
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh"
-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba libssh"
+PR = "r5"
SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
@@ -19,6 +19,7 @@ SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+ file://explicitly_link_with_vchostif_library.patch \
"
S = "${WORKDIR}/git"
--
2.5.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
On 2016-04-22 01:31, Khem Raj wrote:
resend this patch to OE-Core mailing list. and also add
Upstream-Status: to patch
Actually, it should go to the RaspberryPi mailing list, not OE-core
Also, there are no Signed-off-by lines
On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki wrote:
---
.../omxplayer/explicitly_link_with_vchostif_library.patch | 13 +
recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644
recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
diff --git
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
new file mode 100644
index 000..642f63a
--- /dev/null
+++
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
b/Makefile
+@@ -51,7 +51,7 @@ version:
+ bash gen_version.sh > version.h
+
+ omxplayer.bin: version $(OBJS)
+- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos -ldbus-1
-lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample -lpcre
++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale
-lswresample -lpcre
+ $(STRIP) omxplayer.bin
+
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh"
-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba libssh"
+PR = "r5"
SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
@@ -19,6 +19,7 @@ SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+ file://explicitly_link_with_vchostif_library.patch \
"
S = "${WORKDIR}/git"
--
2.5.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
On 4/21/16 6:31 PM, Khem Raj wrote:
> resend this patch to OE-Core mailing list. and also add
> Upstream-Status: to patch
I don't see a "why" anywhere.
Something wrong with libav, something better with ffmpeg, etc?
--Mark
>
> On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki wrote:
>> ---
>> .../omxplayer/explicitly_link_with_vchostif_library.patch | 13
>> +
>> recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
>> 2 files changed, 16 insertions(+), 2 deletions(-)
>> create mode 100644
>> recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>>
>> diff --git
>> a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>>
>> b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>> new file mode 100644
>> index 000..642f63a
>> --- /dev/null
>> +++
>> b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>> @@ -0,0 +1,13 @@
>> +diff --git a/Makefile b/Makefile
>> +index 80b63b1..bcfadfb 100644
>> +--- a/Makefile
>> b/Makefile
>> +@@ -51,7 +51,7 @@ version:
>> + bash gen_version.sh > version.h
>> +
>> + omxplayer.bin: version $(OBJS)
>> +- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos
>> -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample
>> -lpcre
>> ++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif
>> -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale
>> -lswresample -lpcre
>> + $(STRIP) omxplayer.bin
>> +
>> + help.h: README.md Makefile
>> diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
>> b/recipes-multimedia/omxplayer/omxplayer_git.bb
>> index c8251fe..c2b1342 100644
>> --- a/recipes-multimedia/omxplayer/omxplayer_git.bb
>> +++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
>> @@ -7,8 +7,8 @@ SECTION = "console/utils"
>> LICENSE = "GPLv2"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
>>
>> -DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba
>> libssh"
>> -PR = "r4"
>> +DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba
>> libssh"
>> +PR = "r5"
>>
>> SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
>> SRC_URI =
>> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
>> @@ -19,6 +19,7 @@ SRC_URI =
>> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
>> file://fix-tar-command-with-DIST.patch \
>> file://use-native-pkg-config.patch \
>> file://don-t-preserve-file-attributes-when-cp.patch \
>> + file://explicitly_link_with_vchostif_library.patch \
>> "
>> S = "${WORKDIR}/git"
>>
>> --
>> 2.5.0
>>
>> --
>> ___
>> 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] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
resend this patch to OE-Core mailing list. and also add
Upstream-Status: to patch
On Wed, Apr 20, 2016 at 6:11 AM, piotr.lewicki wrote:
> ---
> .../omxplayer/explicitly_link_with_vchostif_library.patch | 13
> +
> recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
> 2 files changed, 16 insertions(+), 2 deletions(-)
> create mode 100644
> recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>
> diff --git
> a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
>
> b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
> new file mode 100644
> index 000..642f63a
> --- /dev/null
> +++
> b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
> @@ -0,0 +1,13 @@
> +diff --git a/Makefile b/Makefile
> +index 80b63b1..bcfadfb 100644
> +--- a/Makefile
> b/Makefile
> +@@ -51,7 +51,7 @@ version:
> + bash gen_version.sh > version.h
> +
> + omxplayer.bin: version $(OBJS)
> +- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos
> -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample
> -lpcre
> ++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif
> -lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale
> -lswresample -lpcre
> + $(STRIP) omxplayer.bin
> +
> + help.h: README.md Makefile
> diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
> b/recipes-multimedia/omxplayer/omxplayer_git.bb
> index c8251fe..c2b1342 100644
> --- a/recipes-multimedia/omxplayer/omxplayer_git.bb
> +++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
> @@ -7,8 +7,8 @@ SECTION = "console/utils"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
>
> -DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba
> libssh"
> -PR = "r4"
> +DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba
> libssh"
> +PR = "r5"
>
> SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
> SRC_URI =
> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
> @@ -19,6 +19,7 @@ SRC_URI =
> "git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
> file://fix-tar-command-with-DIST.patch \
> file://use-native-pkg-config.patch \
> file://don-t-preserve-file-attributes-when-cp.patch \
> + file://explicitly_link_with_vchostif_library.patch \
> "
> S = "${WORKDIR}/git"
>
> --
> 2.5.0
>
> --
> ___
> 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] Fwd: Preventing rebuild of dependencies
On Thu, Apr 21, 2016 at 6:08 AM, Sassan Panahinejad wrote: > Hi, > > On several Yocto-based projects I've worked on, I've ended up accidentally > triggering rebuilds of large packages such as QT or Chromium. > > The example I keep running into at the moment is whenever I modify the > kernel config, I trigger Chromium to rebuild next time I rebuild the image. > This means losing as much as 4 hours every time. > > When searching for a solution, I found other posts and the workaround > usually given is not to rebuild the image after kernel changes and copy the > kernel manually. That's all very well, but I'm also making changes to other > parts of the system and therefore need to be able to rebuild the image > without waiting for Chromium to compile. > > The problem seems to come down to one of Chromium's deps depending on the > kernel for some headers. Now naturally changes to a dependency results in a > rebuild, but I the operator know that the change in question will not have > any affect. Then use locked sstate mechanism. > > I'd like to just be able to blacklist rebuilding of Chromium and QT, but I > can't find a way other than sticking in some fake rules in the Chromium > recipe. In buildroot, one could often cheat by touching the relevant stamp > file to make it think it had rebuilt. Is the same possible in Yocto? > > Note: sstate-cache is enabled. > > Thanks > Sassan Panahinejad > > > -- > ___ > 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 2/4] rpi-config: Add UART enabler
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/bootfiles/rpi-config_git.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 2941982..0fbb17e 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -95,6 +95,11 @@ do_deploy() {
if [ "${PITFT28r}" = "1" ]; then
echo "# Enable PITFT28r display"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
echo
"dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+
+# UART support
+if [ "${ENABLE_UART}" = "1" ]; then
+echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
fi
}
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 4/4] README: Document new variable configuration
From: Theodor Gherzan Signed-off-by: Theodor Gherzan --- README | 7 +++ 1 file changed, 7 insertions(+) diff --git a/README b/README index ec9f905..ee330df 100644 --- a/README +++ b/README @@ -29,6 +29,7 @@ Contents: 3.L. Enable SPI bus 3.M. Enable I2C 3.N. Enable PiTFT support +3.O. Enable UART support 4. Extra apps 4.A. omxplayer 5. Board Configuration @@ -238,6 +239,12 @@ List of currently supported models: - pitft22 - pitft28r +3.O. Enable UART +=== +Set this variable to enable UART on raspberypi3: +ENABLE_UART = "1" + +Note: The value of enable_uart would be set to 1 by default on raspberrypi 1/2. 4. Extra apps = -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 3/4] linux-raspberrypi: Make use of serial aliases
From: Theodor Gherzan
The firmware will parse cmdline and replace serial aliases with the
actual serial console port.
Signed-off-by: Theodor Gherzan
---
recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index f8e0c92..eccbbc6 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
# CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
+CMDLINE = "dwc_otg.lpm_enable=0 console=serial0 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
# Add the kernel debugger over console kernel command line option if enabled
CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1",
"kgdboc=ttyAMA0,115200", "", d)}'
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2 1/4] firmware.inc: Update firmware to include various serial fixes
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/common/firmware.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index c1117d6..abc7d06 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "046effa13ebc4cc7601df4f06f4834bd0eebb0f8"
-RPIFW_DATE ?= "20160326"
+RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
+RPIFW_DATE ?= "20160303"
RPIFW_SRC_URI ?=
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
RPIFW_S ?= "${WORKDIR}/git"
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 2/4] rpi-config: Add UART enabler
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/bootfiles/rpi-config_git.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 2941982..0fbb17e 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -95,6 +95,11 @@ do_deploy() {
if [ "${PITFT28r}" = "1" ]; then
echo "# Enable PITFT28r display"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
echo
"dtoverlay=pitft28-resistive,rotate=90,speed=3200,txbuflen=32768"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+
+# UART support
+if [ "${ENABLE_UART}" = "1" ]; then
+echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
fi
}
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 3/4] linux-raspberrypi: Make use of serial aliases
From: Theodor Gherzan
The firmware will parse cmdline and replace serial aliases with the
actual serial console port.
Signed-off-by: Theodor Gherzan
---
recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index f8e0c92..eccbbc6 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
# CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
+CMDLINE = "dwc_otg.lpm_enable=0 console=serial0 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
# Add the kernel debugger over console kernel command line option if enabled
CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1",
"kgdboc=ttyAMA0,115200", "", d)}'
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 4/4] README: Document new variable configuration
From: Theodor Gherzan Signed-off-by: Theodor Gherzan --- README | 7 +++ 1 file changed, 7 insertions(+) diff --git a/README b/README index ec9f905..ee330df 100644 --- a/README +++ b/README @@ -29,6 +29,7 @@ Contents: 3.L. Enable SPI bus 3.M. Enable I2C 3.N. Enable PiTFT support +3.O. Enable UART support 4. Extra apps 4.A. omxplayer 5. Board Configuration @@ -238,6 +239,12 @@ List of currently supported models: - pitft22 - pitft28r +3.O. Enable UART +=== +Set this variable to enable UART on raspberypi3: +ENABLE_UART = "1" + +Note: The value of enable_uart would be set to 1 by default on raspberrypi 1/2. 4. Extra apps = -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 1/4] firmware.inc: Update firmware to include various serial fixes
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/common/firmware.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index c1117d6..abc7d06 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "046effa13ebc4cc7601df4f06f4834bd0eebb0f8"
-RPIFW_DATE ?= "20160326"
+RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
+RPIFW_DATE ?= "20160303"
RPIFW_SRC_URI ?=
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
RPIFW_S ?= "${WORKDIR}/git"
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 2/5] firmware.inc: Update firmware to include various serial fixes
On Thu, Apr 21, 2016 at 06:32:10PM +0100, Theodor Gherzan wrote: > From: Theodor Gherzan > > Signed-off-by: Theodor Gherzan Doesn't apply over over current master. Can you send a v2 without Trevor's patch and with the updated one for README? -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] serial console definition split
Hi Trevor, On Wed, Apr 13, 2016 at 01:06:21PM -0400, Trevor Woerner wrote: > 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 Merged this 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] omxplayer: Bump revision
On Sat, Apr 16, 2016 at 11:20:51AM +1000, Jonathan Liu wrote: > Fixes linking error due to missing vchostif library dependency. > Rebased patches and removed patches already merged upstream. > > Signed-off-by: Jonathan Liu 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 5/5] README: Document new variable configuration
From: Theodor Gherzan Signed-off-by: Theodor Gherzan --- README | 7 +++ 1 file changed, 7 insertions(+) diff --git a/README b/README index 536926b..326b0bd 100644 --- a/README +++ b/README @@ -29,6 +29,7 @@ Contents: 3.L. Enable SPI bus 3.M. Enable I2C 3.N. Enable PiTFT support +3.O. Enable UART support 4. Extra apps 4.A. omxplayer 5. Board Configuration @@ -233,6 +234,12 @@ the modelname should be added as a MACHINE_FEATURES in local.conf like below: List of currently supported models: - pitft22 +3.O. Enable UART +=== +Set this variable to enable UART on raspberypi3: +ENABLE_UART = "1" + +Note: The value of enable_uart would be set to 1 by default on raspberrypi 1/2. 4. Extra apps = -- 2.1.4 On Thu, Apr 21, 2016 at 6:55 PM, Andrei Gherzan wrote: > On Thu, Apr 21, 2016 at 06:32:13PM +0100, Theodor Gherzan wrote: >> From: Theodor Gherzan >> >> Signed-off-by: Theodor Gherzan >> --- >> README | 4 >> 1 file changed, 4 insertions(+) >> >> diff --git a/README b/README >> index 536926b..cbc7a92 100644 >> --- a/README >> +++ b/README >> @@ -233,6 +233,10 @@ the modelname should be added as a MACHINE_FEATURES in >> local.conf like below: >> List of currently supported models: >> - pitft22 >> >> +3.O. Enable UART >> +=== >> +Set this variable to enable UART: >> +ENABLE_UART = "1" > > Based on the explaination about enable_uart this is not quite right. > Cause on rpi1, rpi2 and cm it will get enabled without this variable by > default. So this needs a little additional information. > >> >> 4. Extra apps >> = >> -- >> 2.1.4 >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > -- > Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Using Java-based code generator in bitbake recipes
Hello everybody,
I need to write bitbake recipes for applications that rely on code generation
as a part of their build. The generator is an Eclipse RCP application that is
available as a pre-built binary. The latter can also be built from the source
code with Maven. The pre-built binary is self-contained and includes
executable launchers for several platforms including linux-x86_64 and linux-x86
as well as .jar files. The launchers only depend on JRE that must be installed
on the build host.
So far I was able to create working bitbake recipes for application build
scripts that are based on either autotools or CMake and expect the generator to
be reachable through the PATH. In order to make sure that the generator is
available on the build host, the recipes add 'generator-native' to the value of
their DEPENDS variables. The recipe generator-native includes the line
'inherit native', fetches pre-built binaries and installs them into ${D}.
The above works as long as (a) the build host has a right version of the JRE
installed and (b) the required version of the pre-built generator binaries is
available. Now my questions are:
1) What would be the recommended way to make sure that (a) is fulfilled?
Should the generator-native recipe test the presence of the right JRE version
on the build host and just fail if this pre-requisite is not fulfilled? Or
should it rather install the JRE (e.g., by using meta-java or meta-java-oracle)?
2) Would it be feasible/sane to support building the generator as a part of
bitbake build? This would help to fulfill (b) through building the generator
from sources, which would also be handy during the generator development. This
would require that the build host also includes Maven, but I was unable to find
an existing native recipe for it. I also wonder how well a Maven build can be
contained by the bitbake build environment. Any hints on what is involved in
making this work would be appreciated.
Thanks,
--Pavel Konopelko
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 5/5] README: Document new variable configuration
On Thu, Apr 21, 2016 at 06:32:13PM +0100, Theodor Gherzan wrote: > From: Theodor Gherzan > > Signed-off-by: Theodor Gherzan > --- > README | 4 > 1 file changed, 4 insertions(+) > > diff --git a/README b/README > index 536926b..cbc7a92 100644 > --- a/README > +++ b/README > @@ -233,6 +233,10 @@ the modelname should be added as a MACHINE_FEATURES in > local.conf like below: > List of currently supported models: > - pitft22 > > +3.O. Enable UART > +=== > +Set this variable to enable UART: > +ENABLE_UART = "1" Based on the explaination about enable_uart this is not quite right. Cause on rpi1, rpi2 and cm it will get enabled without this variable by default. So this needs a little additional information. > > 4. Extra apps > = > -- > 2.1.4 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++
Thanks for the link.
I already have found my hack patch. ;)
I'll take some time to check the EGL test dedicated to the Raspberry in Qt. I
did not check this one yet.
Regards,
Sent from my WIKO RAINBOW LITE 4GLe 21 avr. 2016 7:10 PM, Andrei Gherzan a
écrit : > > Hi Julien, > > On Thu, Apr 21, 2016 at 10:15:23AM +0200, Julien
Gueytat wrote: > > Just to keep you informed that a bug report has been opened
to Qt: > > https://bugreports.qt.io/browse/QTBUG-52739 > > > > We might save
some patches in layers by solving this, > > Thanks for helping, > > > > Great
Julien. Here is a hint - would this help your problem? >
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028277.html > > >
Le 20/04/2016 01:46, Julien Gueytat a écrit : > > > Hi again guys, > > > > > >
after more investigations: > > > > > > I found out that the default value -lEGL
comes from > > > ./mkspecs/common/linux.conf which is included in > > >
./mkspecs/linux-oe-g++/qmake.conf > > > > > > linux-oe-g++ being the only
generic mkspecs that should be used in Yocto > > > > > > So! At the time the
configuration enters egl.pro the content of the > > > variables LIBS and
QMAKE_EGL_LIBS are still a bit weird for me : > > > > > > 1- LIBS already has
the content of the QMAKE_EGL_LIBS content from the > > > result of the
pkg-config command. > > > 2- QMAKE_EGL_LIBS has the content of the default
value found in > > > ./mkspecs/common/linux.conf > > > > > > There are two
options to have it properly working: > > > - First and easy option : remove the
QMAKE_EGL_LIBS default variable in > > > ./mkspecs/linux-oe-g++/qmake.conf
since the good libs seems to already > > > been present in the LIBS variable. >
> > - Second option : understand why the LIBS variable is already properly > >
> set and why the QMAKE_EGL_LIBS properly computed in the configure and > > >
present .qmake.vars is not used. (I would say that the device spec > > >
overrides the one from qmake spec... I did not dig further yet.) > > > > > >
Anyway I'm pretty sure the trouble comes from meta-qt5 side now. I'm > > >
pretty sure meta-raspberrypi maintainers can confirm that their master > > >
branch handles pkg-config stuff now. > > > > > > Thanks advance for having a
look on this guys, > > > Best Regards > > > > > > > > > Le 19/04/2016 10:46,
Julien Gueytat a écrit : > > > > Hi, > > > > > > > > I still can't figure out
the patch to apply in meta-qt5 to get EGL > > > > support with the Raspberry. >
> > > > > > > The test to check EGL does not pass and fails with the following
command: > > > > > > > > arm-poky-linux-gnueabi-g++ -march=armv7-a -marm
-mthumb-interwork > > > > -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7
--sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
> > > > -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o > >
> > -lGLESv2 -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL > > > > >
> > > > > > > Here is the content of the file egl.pro: > > > > > > > > $ cat
egl.pro > > > > SOURCES = egl.cpp > > > > > > > > for(p, QMAKE_LIBDIR_EGL) { >
> > > exists($$p):LIBS += -L$$p > > > > } > > > > > > > > message("In
egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL") > > > > message("In egl.pro -
1: LIBS = $$LIBS") > > > > > > > > !isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH +=
$$QMAKE_INCDIR_EGL > > > > !isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL >
> > > > > > > message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL") > >
> > message("In egl.pro - 2: LIBS = $$LIBS") > > > > > > > > CONFIG -= qt > > >
> > > > > In the main ./configure file of qtbase: > > > > > > > > | In
configure #1: QMAKE_LIBS_EGL = > > > > | In configure #2: QMAKE_LIBS_EGL =
-lEGL -lGLESv2 -lbcm_host > > > > -lvchostif -lbcm_host -lvcos -lvchiq_arm
-pthread > > > > > > > > The variable QMAKE_LIBS_EGL is set properly. > > > > >
> > > > > > > In the ./config.tests/qpa/egl/egl.pro file: > > > > > > > > |
Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL > > > > | Project
MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host > > > > -lvchostif
-lvcos -lvchiq_arm -pthread > > > > | Project MESSAGE: In egl.pro - 2:
QMAKE_LIBS_EGL = -lEGL > > > > | Project MESSAGE: In egl.pro - 2: LIBS = -lEGL
-lGLESv2 -lbcm_host > > > > -lvchostif -lvcos -lvchiq_arm -pthread -lEGL > > >
> > > > > > > > > *What I see is that:* > > > > In the configure file the
variable QMAKE_LIBS_EGL is properly set > > > > through pkg-config. > > > > In
the egl.pro file... The variable LIBS gets the content of > > > >
QMAKE_LIBS_EGL and the variable QMAKE_LIBS_EGL gets back to its > > > > default
-lEGL. > > > > > > > > In the end with have -lGLESv2 before -lEGL and this does
not link. > > > > > > > > I checked also the content of .qmake.vars: > > > >
grep QMAKE_LIBS_EGL .qmake.vars > > > > QMAKE_LIBS_EGL = -lEGL -lGLESv2
-lbcm_host -lvchostif -lbcm_host > > > > -lvcos -lvchiq_arm -pthread > > > > >
> > > > > > > The c
Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler
On Thu, Apr 21, 2016 at 06:47:29PM +0100, Theodor Gherzan wrote: > A new config.txt setting has been introduced - enable_uart - the > purpose of which is to control the initialisation of the UART(*). The > default value varies according to the primary UART on the platform - > if the PL011 is the primary UART (that used for the console and boot > messages) then enable_uart defaults to 1, and if the mini-UART is the > primary then it defaults to 0. > Got it now. So people with rpi3 will need to set this to get serial enabled but rpi1-2 will get it by default. Can you please add a summary in README too? -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler
A new config.txt setting has been introduced - enable_uart - the
purpose of which is to control the initialisation of the UART(*). The
default value varies according to the primary UART on the platform -
if the PL011 is the primary UART (that used for the console and boot
messages) then enable_uart defaults to 1, and if the mini-UART is the
primary then it defaults to 0.
The reason for the additional setting is that making use of the
mini-UART requires the core frequency to be fixed, so setting
enable_uart will limit the core to the minimum (unless force_turbo is
set, since that will fix the core frequency to the maximum, provided
the Pi is adequately powered and cooled). The previous default
behaviour, which rendered much of the output illegible, was not
useful, but we didn't want to restrict all users (even those who don't
care about the UART) to the minimum core frequency. We also wanted to
be able to remove the restriction when the PL011 is chosen on a Pi3,
hence the need for a dedicated setting indicating the reason for the
frequency limit.
On Thu, Apr 21, 2016 at 6:46 PM, Theodor Gherzan wrote:
> Here is a full explination of this:
>
>
> On Thu, Apr 21, 2016 at 6:43 PM, Andrei Gherzan wrote:
>> Hi,
>>
>> On Thu, Apr 21, 2016 at 06:32:11PM +0100, Theodor Gherzan wrote:
>>> From: Theodor Gherzan
>>>
>>> Signed-off-by: Theodor Gherzan
>>> ---
>>> recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
>>> b/recipes-bsp/bootfiles/rpi-config_git.bb
>>> index 4d41723..6ddf843 100644
>>> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
>>> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
>>> @@ -90,6 +90,12 @@ do_deploy() {
>>> echo "# Enable PITFT22 display"
>>> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>>> echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768"
>>> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>>> fi
>>> +
>>> +# UART support
>>> +if [ "${ENABLE_UART}" = "1" ]; then
>>> +echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>>> +echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>> What is the default value of enable_uart?
>>
>> --
>> Andrei Gherzan
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler
Here is a full explination of this:
On Thu, Apr 21, 2016 at 6:43 PM, Andrei Gherzan wrote:
> Hi,
>
> On Thu, Apr 21, 2016 at 06:32:11PM +0100, Theodor Gherzan wrote:
>> From: Theodor Gherzan
>>
>> Signed-off-by: Theodor Gherzan
>> ---
>> recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
>> b/recipes-bsp/bootfiles/rpi-config_git.bb
>> index 4d41723..6ddf843 100644
>> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
>> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
>> @@ -90,6 +90,12 @@ do_deploy() {
>> echo "# Enable PITFT22 display"
>> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>> echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768"
>> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>> fi
>> +
>> +# UART support
>> +if [ "${ENABLE_UART}" = "1" ]; then
>> +echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>> +echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> What is the default value of enable_uart?
>
> --
> Andrei Gherzan
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler
Hi,
On Thu, Apr 21, 2016 at 06:32:11PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan
>
> Signed-off-by: Theodor Gherzan
> ---
> recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
> b/recipes-bsp/bootfiles/rpi-config_git.bb
> index 4d41723..6ddf843 100644
> --- a/recipes-bsp/bootfiles/rpi-config_git.bb
> +++ b/recipes-bsp/bootfiles/rpi-config_git.bb
> @@ -90,6 +90,12 @@ do_deploy() {
> echo "# Enable PITFT22 display"
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768"
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> fi
> +
> +# UART support
> +if [ "${ENABLE_UART}" = "1" ]; then
> +echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
> +echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
What is the default value of enable_uart?
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 3/5] rpi-config: Add UART enabler
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/bootfiles/rpi-config_git.bb | 6 ++
1 file changed, 6 insertions(+)
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4d41723..6ddf843 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -90,6 +90,12 @@ do_deploy() {
echo "# Enable PITFT22 display"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768"
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
fi
+
+# UART support
+if [ "${ENABLE_UART}" = "1" ]; then
+echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
}
addtask deploy before do_package after do_install
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 5/5] README: Document new variable configuration
From: Theodor Gherzan Signed-off-by: Theodor Gherzan --- README | 4 1 file changed, 4 insertions(+) diff --git a/README b/README index 536926b..cbc7a92 100644 --- a/README +++ b/README @@ -233,6 +233,10 @@ the modelname should be added as a MACHINE_FEATURES in local.conf like below: List of currently supported models: - pitft22 +3.O. Enable UART +=== +Set this variable to enable UART: +ENABLE_UART = "1" 4. Extra apps = -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 4/5] linux-raspberrypi: Make use of serial aliases
From: Theodor Gherzan
The firmware will parse cmdline and replace serial aliases with the
actual serial console port.
Signed-off-by: Theodor Gherzan
---
recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
b/recipes-kernel/linux/linux-raspberrypi.inc
index 24e7fe2..2dcab94 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,7 +20,7 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
# CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
+CMDLINE = "dwc_otg.lpm_enable=0 console=serial0 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait"
# Add the kernel debugger over console kernel command line option if enabled
CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1",
"kgdboc=ttyAMA0,115200", "", d)}'
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 2/5] firmware.inc: Update firmware to include various serial fixes
From: Theodor Gherzan
Signed-off-by: Theodor Gherzan
---
recipes-bsp/common/firmware.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index 2c4f497..abc7d06 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,4 +1,4 @@
-RPIFW_SRCREV ?= "028b1f6585280bd0a21885973589c4b101355597"
+RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
RPIFW_DATE ?= "20160303"
RPIFW_SRC_URI ?=
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
RPIFW_S ?= "${WORKDIR}/git"
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH 1/5] SERIAL_CONSOLE definition split
From: 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
Signed-off-by: Theodor Gherzan
---
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 792150e..b125506 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.1.4
--
___
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
On Sat, Apr 16, 2016 at 11:24:01AM +1000, Jonathan Liu wrote: > Hi Khem, > > On 14 April 2016 at 02:36, Khem Raj wrote: > > Thats interesting, I will try to reproduce it > > I have submitted a patch to the mailing list to bump the omxplayer > revision which fixes the issue. > Cool. I'll take a look on it, test it and merge today. -- Andrei Gherzan signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++
Hi Julien,
On Thu, Apr 21, 2016 at 10:15:23AM +0200, Julien Gueytat wrote:
> Just to keep you informed that a bug report has been opened to Qt:
> https://bugreports.qt.io/browse/QTBUG-52739
>
> We might save some patches in layers by solving this,
> Thanks for helping,
>
Great Julien. Here is a hint - would this help your problem?
https://lists.yoctoproject.org/pipermail/yocto/2016-February/028277.html
> Le 20/04/2016 01:46, Julien Gueytat a écrit :
> > Hi again guys,
> >
> > after more investigations:
> >
> > I found out that the default value -lEGL comes from
> > ./mkspecs/common/linux.conf which is included in
> > ./mkspecs/linux-oe-g++/qmake.conf
> >
> > linux-oe-g++ being the only generic mkspecs that should be used in Yocto
> >
> > So! At the time the configuration enters egl.pro the content of the
> > variables LIBS and QMAKE_EGL_LIBS are still a bit weird for me :
> >
> > 1- LIBS already has the content of the QMAKE_EGL_LIBS content from the
> > result of the pkg-config command.
> > 2- QMAKE_EGL_LIBS has the content of the default value found in
> > ./mkspecs/common/linux.conf
> >
> > There are two options to have it properly working:
> > - First and easy option : remove the QMAKE_EGL_LIBS default variable in
> > ./mkspecs/linux-oe-g++/qmake.conf since the good libs seems to already
> > been present in the LIBS variable.
> > - Second option : understand why the LIBS variable is already properly
> > set and why the QMAKE_EGL_LIBS properly computed in the configure and
> > present .qmake.vars is not used. (I would say that the device spec
> > overrides the one from qmake spec... I did not dig further yet.)
> >
> > Anyway I'm pretty sure the trouble comes from meta-qt5 side now. I'm
> > pretty sure meta-raspberrypi maintainers can confirm that their master
> > branch handles pkg-config stuff now.
> >
> > Thanks advance for having a look on this guys,
> > Best Regards
> >
> >
> > Le 19/04/2016 10:46, Julien Gueytat a écrit :
> > > Hi,
> > >
> > > I still can't figure out the patch to apply in meta-qt5 to get EGL
> > > support with the Raspberry.
> > >
> > > The test to check EGL does not pass and fails with the following command:
> > >
> > > arm-poky-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork
> > > -mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7
> > > --sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
> > > -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o
> > > -lGLESv2 -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> > >
> > >
> > > Here is the content of the file egl.pro:
> > >
> > > $ cat egl.pro
> > > SOURCES = egl.cpp
> > >
> > > for(p, QMAKE_LIBDIR_EGL) {
> > > exists($$p):LIBS += -L$$p
> > > }
> > >
> > > message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > > message("In egl.pro - 1: LIBS = $$LIBS")
> > >
> > > !isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
> > > !isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL
> > >
> > > message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
> > > message("In egl.pro - 2: LIBS = $$LIBS")
> > >
> > > CONFIG -= qt
> > >
> > > In the main ./configure file of qtbase:
> > >
> > > | In configure #1: QMAKE_LIBS_EGL =
> > > | In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lbcm_host -lvcos -lvchiq_arm -pthread
> > >
> > > The variable QMAKE_LIBS_EGL is set properly.
> > >
> > >
> > > In the ./config.tests/qpa/egl/egl.pro file:
> > >
> > > | Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
> > > | Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lvcos -lvchiq_arm -pthread
> > > | Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
> > > | Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
> > > -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
> > >
> > >
> > > *What I see is that:*
> > > In the configure file the variable QMAKE_LIBS_EGL is properly set
> > > through pkg-config.
> > > In the egl.pro file... The variable LIBS gets the content of
> > > QMAKE_LIBS_EGL and the variable QMAKE_LIBS_EGL gets back to its
> > > default -lEGL.
> > >
> > > In the end with have -lGLESv2 before -lEGL and this does not link.
> > >
> > > I checked also the content of .qmake.vars:
> > > grep QMAKE_LIBS_EGL .qmake.vars
> > > QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif -lbcm_host
> > > -lvcos -lvchiq_arm -pthread
> > >
> > >
> > > The command QMakeVar set QMAKE_LIBS_EGL "$QMAKE_LIBS_EGL" seems to
> > > have his job done too late...
> > >
> > > If someone has an idea to get the proper correction done...
> > >
> > > Best Regards,
> > > Julien
> > >
> > >
> > >
> >
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Andrei Gherzan
signature.asc
Description: PGP signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lis
Re: [yocto] what does ${libdir} refer to?
No, libdir is /usr/lib on the target. We never write to the host system
outside the build directory. do_install installs a lib into ${D}${libdir},
and then the contents of ${D} get split up into individual binary packages,
and those packages are then installed in a root filesystem and archived
into a rootfs image.
On Thu, Apr 21, 2016 at 8:53 AM 杜 昊 wrote:
> Hello there!
>
> I have a question about the absolute path of ${libdir}.
>
> for example in poco recipe:
>
>
> here is:
>
> PACKAGES += "${PN}-dev ${PN}-staticdev"
> FILES_${PN}-dev = "${includedir} ${libdir}/libPoco*.so ${libdir}/cmake"
> FILES_${PN}-staticdev = "${libdir}/libPoco*.a"
>
>
> i have searched for the yocto reference. In meta/conf/bitbake.conf we can
> see
>
>
> baselib = "${BASELIB}"
> BASELIB = "lib"
>
> # Path prefixes
> export exec_prefix = "/usr"
>
> # Architecture dependent paths
> export bindir = "${exec_prefix}/bin"
> export libdir = "${exec_prefix}/${baselib}"
>
> Does this mean that ${libdir} =/usr/lib in my host machine. But i
> can't find such libraries(libPoco*.so) in my host(ubuntu 14.04) under
> /usr/lib
> I think i misunderstand the absolute path of ${libdir}. Who can tell me
> the right meaning of this. Thanks for helping.
>
> regards
> hao du
>
>
> --
> ___
> 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] what does ${libdir} refer to?
Hello there!
I have a question about the absolute path of ${libdir}.
for example in poco recipe:
here is:
PACKAGES += "${PN}-dev ${PN}-staticdev"
FILES_${PN}-dev = "${includedir} ${libdir}/libPoco*.so ${libdir}/cmake"
FILES_${PN}-staticdev = "${libdir}/libPoco*.a"
i have searched for the yocto reference. In meta/conf/bitbake.conf we can see
baselib = "${BASELIB}"
BASELIB = "lib"
# Path prefixes
export exec_prefix = "/usr"
# Architecture dependent paths
export bindir = "${exec_prefix}/bin"
export libdir = "${exec_prefix}/${baselib}"
Does this mean that ${libdir} =/usr/lib in my host machine. But i can't find
such libraries(libPoco*.so) in my host(ubuntu 14.04) under /usr/lib
I think i misunderstand the absolute path of ${libdir}. Who can tell me the
right meaning of this. Thanks for helping.
regards
hao du
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Binary Configuration Support
Hej, I read that there is a way to the binary configuration ( https://wiki.yoctoproject.org/wiki/Binary_configuration_support). It is described jow this internally works. But I am missing an example how to use it praticaly. My learning system is a SAMA5D3x Eval board from Atmel. For that I am using the meta-atmel layer to generate an kernel + rootfs. Now I want to configure the network to static IPs etc. For me the binary support seems designed for that. Can you explain me, how to use it? http://stackoverflow.com/questions/36764613/how-to-configurate-yocto-builds-by-useing-the-binary-configuration Kind regards! Stefan Jaritz ESA Elektroschaltanlagen Grimma GmbH Broner Ring 30 04668 Grimma Telefon: +49 3437 9211 176 Telefax: +49 3437 9211 26 E-Mail: s.jar...@esa-grimma.de Internet: www.esa-grimma.de Geschäftsführer: Dipl.-Ing. Jörg Gaitzsch Jörg Reinker Sitz der Gesellschaft: Grimma Ust.-ID: DE 141784437 Amtsgericht: Leipzig, HRB 5159 Steuernummer: 238/108/00755 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] replace libav with ffmpeg and add a patch fixing building omxplayer after 3645b27848edd0d873925f5fa2a7686f3ff9eeb9
---
.../omxplayer/explicitly_link_with_vchostif_library.patch | 13 +
recipes-multimedia/omxplayer/omxplayer_git.bb | 5 +++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644
recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
diff --git
a/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
new file mode 100644
index 000..642f63a
--- /dev/null
+++
b/recipes-multimedia/omxplayer/omxplayer/explicitly_link_with_vchostif_library.patch
@@ -0,0 +1,13 @@
+diff --git a/Makefile b/Makefile
+index 80b63b1..bcfadfb 100644
+--- a/Makefile
b/Makefile
+@@ -51,7 +51,7 @@ version:
+ bash gen_version.sh > version.h
+
+ omxplayer.bin: version $(OBJS)
+- $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvcos -ldbus-1
-lrt -lpthread -lavutil -lavcodec -lavformat -lswscale -lswresample -lpcre
++ $(CXX) $(LDFLAGS) -o omxplayer.bin $(OBJS) -lvchiq_arm -lvchostif
-lvcos -ldbus-1 -lrt -lpthread -lavutil -lavcodec -lavformat -lswscale
-lswresample -lpcre
+ $(STRIP) omxplayer.bin
+
+ help.h: README.md Makefile
diff --git a/recipes-multimedia/omxplayer/omxplayer_git.bb
b/recipes-multimedia/omxplayer/omxplayer_git.bb
index c8251fe..c2b1342 100644
--- a/recipes-multimedia/omxplayer/omxplayer_git.bb
+++ b/recipes-multimedia/omxplayer/omxplayer_git.bb
@@ -7,8 +7,8 @@ SECTION = "console/utils"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-DEPENDS = "libpcre libav virtual/egl boost freetype dbus openssl samba libssh"
-PR = "r4"
+DEPENDS = "libpcre ffmpeg virtual/egl boost freetype dbus openssl samba libssh"
+PR = "r5"
SRCREV = "15a490b2397b358776c56b017a137c4716eb6b4e"
SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master \
@@ -19,6 +19,7 @@ SRC_URI =
"git://github.com/popcornmix/omxplayer.git;protocol=git;branch=master
file://fix-tar-command-with-DIST.patch \
file://use-native-pkg-config.patch \
file://don-t-preserve-file-attributes-when-cp.patch \
+ file://explicitly_link_with_vchostif_library.patch \
"
S = "${WORKDIR}/git"
--
2.5.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is there a known issue with how SRC_URI uses OVERRIDES to locate .scc files?
On Thu, Apr 21, 2016 at 4:59 AM, Robert P. J. Day wrote: > On Wed, 20 Apr 2016, Bruce Ashfield wrote: > > > > > > > On Wed, Apr 20, 2016 at 6:37 PM, Robert P. J. Day > wrote: > > On Wed, 20 Apr 2016, Bruce Ashfield wrote: > > > > > You haven't supplied your SRC_URI in the question ... what does > it > > > look like ? > > > > > > It has no relation to the SRC_URI, probably a run of the mill > bug in > > > the processing code. I'd suggest taking it up with Wind River > > > support. > > > > > > Alternatively, if you have this somewhere that I clone and > launch a > > > test build, I can help you out .. but I won't be able to easily > > > reproduce that situation from scratch. > > > > ok, i found what appears to be a cheap workaround for this, and > i'm > > curious if this makes any sense. recall original kernel recipe > > directory structure: > > > > linux-windriver/ > > uio.* > > ssd.* > > mxeiii/ > > mm.* > > > > when SRC_URI mentioned only that first-level stuff (uio, ssd), then > > the configure step worked fine. but as soon as i added the mm.scc > file > > to SRC_URI, it just seems that any descent into a lower-level > > directory based on OVERRIDES totally bones the search process. so, > i > > wondered, how can i work around this? > > > > oh, wait, no problem. see, all target boards are powerpc, so > > "powerpc" is one of the possible OVERRIDES. obviously, there is no > > *actual* value in using an OVERRIDE for which *every* *single* > *board* > > is compatible ... oh, wait, there is. > > > > so i restructured: > > > > linux-windriver/ > > mxeiii/ > > mm.* > > powerpc/ > > uio.* > > ssd.* > > > > it looks idiotic to take the uio.* and ssd.* content, which should > be > > generic, and deliberately put it in a subdirectory, unless that > > subdirectory represents an OVERRIDE which matches every board and, > ta > > da, solves the problem. > > > > i need a drink. > > > > > > Following up to the list. I was able to take a reproducer for this > > and indeed find some *really* old code that didn't handle a trailing > > / properly. The end result was the inability to find the > > configuration fragments that were not in subdirectories. > > just to be clear, there was no problem finding config fragments that > were not in subdirectories until i somehow triggered the bug by > *adding* an item that *was* in a subdirectory, and that's when things > went to hell. > > so the "bug" apparently never manifested itself until i triggered it > by doing something else. does that sound about right? > Correct. The subdirs were getting a trailing / and hence when the fragments were all gathered up (in case the original location is remote), they were being dumped into .kernel-meta/cfg//foo.cfg. Later on the configuration was looking for them in just /foo.cfg .. and couldn't find them. Bloody trailing slashes! Bruce > > rday -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: Preventing rebuild of dependencies
Hi, On several Yocto-based projects I've worked on, I've ended up accidentally triggering rebuilds of large packages such as QT or Chromium. The example I keep running into at the moment is whenever I modify the kernel config, I trigger Chromium to rebuild next time I rebuild the image. This means losing as much as 4 hours every time. When searching for a solution, I found other posts and the workaround usually given is not to rebuild the image after kernel changes and copy the kernel manually. That's all very well, but I'm also making changes to other parts of the system and therefore need to be able to rebuild the image without waiting for Chromium to compile. The problem seems to come down to one of Chromium's deps depending on the kernel for some headers. Now naturally changes to a dependency results in a rebuild, but I the operator know that the change in question will not have any affect. I'd like to just be able to blacklist rebuilding of Chromium and QT, but I can't find a way other than sticking in some fake rules in the Chromium recipe. In buildroot, one could often cheat by touching the relevant stamp file to make it think it had rebuilt. Is the same possible in Yocto? Note: sstate-cache is enabled. Thanks Sassan Panahinejad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build Failure Errors
Remove -Werror from CFLAGS or EXTRA_OECONF if any. On Thu, Apr 21, 2016 at 11:38 AM, Harinath maddelal wrote: > > Hi > > > Im new to Yocto. > > After downloading poky and i added our BSP package. So while trying to > compile i get the following errors > > > === > > LD init/mounts.o > LD init/built-in.o > CC mm/fadvise.o > CC arch/mips/incdhad1/diap/pllConfig.o > CC arch/mips/incdhad1/diap/dmcConfig.o > /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/incdhad1/diap/pllConfig.c:136:2: > error: 'writel' is static but used in inline function 'setPixelClock' which > is not static [-Werror] > writel(0x80030003, (void __iomem*)0xBE903064); > ^ > /home/harinathm/poky/build/tmp/work-shared/dhruva/kernel-source/arch/mips/incdhad1/diap/pllConfig.c:121:2: > error: 'writel' is static but used in inline function 'setPixelClock' which > is not static [-Werror] > writel(0x800A0003, (void __iomem*)0xBE903064); > ^ > === > > > Looks like warnings are treated as errors. How can i compress warnings being > treated as errors. > > > Can you please help me in this. > > > Attaching log.do_compile file for further reference. > > > Expecting your reply. Thanks in Advance > > > Thanks and Regards, > Harinath > > > -- > ___ > 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] is there a known issue with how SRC_URI uses OVERRIDES to locate .scc files?
On Wed, 20 Apr 2016, Bruce Ashfield wrote: > > > On Wed, Apr 20, 2016 at 6:37 PM, Robert P. J. Day > wrote: > On Wed, 20 Apr 2016, Bruce Ashfield wrote: > > > You haven't supplied your SRC_URI in the question ... what does it > > look like ? > > > > It has no relation to the SRC_URI, probably a run of the mill bug in > > the processing code. I'd suggest taking it up with Wind River > > support. > > > > Alternatively, if you have this somewhere that I clone and launch a > > test build, I can help you out .. but I won't be able to easily > > reproduce that situation from scratch. > > ok, i found what appears to be a cheap workaround for this, and i'm > curious if this makes any sense. recall original kernel recipe > directory structure: > > linux-windriver/ > uio.* > ssd.* > mxeiii/ > mm.* > > when SRC_URI mentioned only that first-level stuff (uio, ssd), then > the configure step worked fine. but as soon as i added the mm.scc file > to SRC_URI, it just seems that any descent into a lower-level > directory based on OVERRIDES totally bones the search process. so, i > wondered, how can i work around this? > > oh, wait, no problem. see, all target boards are powerpc, so > "powerpc" is one of the possible OVERRIDES. obviously, there is no > *actual* value in using an OVERRIDE for which *every* *single* *board* > is compatible ... oh, wait, there is. > > so i restructured: > > linux-windriver/ > mxeiii/ > mm.* > powerpc/ > uio.* > ssd.* > > it looks idiotic to take the uio.* and ssd.* content, which should be > generic, and deliberately put it in a subdirectory, unless that > subdirectory represents an OVERRIDE which matches every board and, ta > da, solves the problem. > > i need a drink. > > > Following up to the list. I was able to take a reproducer for this > and indeed find some *really* old code that didn't handle a trailing > / properly. The end result was the inability to find the > configuration fragments that were not in subdirectories. just to be clear, there was no problem finding config fragments that were not in subdirectories until i somehow triggered the bug by *adding* an item that *was* in a subdirectory, and that's when things went to hell. so the "bug" apparently never manifested itself until i triggered it by doing something else. does that sound about right? rday-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-qt5][meta-raspberrypi]: Qt5 with EGL support for the Raspberry through linux-oe-g++
Just to keep you informed that a bug report has been opened to Qt:
https://bugreports.qt.io/browse/QTBUG-52739
We might save some patches in layers by solving this,
Thanks for helping,
Le 20/04/2016 01:46, Julien Gueytat a écrit :
Hi again guys,
after more investigations:
I found out that the default value -lEGL comes from
./mkspecs/common/linux.conf which is included in
./mkspecs/linux-oe-g++/qmake.conf
linux-oe-g++ being the only generic mkspecs that should be used in Yocto
So! At the time the configuration enters egl.pro the content of the
variables LIBS and QMAKE_EGL_LIBS are still a bit weird for me :
1- LIBS already has the content of the QMAKE_EGL_LIBS content from the
result of the pkg-config command.
2- QMAKE_EGL_LIBS has the content of the default value found in
./mkspecs/common/linux.conf
There are two options to have it properly working:
- First and easy option : remove the QMAKE_EGL_LIBS default variable
in ./mkspecs/linux-oe-g++/qmake.conf since the good libs seems to
already been present in the LIBS variable.
- Second option : understand why the LIBS variable is already properly
set and why the QMAKE_EGL_LIBS properly computed in the configure and
present .qmake.vars is not used. (I would say that the device spec
overrides the one from qmake spec... I did not dig further yet.)
Anyway I'm pretty sure the trouble comes from meta-qt5 side now. I'm
pretty sure meta-raspberrypi maintainers can confirm that their master
branch handles pkg-config stuff now.
Thanks advance for having a look on this guys,
Best Regards
Le 19/04/2016 10:46, Julien Gueytat a écrit :
Hi,
I still can't figure out the patch to apply in meta-qt5 to get EGL
support with the Raspberry.
The test to check EGL does not pass and fails with the following command:
arm-poky-linux-gnueabi-g++ -march=armv7-a -marm -mthumb-interwork
-mfloat-abi=hard -mfpu=neon-vfpv4 -mtune=cortex-a7
--sysroot=/home/jgueytat/projects/LightPixels/poky/build/tmp/sysroots/lightpixels
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o egl egl.o
-lGLESv2 -lbcm_host -lvchostif -lvcos -lvchiq_arm -pthread -lEGL
Here is the content of the file egl.pro:
$ cat egl.pro
SOURCES = egl.cpp
for(p, QMAKE_LIBDIR_EGL) {
exists($$p):LIBS += -L$$p
}
message("In egl.pro - 1: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
message("In egl.pro - 1: LIBS = $$LIBS")
!isEmpty(QMAKE_INCDIR_EGL): INCLUDEPATH += $$QMAKE_INCDIR_EGL
!isEmpty(QMAKE_LIBS_EGL): LIBS += $$QMAKE_LIBS_EGL
message("In egl.pro - 2: QMAKE_LIBS_EGL = $$QMAKE_LIBS_EGL")
message("In egl.pro - 2: LIBS = $$LIBS")
CONFIG -= qt
In the main ./configure file of qtbase:
| In configure #1: QMAKE_LIBS_EGL =
| In configure #2: QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lbcm_host -lvcos -lvchiq_arm -pthread
The variable QMAKE_LIBS_EGL is set properly.
In the ./config.tests/qpa/egl/egl.pro file:
| Project MESSAGE: In egl.pro - 1: QMAKE_LIBS_EGL = -lEGL
| Project MESSAGE: In egl.pro - 1: LIBS = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lvcos -lvchiq_arm -pthread
| Project MESSAGE: In egl.pro - 2: QMAKE_LIBS_EGL = -lEGL
| Project MESSAGE: In egl.pro - 2: LIBS = -lEGL -lGLESv2 -lbcm_host
-lvchostif -lvcos -lvchiq_arm -pthread -lEGL
*What I see is that:*
In the configure file the variable QMAKE_LIBS_EGL is properly set
through pkg-config.
In the egl.pro file... The variable LIBS gets the content of
QMAKE_LIBS_EGL and the variable QMAKE_LIBS_EGL gets back to its
default -lEGL.
In the end with have -lGLESv2 before -lEGL and this does not link.
I checked also the content of .qmake.vars:
grep QMAKE_LIBS_EGL .qmake.vars
QMAKE_LIBS_EGL = -lEGL -lGLESv2 -lbcm_host -lvchostif -lbcm_host
-lvcos -lvchiq_arm -pthread
The command QMakeVar set QMAKE_LIBS_EGL "$QMAKE_LIBS_EGL" seems to
have his job done too late...
If someone has an idea to get the proper correction done...
Best Regards,
Julien
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
