Re: [yocto] raspberrypi3-64 target not booting

[Herve Jourdain]

Hi,

Are you using vc4 as graphics, or are you using the default userland?
If you want graphics with 64 bits, you need to use vc4.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Khem Raj
Sent: vendredi 25 août 2017 19:28
To: Bill Jenkins ; yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] raspberrypi3-64 target not booting

On Fri, Aug 25, 2017 at 10:14 AM, Bill Jenkins  wrote:
>
> On Aug 25, 2017, at 9:42 AM, Khem Raj  wrote:
>
>
> On Fri, Aug 25, 2017 at 9:39 AM Bill Jenkins  wrote:
>>
>> I am trying to just get the simple 64-bit rpi-basic-image to work, 
>> but the Raspberry Pi 3 seems to hang with the rainbow screen at startup.
>
>
> Can you plugin a serial cable and see if that worked or try to add ssh 
> daemon on target and try to ssh into pi
>>
>>
>
> That was a good call. I can login with the ssh daemon, so it does 
> successfully boot. I just cannot access it from the HDMI port. (I do 
> not have the hardware for a serial connection at the moment)
>
> Any ideas on how to get the HDMI port to function the same way as it 
> does for the 32-bit case?
>

Readding the mailing list.

what you have is exactly what I had when I submitted the port to
meta-raspberrypi. Haven;t had a chance to revisit it. but this could
be related to device tree files we are using here. I have had reports
from other devs of having been able to boot into graphics using older
kernels but I never got
that far myself.
-- 
___
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] ***SPAM*** Re: [meta-raspberrypi] Building rpi-test-image for Pi3 64 bit

[Herve Jourdain]

Hi Luca,

 

The userland libraries do not support 64 bits. It’s not just a problem of 
compiling the libraries with a 64bits compiler, it’s because they interface 
with some FW in the Videocore IV that supports only 32 bits addressing, and 
that communicates with the userland through 32 bits “pointers” (at least for 
the HW decoding parts).
And this is proprietary FW, that AFAIK will not be rebuilt to support 64 bits.

So the only thing that should be possible in 64 bits is to use the VC4 driver 
(open source), and disable the userland. The VC4 driver works fine, however you 
lose the HW decoding capabilities that the userland provides (H.264/MPEG2, + 
some audio).

As a consequence, anything that uses those or other userland features 
(gst-omx/omxplayer/…) can’t be compiled or run in 64bits.

What should work, though, is Wayland in 64bits using VC4 driver (at least, I 
had that working with a previous kernel version). But anything playing AV will 
have to resort back to using SW decode, AFAIK.

 

Cheers,
Herve

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Luca Carlon
Sent: mercredi 3 mai 2017 18:19
To: Khem Raj 
Cc: yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi] Building rpi-test-image for 
Pi3 64 bit

 

What I'd like to be able to do is setup is a 64bit system including the 
libraries from the userland repo: https://github.com/raspberrypi/userland. I 
suspect vc4graphic is something different, isn't it?
But maybe you're right and those libs will never be built, as I see that 
according to https://github.com/raspberrypi/userland/pull/347 not everything 
builds in userland. In the recipe I however see that the ARM64 macro is defined 
and so I'm asking myself which libraries are currently supported and which are 
not. Anyone who knows?
Thank you!

Luca

 

On Wed, May 3, 2017 at 2:35 PM, Khem Raj  > wrote:

 

On Wed, May 3, 2017 at 8:28 AM Luca Carlon  > wrote:

Hello,

thank you for your help. I followed your advice and I'm now able to build 
rpi-test-image for raspberrypi2 and raspberrypi3. When I try raspberrypi3-64 
instead I'm getting a few errors. I fixed one build error, but then I got: 
https://pastebin.com/pL2mei9s. It seems that those libs were not added to the 
sysroot for some reason. I think those come from the userspace package 
probably. As it seems to work for the other machines I'm trying to determine 
what difference raspberrypi3-64 is introducing but for the moment I'm failing. 
Any idea what is causing this error? Are you able to build rpi-test-image? 
rpi-basic-image seems to work but not rpi-test-image, which includes omxplayer 
and other libs that I need like libEGL, libGLESv2, libopenmax etc...

 

These are my current conf files:

 

https://pastebin.com/LJnRfDUj

https://pastebin.com/axt9RLQS

 

Any idea why those libs cannot be found?

Thank you!

Regards.

 

I don't know if anyone here has got GUI up with rpi64 using yocto yet however 
you could try to use vc4 graphics drivers by adding "vc4graphic" to 
MACHINE_FEATURES

 

Luca

 

On Sat, Apr 29, 2017 at 9:40 AM, Andrea Galbusera  > wrote:

On Sat, Apr 29, 2017 at 2:39 AM, Luca Carlon  > wrote:

Hello,
thank you very much for your advice. It seems I can build both a minimal image 
and rpi-basic-image. I would like to test to see if the Pi is able to boot with 
these images but it seems that the images directory does not contain any sdimg 
file. By reading https://github.com/agherzan/meta-raspberrypi and 
https://github.com/Nuand/bladeRF/wiki/Creating-Linux-based-Embedded-System-Images-with-Yocto
 it seems I should find a sdimg file to flash to the sdcard. I suppose this 
image file contains both the boot and rootfs partitions. But it seems I do not 
see this image at all, this is a list of what I can see in 
tmp/deploy/images/raspberrypi3-64: https://pastebin.com/8XsRHzUY. I see the 
rootfs filesystem that I can extract in a partition, but not the boot partition 
the Pi needs. Maybe I'm missing some line in the conf files?

 

If you are using the local.conf you previously posted, the line:

 

IMAGE_FSTYPES = "tar.xz"

 

is overriding default configuration from rpi-base.inc in meta-raspberrypi which 
is:

 

IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"

 

You can also consider using wic image format to generate a flashable image (see 
Yocto documentation on how to do that).

 

--
___
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] gles2 on raspi3

[Herve Jourdain]

Hi Trevor,

I agree with you that VC4 is easier to work with - and can be patched if there 
are issues.
But normally you lose the H.264 and MPEG2 HW decoders, and a bunch of audio 
codecs, provided by the userland/omx.
Depending on what you're doing, you may or may not notice the difference. But 
I'm not sure how well you can handle 1080p30 or 1080p60 in H.264 using only 
ffmpeg - if you're using chromium, that's what you should be using I guess.
My personal preference would be to use VC4, and that's what I do most of the 
time, but there is still a limitation for the moment, that I just wanted to 
point out.
And that's why I think we can't do only VC4, and probably have to keep userland 
a while longer.

Cheers,
Herve

-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: jeudi 20 avril 2017 09:13
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: 'Andreas Müller' <schnitzelt...@googlemail.com>; 'Yocto Project' 
<yocto@yoctoproject.org>
Subject: Re: [yocto] [meta-raspberrypi] gles2 on raspi3

On Thu 2017-04-20 @ 05:41:44 AM, Herve Jourdain wrote:
> Yes, VC4 indeed works for both 32bits and 64bits. It was first introduced  .
> for 32bits, actually Regarding why still using userland: at this point in  .
> time, we have accelerated HW codec (H.264, MPEG2, some audio) only if using.
> userland If one doesn't need that, then VC4 is, in my opinion, the way to  .
> go. Otherwise, userland still needs to be used .

What decoder is needed to play youtube videos?

Using Andreas' meta-raspi-light (which removes userland and only uses vc4) I've 
spent the last hour or so watching youtube videos from my raspberrypi3 (32-bit 
build) in chromium, accelerated, with sound (both via the HDMI and the jack), 
both on the big monitor and the 7" waveshare touchscreen. Not to mention I can 
now run openGL and GLESx apps accelerated.

I wasn't able to do that with userland. In fact, it was quite a struggle just 
to get it to build!

Maybe I did something wrong with userland, but vc4 is successful, and certainly 
easier to work with.

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

Re: [yocto] ***SPAM*** Re: [meta-raspberrypi] gles2 on raspi3

[Herve Jourdain]

Hi Andreas,

Yes, VC4 indeed works for both 32bits and 64bits. It was first introduced for 
32bits, actually.
Regarding why still using userland: at this point in time, we have accelerated 
HW codec (H.264, MPEG2, some audio) only if using userland.
If one doesn't need that, then VC4 is, in my opinion, the way to go. Otherwise, 
userland still needs to be used.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Andreas Müller
Sent: samedi 15 avril 2017 20:09
To: Trevor Woerner 
Cc: Yocto Project 
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi] gles2 on raspi3

On Sat, Apr 15, 2017 at 6:35 PM, Trevor Woerner  wrote:
> On Sat 2017-04-15 @ 04:46:14 PM, Andreas Müller wrote:
>> > Does anyone have any of these (or something else?) working?
>> >
>> Ehm userland gles2 on X11? I would not expect that to work. Experts 
>> correct me but userland acceleration works for fullscreen apps only.
>
> I have made this work before (which, as you'll see later in this 
> email, doesn't imply that's how it's supposed to work!):
> https://twoerner.blogspot.ca/2015/09/oe-build-of-glmark2-running-on.ht
> ml
>
> Oh, and I did try both with and without "--fullscreen".
>
>> Why not using FOSS VC4+mesa?
>
> Now's probably a good time to point out I only have a vague idea of 
> what I'm doing ;-)
>
> I didn't try vc4 because the raspi recipes implied (to me) it was for 
> aarch64 only. The "vc4graphics" MACHINE_FEATURES is only added for 
> raspberrypi3-64.
> I'll give this a try though.
Oh yes you are right - it is long time ago - maybe this was one of the reasons 
for my vc4-only fork. I thought it is an option set in local.conf.
>
> Here's another question that only shows my inexperience in this 
> area... does using mesa always imply software-only rendering? mali 
> (for example) would be hardware rendering (though through a binary 
> blob) and mesa is the software fallback?
I am also no expert here but Mesa is the open source userspace part for 
accelerated graphics. Mesa-SW rendering driver is a fallback in case no driver 
is supported/implemented. This is what you have seen for glmark2. Since the 
VC4-Mesa was implemented, for me RaspberryPi turned into the reference hardware 
regarding graphics. You can have accelerated X11 + wayland in one image without 
any trouble with proper working modesetting (and HDMI sound is on it's way). 
I've never had this before on other machines where closed source blobs do 
graphics acceleration. Either you have fb only (no X11/wayland) or you have to 
decide either X11 or wayland - and worst: With every new version of xserver you 
have to expect trouble.
>
> By the way, with my current setup I have been able to run openGL apps (e.g.
> glmark2 by itself) albeit most definitely non-accelerated!
mesa-gl builds swrast - mentioned above
>
> A lot of google searches talk about setting environment variables. Are 
> there any that might apply?
>
For the first shot I would add vc4graphics to MACHINE_FEATURES in 
raspberrypi3.conf. The required settings should happen (see recipe rpi-config).

In the long run I would start a discussion:

* Mesa/VC4 is not a machine feature only available on 64Bit Pi3 only:
It is common to all version of RaspberryPi. Using mesa should be a decision 
easily selected by a setting somewhere. The only reason 64Bit
Pi3 gets VC4 by default is that userland is not working for 64Bit - see commit 
9d418db5ed2962821987ac90c07c3a61e40c0814)
* Why still use userland? Dropping it would make things MUCH easier:
All the decisions based vc4graphics in MACHINE_FEATURES could be removed 
(that's what my fork does)

Andreas
--
___
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] ***SPAM*** Re: [meta-raspberrypi][morty][PATCH 4/6] linux-raspberrypi: Drop v4.8

[Herve Jourdain]

Hi,

The problem with 4.8 is that because of the constant rebasing in the 
downstream, it will get broken fast.
So someone will have to maintain it and constantly update it, and if we don't 
do it for master, it's unlikely to be done on Morty.
At some point, 4.8 will stop changing, but we're not there yet.
Right now, 4.4 is stable in downstream, and it seems 4.7 is also - at least 
4.7.10 compiles.
If we don't want to keep 4.7 in Morty, the best bet is probably 4.4 + 4.9, 
knowing there'll be a lot of updates in 4.9 - but they'll follow the ones in 
master.

Cheers,
Herve

> On 19 Jan 2017, at 20:55, Andrei Gherzan  wrote:
> 
>> On Thu, Jan 19, 2017 at 12:41 PM, Paul Barker  wrote:
>>> On 19 January 2017 12:07:11 GMT+00:00, Andrei Gherzan  
>>> wrote:
>>> On Thu, Jan 19, 2017 at 12:03 PM, Paul Barker 
>>> wrote:
 On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan
>>>  wrote:
> From: Paul Barker 
> 
> Signed-off-by: Paul Barker 
> ---
> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8 
> 1 file changed, 8 deletions(-)
> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> deleted file mode 100644
> index be25e65..000
> --- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
> +++ /dev/null
> @@ -1,8 +0,0 @@
> -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
> -
> -LINUX_VERSION ?= "4.8.16"
> -
> -SRCREV = "061dccce6cf6705bbb5da29a643f4b0ad1d11630"
> -SRC_URI =
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y
>>> \
> -"
> -require linux-raspberrypi.inc
 
 I'm not sure on this one. I don't think we should drop kernel
>>> versions from a stable branch unless they're broken. Can we hold off on
>>> this and I'll have a look at it tomorrow.
 
 (Resending as I mis-clicked and didn't do reply all)
>>> 
>>> I don't see the benefit in keeping 4.8 and 4.9. The default + the
>>> latest should be enough. Default would give stability and suitable for
>>> production while latest will give new features.
>>> 
>>> BTW I already removed 4.8 from master.
>>> 
>> 
>> Agreed for master. I'm just wondering if we want to leave 4.8 on morty (if 
>> it currently builds) in case anyone depends on that version.
>> 
>> I can see the other side though - if you need a stable branch of 
>> openembedded you should probably also use a linux-raspberrypi version that's 
>> stable.
> 
> I'll try to compile and not remove it if it compiles. Doesn't hurt to
> leave it there anyway.
> 
> --
> Andrei Gherzan
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

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

[yocto] [meta-raspberrypi][PATCH] Add recipe to build qtbase for raspberrypi out of the box.

[Herve Jourdain]

Supports different EGLFS_DEVICE_INTEGRATION for userland or vc4

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-qt/qt5/qtbase_%.bbappend | 10 ++
 1 file changed, 10 insertions(+)
 create mode 100644 recipes-qt/qt5/qtbase_%.bbappend

diff --git a/recipes-qt/qt5/qtbase_%.bbappend b/recipes-qt/qt5/qtbase_%.bbappend
new file mode 100644
index 000..aebcaf9
--- /dev/null
+++ b/recipes-qt/qt5/qtbase_%.bbappend
@@ -0,0 +1,10 @@
+PACKAGECONFIG_GL_rpi = "gles2 eglfs"
+DEPENDS_${PN}_append_rpi = " virtual/egl"
+
+OE_QTBASE_EGLFS_DEVICE_INTEGRATION = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', 'eglfs_kms', 'eglfs_brcm', d)}"
+
+do_configure_prepend() {
+# Add the appropriate EGLFS_DEVICE_INTEGRATION, depending if using VC4 or 
USERLAND
+echo "EGLFS_DEVICE_INTEGRATION = ${OE_QTBASE_EGLFS_DEVICE_INTEGRATION}" > 
${S}/mkspecs/oe-device-extra.pri
+}
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH] Fix compilation of Weston when using USERLAND: kms PACKAGECONFIG must be removed

[Herve Jourdain]

When building weston with userland, there is an error at configuration time:
| checking for DRM_COMPOSITOR... no
| configure: error: Package requirements (libudev >= 136 libdrm >= 2.4.30 gbm 
mtdev >= 1.1.0) were not met:
| 
| No package 'gbm' found
This is due to kms being enabled by default in the PACKAGECONFIG, which 
triggers --enable-drm-compositor, which requires gbm [vc4 is kms-based, not 
userland]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/wayland/weston_%.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-graphics/wayland/weston_%.bbappend 
b/recipes-graphics/wayland/weston_%.bbappend
index f2cb7aa..f36bd32 100644
--- a/recipes-graphics/wayland/weston_%.bbappend
+++ b/recipes-graphics/wayland/weston_%.bbappend
@@ -1,6 +1,6 @@
 EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', '', ' --enable-rpi-compositor 
WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
 
-PACKAGECONFIG_remove_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', 'fbdev', '', d)}"
+PACKAGECONFIG_remove_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', 'fbdev', 'kms', d)}"
 
 EXTRA_OECONF += "--disable-xwayland-test \
  --disable-simple-egl-clients \
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7 and 4.8

[Herve Jourdain]

Hi Gary,

You get this because the patch to the latest 4.7 version have not been
merged...
4.7 has been stable for some time now, unlike 4.8 - and 4.9 will probably
have some similar issues, basically the downstream is heavily rebasing, so
revisions numbers are not reliable anymore.

I'm OK to remove 4.7, since I've branched it - and mine is working fine :)
I have no problem removing 4.8, since I moved from 4.7 to 4.9.

But I believe we might also want to remove 4.1, because it's really very
old, and select the next non-LTS version instead.
That would make it 4.4, 4.9 and next-kernel.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: lundi 16 janvier 2017 15:48
To: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7
and 4.8

On 2017-01-16 08:26, Paul Barker wrote:
> As discussed recently on the list, we can just keep LTS versions now 
> that v4.9 is available.
>
> I'm sending these so anyone who still needs v4.7 or v4.8 can shout 
> 'stop!' before we remove them.
>
> Paul Barker (2):
>   linux-raspberrypi: Drop v4.7
>   linux-raspberrypi: Drop v4.8
>
>  .../0001-fix-dtbo-rules.patch  | 44
--
>  recipes-kernel/linux/linux-raspberrypi_4.7.bb  |  9 -
>  recipes-kernel/linux/linux-raspberrypi_4.8.bb  |  8 
>  3 files changed, 61 deletions(-)
>  delete mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
>  delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.7.bb
>  delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
>

+1 at least for 4.7 given that with today's repo I get this:

ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
do_kernel_version_sanity_check: Package Version
(4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built (4.7.10).
Please update the PV variable to match the kernel source.
ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
do_kernel_version_sanity_check: Function failed: 
do_kernel_version_sanity_check (log file is located at
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_ch
eck.27925)
ERROR: Logfile of failure stored in: 
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_version_sanity_ch
eck.27925
ERROR: Task
(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi_4.7.bb:do_kernel_version_sanity_check)
failed with exit code '1'


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
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 0/2] Drop kernel versions 4.7 and 4.8

[Herve Jourdain]

Hi Gary,

I believe that we will see for 4.9 the same issues we had with 4.8, heavy
rebasing from the downstream.
I'm currently working with the upstream - plus patches - and I plan to have
a yocto build that would take the upstream source and add some patches,
instead of taking the downstream as a reference.
Is this an approach that could be interesting to people using yocto and
RaspberryPi? Any thoughts on that? Or another solution to remove the
dependency to the downstream and its constant rebasing?

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: lundi 16 janvier 2017 15:52
To: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 0/2] Drop kernel versions 4.7
and 4.8

On 2017-01-16 15:48, Gary Thomas wrote:
> On 2017-01-16 08:26, Paul Barker wrote:
>> As discussed recently on the list, we can just keep LTS versions now 
>> that v4.9 is available.
>>
>> I'm sending these so anyone who still needs v4.7 or v4.8 can shout 
>> 'stop!' before we remove them.
>>
>> Paul Barker (2):
>>   linux-raspberrypi: Drop v4.7
>>   linux-raspberrypi: Drop v4.8
>>
>>  .../0001-fix-dtbo-rules.patch  | 44
--
>>  recipes-kernel/linux/linux-raspberrypi_4.7.bb  |  9 -
>>  recipes-kernel/linux/linux-raspberrypi_4.8.bb  |  8 
>>  3 files changed, 61 deletions(-)
>>  delete mode 100644 
>> recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
>>  delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.7.bb
>>  delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
>>
>
> +1 at least for 4.7 given that with today's repo I get this:
>
> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0 
> do_kernel_version_sanity_check: Package Version
> (4.7.7+gitAUTOINC+c2cbd9c611) does not match of kernel being built 
> (4.7.10). Please update the PV variable to match the kernel source.
> ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+c2cbd9c611-r0
do_kernel_version_sanity_check: Function failed:
> do_kernel_version_sanity_check (log file is located at
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux
> -raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_versi
> on_sanity_check.27925)
>
> ERROR: Logfile of failure stored in:
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux
> -raspberrypi/1_4.7.7+gitAUTOINC+c2cbd9c611-r0/temp/log.do_kernel_versi
> on_sanity_check.27925
>
> ERROR: Task
> (/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-
> raspberrypi_4.7.bb:do_kernel_version_sanity_check)
> failed with exit code '1'
>


However, there is this error when I tried to switch to 4.9:
ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch: Fetcher
failure: Unable to find revision
4052b0da7dbab0df22ca8733cf50b3e573e221e0 in branch rpi-4.9.y even from
upstream
ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch: Fetcher
failure for URL: 
'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y'.
Unable to fetch URL from any source.
ERROR: linux-raspberrypi-1_4.9.2+gitAUTOINC+4052b0da7d-r0 do_fetch: Function
failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.9.2+gitAUTOINC+4052b0da7d-r0/temp/log.do_fetch.13098
ERROR: Task
(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi_4.9.bb:do_fetch) failed with exit code '1'

Using meta-raspberrypi:e1f69daa805cb02ddd123ae2d4d48035cb5b41d0

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
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] ***SPAM*** Re: [meta-raspberrypi][PATCH] gstreamer1.0-plugins-bad: Don't hard wire use of userland

[Herve Jourdain]

Hi Gary,

That was a pretty crude way of doing something for testing purpose.
If it works, obviously we should consider changing that in .bbappend in the
meta-raspberrypi layer, and not outside.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: mercredi 7 décembre 2016 11:25
To: yocto@yoctoproject.org
Subject: Re: [yocto] ***SPAM*** Re: [meta-raspberrypi][PATCH]
gstreamer1.0-plugins-bad: Don't hard wire use of userland

On 2016-12-06 19:22, Herve Jourdain wrote:
> Hi Gary,
>
> Could you try a local to your layer 
> gstreamer1.0-plugins-bad_%.bbappend,
> that would contain:
> PACKAGECONFIG_remove_rpi = " dispmanx"
> And see if it solves your problem?

Yes, it does solve the problem, thanks.  Although written this way and
putting it in local.conf forced every package that uses PACKAGECONFIG to be
rebuilt :-(

Perhaps a softer approach might be:
   PACKAGECONFIG_remove_pn-gstreamer1.0-plugins-bad = "dispmax"

Too bad though that this needs to be disabled to get X11 to work as it would
seem to be very useful in a high-need graphic environment.

>
> I've never built for "vc-graphics-hardfp", as I'm not sure if there 
> are benefits in using it over either using the userland or vc4, so I'm 
> not sure whether it can work without dispmanx, nor why it would not 
> compile with dispmanx enabled.
> But if this works, then we might need to consider to add an additional 
> case for not enabling dispmanx.
>
> Cheers,
> Herve
>
> -Original Message-
> From: Gary Thomas [mailto:g...@mlbassoc.com]
> Sent: mardi 6 décembre 2016 16:58
> To: Andrei Gherzan <and...@gherzan.ro>
> Cc: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
> Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi][PATCH]
> gstreamer1.0-plugins-bad: Don't hard wire use of userland
>
> On 2016-12-06 16:48, Andrei Gherzan wrote:
>> On Tue, Dec 06, 2016 at 04:02:20PM +0100, Gary Thomas wrote:
>>> On 2016-12-06 13:45, Herve Jourdain wrote:
>>>> Hi Gary,
>>>>
>>>> But dispmanx is really only provided by userland, it does not exist 
>>>> in other flavors of egl/libgles.
>>>> Actually, dispmanx should not be selected in PACKAGECONFIG if 
>>>> userland is not in use for EGL/GLES.
>>>
>>> Fine, but I'm looking for a solution where I can choose to use 
>>> vc-graphics-hardfp so X11 works again and I can also have gst-player 
>>> which depends on gstreamer-1.0-bad
>>>
>>> Any ideas?
>>>
>>
>> Disabling dispamanx is not working?
>
> How might I do that?  It's not clear from [at least] that recipe.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
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] ***SPAM*** Re: [meta-raspberrypi] Current master broken

[Herve Jourdain]

Sorry, a bit tired...
I meant we need to track the changes happening to the versions we decide we
want to support, and update the recipes accordingly.
My understanding is we're interested in 4.4, 4.8 and 4.9. And I have a
personal interest in 4.7 for the moment, so I can try to keep the 4.7 recipe
up to date with the changes.
If 4.4 is "stable", then we need some people to focus on tracking the
changes happening on 4.8 and 4.9.

Cheers,
Herve

-Original Message-
From: Andrei Gherzan [mailto:and...@gherzan.ro] 
Sent: mardi 6 décembre 2016 19:11
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: 'Khem Raj' <raj.k...@gmail.com>; yocto@yoctoproject.org; 'Gary Thomas'
<g...@mlbassoc.com>
Subject: Re: ***SPAM*** Re: [yocto] [meta-raspberrypi] Current master broken

On Tue, Dec 06, 2016 at 07:04:31PM +0100, Herve Jourdain wrote:
> Hi Andrei,
>
> But I believe that the core of the problem is not necessarily the 
> patch in oe-core to detect the kernel version itself, but like Khem 
> mentioned the fact that a "well known" SRCREV is only valid for a 
> brief period of time under the RPI tree "constant" rebasing we've been
experiencing lately.
> So basically, the SRCREV that is used is not corresponding to what it 
> used to be, if it's still there in the tree, and the oe-core detects 
> that - the SRCREV thought it was one version of the kernel, and it 
> just happened that it corresponds to a different codebase with a different
linux version.
> Killing the error reporting by a patch will probably not prevent the 
> mismatch happening behind the scene.
> So like Khem mentioned, either we find a way to "prevent" the rebasing 
> at the source, or we need to track down every version we want to 
> support, and update SRCREV and corresponding kernel version for those.

Got it now. What do you mean by "track down every version we want"?
--
Andrei Gherzan

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

Re: [yocto] ***SPAM*** Re: [meta-raspberrypi][PATCH] gstreamer1.0-plugins-bad: Don't hard wire use of userland

[Herve Jourdain]

Hi Gary,

Could you try a local to your layer gstreamer1.0-plugins-bad_%.bbappend,
that would contain:
PACKAGECONFIG_remove_rpi = " dispmanx"
And see if it solves your problem?

I've never built for "vc-graphics-hardfp", as I'm not sure if there are
benefits in using it over either using the userland or vc4, so I'm not sure
whether it can work without dispmanx, nor why it would not compile with
dispmanx enabled.
But if this works, then we might need to consider to add an additional case
for not enabling dispmanx.

Cheers,
Herve

-Original Message-
From: Gary Thomas [mailto:g...@mlbassoc.com] 
Sent: mardi 6 décembre 2016 16:58
To: Andrei Gherzan <and...@gherzan.ro>
Cc: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi][PATCH]
gstreamer1.0-plugins-bad: Don't hard wire use of userland

On 2016-12-06 16:48, Andrei Gherzan wrote:
> On Tue, Dec 06, 2016 at 04:02:20PM +0100, Gary Thomas wrote:
>> On 2016-12-06 13:45, Herve Jourdain wrote:
>>> Hi Gary,
>>>
>>> But dispmanx is really only provided by userland, it does not exist 
>>> in other flavors of egl/libgles.
>>> Actually, dispmanx should not be selected in PACKAGECONFIG if 
>>> userland is not in use for EGL/GLES.
>>
>> Fine, but I'm looking for a solution where I can choose to use 
>> vc-graphics-hardfp so X11 works again and I can also have gst-player 
>> which depends on gstreamer-1.0-bad
>>
>> Any ideas?
>>
>
> Disabling dispamanx is not working?

How might I do that?  It's not clear from [at least] that recipe.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world


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

Re: [yocto] ***SPAM*** Re: [meta-raspberrypi] Current master broken

[Herve Jourdain]

Hi Andrei,

But I believe that the core of the problem is not necessarily the patch in
oe-core to detect the kernel version itself, but like Khem mentioned the
fact that a "well known" SRCREV is only valid for a brief period of time
under the RPI tree "constant" rebasing we've been experiencing lately.
So basically, the SRCREV that is used is not corresponding to what it used
to be, if it's still there in the tree, and the oe-core detects that - the
SRCREV thought it was one version of the kernel, and it just happened that
it corresponds to a different codebase with a different linux version.
Killing the error reporting by a patch will probably not prevent the
mismatch happening behind the scene.
So like Khem mentioned, either we find a way to "prevent" the rebasing at
the source, or we need to track down every version we want to support, and
update SRCREV and corresponding kernel version for those.

Cheers,
Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Andrei Gherzan
Sent: mardi 6 décembre 2016 16:29
To: Khem Raj 
Cc: yocto@yoctoproject.org; Gary Thomas 
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi] Current master broken

On Mon, Dec 5, 2016 at 4:50 PM, Khem Raj  wrote:
> On Sun, Dec 4, 2016 at 10:03 PM, Gary Thomas  wrote:
>> On 2016-12-05 01:54, Andrei Gherzan wrote:
>>>
>>> Hi Gary,
>>>
>>>
>>> On Sat, Dec 3, 2016 at 2:16 PM, Paul Barker 
wrote:

 On Sat, 3 Dec 2016 08:33:40 +0100
 Gary Thomas  wrote:

> I'm currently unable to build for the RaspberryPi-3 using the 
> master
> branch:
>
> Build Configuration:
> BB_VERSION= "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "arm-amltd-linux-gnueabi"
> MACHINE   = "raspberrypi3"
> DISTRO= "amltd"
> DISTRO_VERSION= "2.2+snapshot-20161202"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> callconvention-hard cortexa7"
> TARGET_FPU= "hard"
> meta  = "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a"
> meta-amltd= "master:074120ab3a82cea0ac50d4e9eec89130a860a4fa"
> meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"
>
> Initialising tasks: 100%
> |#| Time:
> 0:00:00
> Checking sstate mirror object availability: 100%
> |#| Time: 0:00:00
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0
> do_kernel_metadata: Function failed: do_kernel_metadata (log file 
> is located at
>
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/l
> inux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_ker
> nel_metadata.5647)
> ERROR: Logfile of failure stored in:
>
> /build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/l
> inux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_ker
> nel_metadata.5647
> Log data follows:
> | DEBUG: Executing shell function do_kernel_metadata
> | [ERROR]: processing of file /tmp/tmp.bXPr8PVPz3 failed
> |
>
/build/rpi3_2016-09-13/tmp/sysroots/x86_64-linux/usr/bin/scc-cmds/patch.cmd:
> line 29: : No such file or directory
> |
> | Context around the error is:
> |
> | #
> | prefix
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
> ux-raspberrypi/
> | kconf non-hardware
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
> ux-raspberrypi/defconfig
> | prefix
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
> ux-raspberrypi-4.4/
> | patch
>
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
> | # run time: 0 seconds
> | # processed files:
> | # _cfg
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
> ux-raspberrypi/defconfig
> | # _cfg
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/lin
> ux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> |
> | See pre-processed file /tmp/tmp.bXPr8PVPz3 for more details # # 
> | scc v0.8 # processed: Fri Dec  2 04:12:25 CET 2016 # # This is a 
> | scc output file, do not edit #
> | [ERROR]: processing of file /tmp/tmp.eTLAT789Q2 failed # 
> | _reloc_dir
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
> | # _reloc_dir
> /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
> |
>

Re: [yocto] ***SPAM*** [meta-raspberrypi] Qt EGLFS frozen on VC4

[Herve Jourdain]

Hi Gerhard,

 

Could you please provide a bit more information, like the kernel you’re
building against, the kind of features you’re using in QT, if you’re using
GStreamer as well, if you’re playing video, versions of the
meta-raspberrypi/yocto/openembedded layers, etc…

I’m not sure I can help, but without additional information it would be
second-guessing at best.

 

Cheers,

Herve

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gerhard de Clercq
Sent: mardi 6 décembre 2016 15:18
To: Yocto list discussion 
Subject: ***SPAM*** [yocto] [meta-raspberrypi] Qt EGLFS frozen on VC4

 

When I build Qt5 for my RPi 3 so that it uses EGLFS on VC4  (all using
Yocto) then everything seems to go well initially and I can even get a
program to launch but it then seems to render only one frame and then stay
there. There is no response to user input and applications that are supposed
to have constant animations do not change. It is also not possible to
terminate the application with ^c.

 

I'm not even sure where to ask for support because I have no idea if this is
a problem with Qt, VC4 or Yocto. Does anyone here have a clue of what might
be wrong?

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

Re: [yocto] [meta-raspberrypi][PATCH] gstreamer1.0-plugins-bad: Don't hard wire use of userland

[Herve Jourdain]

Hi Gary,

But dispmanx is really only provided by userland, it does not exist in other
flavors of egl/libgles.
Actually, dispmanx should not be selected in PACKAGECONFIG if userland is
not in use for EGL/GLES.

Cheers,

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: mardi 6 décembre 2016 10:34
To: yocto@yoctoproject.org
Cc: Gary Thomas 
Subject: [yocto] [meta-raspberrypi][PATCH] gstreamer1.0-plugins-bad: Don't
hard wire use of userland

Selection of the libgl packages should be by virtual/XXX.  Using 'userland'
directly can lead to build conflicts and make the system unbuildable.

Signed-off-by: Gary Thomas 
---
 recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git
a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
index 7292f90..432869d 100644
--- a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
@@ -9,4 +9,4 @@ PACKAGECONFIG_GL_rpi = "egl gles2"
 
 PACKAGECONFIG_append_rpi = " hls libmms faad"
 
-PACKAGECONFIG[dispmanx] = "--enable-dispmanx,--disable-dispmanx,userland"
+PACKAGECONFIG[dispmanx] = "--enable-dispmanx,--disable-dispmanx,virtual/egl
virtual/libgles2"
-- 
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-raspberrypi] Current master broken

[Herve Jourdain]

Hi Gary,

Regarding the 4.7, did you try the patch I sent 1 week ago?
It uses 4.7.10, with revision " e7fa325a40f260ed9fb86391a0b65150eba8c112",
and is known to work.
The "good" revision you mention is known to not be "good" anymore.

The patch can be found on the list, or on
https://github.com/hjourdain/meta-raspberrypi.

Hope it helps,

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: samedi 3 décembre 2016 08:34
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi] Current master broken

I'm currently unable to build for the RaspberryPi-3 using the master branch:

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "raspberrypi3"
DISTRO= "amltd"
DISTRO_VERSION= "2.2+snapshot-20161202"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
cortexa7"
TARGET_FPU= "hard"
meta  = "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a"
meta-amltd= "master:074120ab3a82cea0ac50d4e9eec89130a860a4fa"
meta-raspberrypi  = "master:44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9"

Initialising tasks: 100%
|#| Time:
0:00:00 Checking sstate mirror object availability: 100%
|#| Time: 0:00:00
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0
do_kernel_metadata: Function failed: do_kernel_metadata (log file is located
at
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647)
ERROR: Logfile of failure stored in: 
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647
Log data follows:
| DEBUG: Executing shell function do_kernel_metadata
| [ERROR]: processing of file /tmp/tmp.bXPr8PVPz3 failed
| /build/rpi3_2016-09-13/tmp/sysroots/x86_64-linux/usr/bin/scc-cmds/patc
| h.cmd: line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/
| kconf non-hardware
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi-4.4/
| patch
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 0 seconds
| # processed files:
| # _cfg
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| # _cfg 
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-r
| aspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.bXPr8PVPz3 for more details # # scc 
| v0.8 # processed: Fri Dec  2 04:12:25 CET 2016 # # This is a scc 
| output file, do not edit #
| [ERROR]: processing of file /tmp/tmp.eTLAT789Q2 failed # _reloc_dir 
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
| # _reloc_dir 
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux
| /build/rpi3_2016-09-13/tmp/sysroots/x86_64-linux/usr/bin/scc-cmds/patc
| h.cmd: line 29: : No such file or directory
|
| Context around the error is:
|
| #
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/
| kconf non-hardware
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| prefix
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi-4.4/
| patch
"/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi-4.4/0001-fix-dtbo-rules.patch"
| # run time: 1 seconds
| # processed files:
| # _cfg
/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspber
rypi/defconfig
| # _cfg 
| /local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-r
| aspberrypi-4.4/0001-fix-dtbo-rules.patch
|
| See pre-processed file /tmp/tmp.eTLAT789Q2 for more details
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_metadata (log file is located at
/build/rpi3_2016-09-13/tmp/work/raspberrypi3-amltd-linux-gnueabi/linux-raspb
errypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_kernel_metadata.5647)
ERROR: Task
(/local/poky-cutting-edge/meta-raspberrypi/recipes-kernel/linux/linux-raspbe
rrypi_4.4.bb:do_kernel_metadata)
failed with exit code '1'

I also tried kernel version 4.7:
ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: Fetcher
failure: Unable to find revision a45a35c08598b23f9fd82e49c83b46c7d536244f in
branch rpi-4.7.y even 

Re: [yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Hi Trevor,

No, that would be me missing a patch in my branch... :(
It should be 4.7.10, and it did compile yesterday.
My mistake, I'm adding that right now, please retry.

Herve

-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: mardi 22 novembre 2016 19:30
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and 
add raspberrypi3-64.conf

On Tue 2016-11-22 @ 05:23:49 PM, Herve Jourdain wrote:
> I didn't have any such branch, but I've created them now.
> They are located at: https://github.com/hjourdain/meta-raspberrypi and 
> https://github.com/hjourdain/openembedded-core.
> I've just pushed my patches there. I've not tested out of those repositories 
> yet, but I did test those patches before, and they were working, so hopefully 
> everything will be alright.

It looks like the raspberry pi's linux tree has been rebased again :-(

ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: 
Fetcher failure: Unable to find revision 
a45a35c08598b23f9fd82e49c83b46c7d536244f in branch rpi-4.7.y even from upstream
ERROR: linux-raspberrypi-1_4.7.7+gitAUTOINC+a45a35c085-r0 do_fetch: 
Fetcher failure for URL: 
'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.7.y'. Unable 
to fetch URL from any source.

Checking out the rpi-4.7.y branch of git://github.com/raspberrypi/linux.git
doesn't give a a45a35c08598b23f9fd82e49c83b46c7d536244f revision. Also, the 
HEAD of that branch is 4.7.10. Any idea how far back I have to go to find 
4.7.7? Or maybe I should just try 4.7.10?

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

Re: [yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Hi Trevor,

I didn't have any such branch, but I've created them now.
They are located at: https://github.com/hjourdain/meta-raspberrypi and 
https://github.com/hjourdain/openembedded-core.
I've just pushed my patches there. I've not tested out of those repositories 
yet, but I did test those patches before, and they were working, so hopefully 
everything will be alright.

Cheers,

Herve

-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: mardi 22 novembre 2016 16:10
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and 
add raspberrypi3-64.conf

Herve,

Any chance your patches are available in a tree somewhere? Maybe in a branch?
Maybe on github? ;-)

I would like to give them a try (build and boot).

Best regards,
Trevor

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

Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Hi Khem,

I believe it would be more appropriate to have it "system-wide", because at 
some point it should not be something the apps need to worry about.
Plus, it's really a SoC thing, some armv8 SoCs do implement those options, some 
don't (when I say "option" there, I mean it's a HW block that may or may not be 
implemented in the SoC, it's not just a compilation switch that would work for 
all revisions of armv8).
So I believe those HW options should indeed be defined in arch-armv8.inc, and 
each soc-specific file should select the options that are possible for it.
For instance, cortex-a53 has "by definition" the crc HW included, but the 
crypto HW block may or may not be implemented. For Raspberrypi3, BCM2837 does 
not have it. Most other Cortex-A53 I know of have it, though.
Therefore, the definition of the "crypto" variant for cortexa53-32, in addition 
with the sf/hf variants for aarch32.
For aarch64, the floating point abi is hf, so that's less variants, but I 
should also add cortexa53crypto-64, to be exhaustive... It's not going to be 
useful for RPI3, but it might be for all future 
armv8/cortex-a53/cortex-a57/cortex-a72/cortex-a73 based SoCs that will have to 
be supported in the future.
So we could add it all now, or we could add it in the future as needs emerge.

Herve

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: lundi 21 novembre 2016 17:35
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and 
add raspberrypi3-64.conf

On Sun, Nov 20, 2016 at 9:21 PM, Herve Jourdain <herve.jourd...@neuf.fr> wrote:
> Hi Khem,
>
> For cortexa53 in aarch32, the problem is to figure out if we want to cover 
> all cases or not.
> Raspberrypi3 is one case of CortexA53 that has crc support, but no crypto 
> support. So I could define a cortexa53-32 as being just that.
> But then, there are other CortexA53-based SoCs that do have the crypto 
> extension, and I thought that, since I was going to modify it, I'd rather 
> cover all possible cases/options...
>
> The one thing that could be scrapped is the hf option, if we decide that all 
> cortexa53 aarch32 will be hf only.
> Then that would avoid the hf duplication of the aarch32 tunes, leaving only 2 
> tunes for cortexa53 aarch32 + 1 tune for cortexa53 aarch64.
>
> Please advise what you would prefer me to do.

is there an advantage of having crc and crypto as systemwide tune options or is 
it more beneficial to apply them surgically to needed apps via MACHINE_FEATURES
>
> Herve
>
> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: dimanche 20 novembre 2016 20:30
> To: Herve Jourdain <herve.jourd...@neuf.fr>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify 
> raspberrypi3.conf and add raspberrypi3-64.conf
>
> Herve,
>
> There is no need to create so many variants for a53 32 bit mode. We can keep 
> using whatever we have its only 64bit that needs to be added as a new machine.
>
> On Sun, Nov 20, 2016 at 4:06 AM, Herve Jourdain <herve.jourd...@neuf.fr> 
> wrote:
>> Hi Khem,
>>
>> FYI, I am sending a slightly modified version (cortexa53hf-32 instead 
>> of
>> cortexa53-32 for raspberrypi3.conf).
>> They still depend on modifications in oe-core (heavier this time than 
>> before), also posted to the list.
>>
>> Herve
>>
>> -Original Message-
>> From: Khem Raj [mailto:raj.k...@gmail.com]
>> Sent: samedi 19 novembre 2016 19:19
>> To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
>> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify 
>> raspberrypi3.conf and add raspberrypi3-64.conf
>>
>> Nevermind, I managed to apply it, there are some CR changes I guess 
>> which was freaking git
>>
>> On 11/19/16 5:03 AM, Herve Jourdain wrote:
>>> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
>>> ---
>>>  conf/machine/raspberrypi3-64.conf | 19 +++
>>>  conf/machine/raspberrypi3.conf|  8 ++--
>>>  2 files changed, 25 insertions(+), 2 deletions(-)  create mode
>>> 100644 conf/machine/raspberrypi3-64.conf
>>>
>>> diff --git a/conf/machine/raspberrypi3-64.conf
>>> b/conf/machine/raspberrypi3-64.conf
>>> new file mode 100644
>>> index 000..a5ceddb
>>> --- /dev/null
>>> +++ b/conf/machine/raspberrypi3-64.conf
>>> @@ -0,0 +1,19 @@
>>> +#@TYPE: Machine
>>> +#@NAME: RaspberryPi 3 Development Board
>>> +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 
>>>

Re: [yocto] [raspberrypi] raspi3 vs raspi2

[Herve Jourdain]

Hi Trevor,

I've never tried with 4.8, but I sent patches to the list that add 64 bits 
support for 4.7.10 - and this one, I tested and it is working.
It's probably possible to port 64 bits to 4.4 as well, but I'm not sure if it's 
worth the effort.
I have 4.7 covered, there is some "built-in" level of support in 4.8 (but I 
don't know what's working or not there), and I'll sure work it for 4.9 soon.

Herve

-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: mardi 22 novembre 2016 06:39
To: Khem Raj <raj.k...@gmail.com>
Cc: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [raspberrypi] raspi3 vs raspi2

On Mon 2016-11-21 @ 04:09:50 PM, Khem Raj wrote:
> 4.4 does not support 64-bit pi3, do you set the PREFERRED_VERSION in 
> local conf metadata ?

Yes, my conf/local.conf contains:

PREFERRED_VERSION_linux-raspberrypi = "4.8%"

If you clone git://github.com/raspberrypi/linux.git and checkout the 4.8.y 
branch, you'll see that there's no commit
ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7 anywhere in that branch. In fact there 
is no such commit anywhere in that repository:

$ git branch --contains ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7
error: no such commit ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7

> 
> On 11/21/16 3:07 PM, Trevor Woerner wrote:
> > On Sun 2016-11-20 @ 11:28:48 AM, Khem Raj wrote:
> >> I gave a whirl at building and looking closely at them. As it seems 
> >> the OE core patch is not needed since for armv8 we want to keep it 
> >> like x86 ( common ) I have therefore made changes to your patches 
> >> and staged them here.
> >>
> >> https://github.com/kraj/meta-raspberrypi/commits/kraj/master
> >>
> >> Which should work without any change in OE-Core, secondly I have 
> >> further divided them and also fixed 4.8 to compile arm64.
> > 
> > I tried giving this a whirl.
> > 
> > Maybe the order of my layers in bblayers isn't correct, but by 
> > default my build uses 4.4% instead of 4.8%.
> > 
> > conf/machine/raspberrypi3-64.conf includes:
> > ...
> > include conf/machine/include/rpi-base.inc
> > ...
> > PREFERRED_VERSION_linux-raspberrypi ?= "4.8.%"
> > 
> > conf/machine/include/rpi-base.inc contains:
> > ...
> > include conf/machine/include/rpi-default-versions.inc
> > ...
> > 
> > conf/machine/include/rpi-default-versions.inc contains:
> > ...
> > PREFERRED_VERSION_linux-raspberrypi ?= "4.4.%"
> > 
> > In any case when I try building with 4.4 I get:
> > 
> > ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 
> > do_kernel_configme: No default configuration for raspberrypi3-64 / 
> > bcmrpi3_defconfig available.
> > ERROR: linux-raspberrypi-1_4.4.28+gitAUTOINC+5afda48c34-r0 
> > do_kernel_configme: Function failed: do_kernel_configme (log file is 
> > located at 
> > /z/layerindex-master/raspi3-64/tmp-glibc/work/raspberrypi3_64-oe-lin
> > ux/linux-raspberrypi/1_4.4.28+gitAUTOINC+5afda48c34-r0/temp/log.do_k
> > ernel_configme.15498)
> > 
> > When I switch to 4.8 explicitly in my conf/local.conf I get:
> > 
> > ERROR: linux-raspberrypi-1_4.8.8+gitAUTOINC+ea6eeaff07-r0 do_fetch: 
> > Fetcher failure: Unable to find revision 
> > ea6eeaff07c4881e6287fe3e7ea58fc30e5569d7 in branch rpi-4.8.y even from 
> > upstream
> > ERROR: linux-raspberrypi-1_4.8.8+gitAUTOINC+ea6eeaff07-r0 do_fetch: 
> > Fetcher failure for URL: 
> > 'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y'. 
> > Unable to fetch URL from any source.
> > 
> > My build configuration is:
> > Build Configuration:
> > BB_VERSION= "1.32.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING   = "opensuse-42.1"
> > TARGET_SYS= "aarch64-oe-linux"
> > MACHINE   = "raspberrypi3-64"
> > DISTRO= "nodistro"
> > DISTRO_VERSION= "nodistro.0"
> > TUNE_FEATURES = "aarch64"
> > TARGET_FPU= ""
> > meta-raspberrypi__kraj = 
> > "kraj/master:4735e7cde210b2b0b855bca1eb90ef4adca8019b"
> > meta  = "master:a675b2c89e477af088faee9b3be96eae19a85f0b"
> > meta-oe   
> > meta-gnome= "master:7f8915a6ecdd5c4b03c7e5b5f1fa903f89c2d560"
> > 
> 


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

Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Hi Khem,

For cortexa53 in aarch32, the problem is to figure out if we want to cover all 
cases or not.
Raspberrypi3 is one case of CortexA53 that has crc support, but no crypto 
support. So I could define a cortexa53-32 as being just that.
But then, there are other CortexA53-based SoCs that do have the crypto 
extension, and I thought that, since I was going to modify it, I'd rather cover 
all possible cases/options...

The one thing that could be scrapped is the hf option, if we decide that all 
cortexa53 aarch32 will be hf only.
Then that would avoid the hf duplication of the aarch32 tunes, leaving only 2 
tunes for cortexa53 aarch32 + 1 tune for cortexa53 aarch64.

Please advise what you would prefer me to do.

Herve

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: dimanche 20 novembre 2016 20:30
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and 
add raspberrypi3-64.conf

Herve,

There is no need to create so many variants for a53 32 bit mode. We can keep 
using whatever we have its only 64bit that needs to be added as a new machine.

On Sun, Nov 20, 2016 at 4:06 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote:
> Hi Khem,
>
> FYI, I am sending a slightly modified version (cortexa53hf-32 instead 
> of
> cortexa53-32 for raspberrypi3.conf).
> They still depend on modifications in oe-core (heavier this time than 
> before), also posted to the list.
>
> Herve
>
> -Original Message-
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: samedi 19 novembre 2016 19:19
> To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify 
> raspberrypi3.conf and add raspberrypi3-64.conf
>
> Nevermind, I managed to apply it, there are some CR changes I guess 
> which was freaking git
>
> On 11/19/16 5:03 AM, Herve Jourdain wrote:
>> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
>> ---
>>  conf/machine/raspberrypi3-64.conf | 19 +++
>>  conf/machine/raspberrypi3.conf|  8 ++--
>>  2 files changed, 25 insertions(+), 2 deletions(-)  create mode 
>> 100644 conf/machine/raspberrypi3-64.conf
>>
>> diff --git a/conf/machine/raspberrypi3-64.conf
>> b/conf/machine/raspberrypi3-64.conf
>> new file mode 100644
>> index 000..a5ceddb
>> --- /dev/null
>> +++ b/conf/machine/raspberrypi3-64.conf
>> @@ -0,0 +1,19 @@
>> +#@TYPE: Machine
>> +#@NAME: RaspberryPi 3 Development Board
>> +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 
>> +bits mode
>> +
>> +DEFAULTTUNE ?= "cortexa53-64"
>> +
>> +MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
>> +
>> +MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>> +
>> +PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
>> +
>> +require conf/machine/include/tune-cortexa53.inc
>> +include conf/machine/include/rpi-base.inc
>> +
>> +SERIAL_CONSOLE = "115200 ttyS0"
>> +VC4_CMA_SIZE ?= "cma-256"
>> +
>> +UBOOT_MACHINE = "rpi_3_config"
>> diff --git a/conf/machine/raspberrypi3.conf 
>> b/conf/machine/raspberrypi3.conf index 9820209..f142323 100644
>> --- a/conf/machine/raspberrypi3.conf
>> +++ b/conf/machine/raspberrypi3.conf
>> @@ -2,12 +2,16 @@
>>  #@NAME: RaspberryPi 3 Development Board
>>  #@DESCRIPTION: Machine configuration for the RaspberryPi 3
>>
>> -MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
>> +DEFAULTTUNE ?= "cortexa53-32"
>> +
>> +MACHINEOVERRIDES = "raspberrypi2:raspberrypi:${MACHINE}"
>>
>>  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>>
>> -include conf/machine/raspberrypi2.conf
>> +require conf/machine/include/tune-cortexa53.inc
>> +include conf/machine/include/rpi-base.inc
>>
>>  SERIAL_CONSOLE = "115200 ttyS0"
>>  VC4_CMA_SIZE ?= "cma-256"
>>
>> +UBOOT_MACHINE = "rpi_3_config"
>>
>
>

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

Re: [yocto] [meta-raspberrypi][PATCH 2/2] Support for 64bits target on raspberrypi3 (patches for supporting 64bits on linux 4.7)

[Herve Jourdain]

Hi Khem,

OK, I'll submit a v2 soon.

Herve

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: dimanche 20 novembre 2016 20:42
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 2/2] Support for 64bits target on 
raspberrypi3 (patches for supporting 64bits on linux 4.7)

this patch needs some rework. user __PRIx64__ whereveer llx and lld
are used you dont need ifdefs
secondly all the backports should be a separate patch. All local
changes should be logically seprated individual patches.

On Sun, Nov 20, 2016 at 4:46 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  .../0001-fix-dtbo-rules.patch  |   19 +-
>  .../0002-support-64bits.patch  | 2080 
> 
>  recipes-kernel/linux/linux-raspberrypi_4.7.bb  |2 +
>  3 files changed, 2098 insertions(+), 3 deletions(-)
>  create mode 100644 
> recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch
>
> diff --git 
> a/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch 
> b/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
> index 5113e23..96f3c32 100644
> --- a/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
> +++ b/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
> @@ -1,7 +1,7 @@
> -From 13c8784da3dbd977f64cec740eba775b6fab11c2 Mon Sep 17 00:00:00 2001
> +From 13c8784da3dbd977f64cec740eba775b6fab11c2 Sat Nov 19 00:00:00 2001
>  From: Herve Jourdain <herve.jourd...@neuf.fr>
> -Date: Fri, 20 May 2016 16:02:23 +0800
> -Subject: [yocto][meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc:
> +Date: Sat, 19 Nov 2016 16:02:23 +0800
> +Subject: [yocto][meta-raspberrypi][PATCH] linux-raspberrypi_4.7.inc:
>   support for .dtbo files for dtb overlays
>
>  Upstream-Status: Pending
> @@ -28,6 +28,19 @@ index a2e7cf7..673c1cb 100644
>
>   PHONY += dtbs dtbs_install
>
> +diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> +index 648a32c..68b8147 100644
> +--- a/arch/arm64/Makefile
>  b/arch/arm64/Makefile
> +@@ -103,6 +103,8 @@ zinstall install:
> +
> + %.dtb: scripts
> +   $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
> ++%.dtbo: scripts
> ++  $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
> +
> + PHONY += dtbs dtbs_install
> +
>  diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
>  index 3079c4f..6cc3766 100644
>  --- a/scripts/Makefile.lib
> diff --git 
> a/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch 
> b/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch
> new file mode 100644
> index 000..681e05a
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch
> @@ -0,0 +1,2080 @@
> +From dbf41aef92421f5601e2122cbee921561a56ad4b Mon Sep 17 00:00:00 2001
> +From: Herve Jourdain <herve.jourd...@neuf.fr>
> +Date: Wed, 31 Aug 2016 19:30:33 +0800
> +Subject: [PATCH] Support for 64bits (aarch64) v4.7 kernel on RaspberryPi3
> +
> +---
> + arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi  |   19 +
> + arch/arm/boot/dts/bcm283x.dtsi   |2 +
> + arch/arm64/Kconfig.platforms |   13 +
> + arch/arm64/boot/dts/broadcom/Makefile|5 +
> + arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts |   47 +
> + arch/arm64/boot/dts/broadcom/bcm2837.dtsi|   76 ++
> + arch/arm64/boot/dts/broadcom/overlays|1 +
> + arch/arm64/configs/bcm2837_defconfig | 1273 
> ++
> + arch/arm64/include/asm/dma-mapping.h |   15 +-
> + drivers/irqchip/irq-bcm2835.c|   22 +
> + drivers/irqchip/irq-bcm2836.c|8 +-
> + drivers/mmc/host/bcm2835-sdhost.c|  104 ++
> + drivers/spi/spi-bcm2835.c|4 +
> + drivers/tty/serial/amba-pl011.c  |2 +
> + drivers/video/fbdev/bcm2708_fb.c |4 +
> + 15 files changed, 1592 insertions(+), 3 deletions(-)
> + create mode 100644 arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi
> + create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts
> + create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837.dtsi
> + create mode 12 arch/arm64/boot/dts/broadcom/overlays
> + create mode 100644 arch/arm64/configs/bcm2837_defconfig
> +
> +diff --git a/arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi 
> b/arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi
> +new file mode 100644
> +index 000..3f0a56e
> +--- /dev/null
>  b/arch/arm/boot/dts/bcm2

Re: [yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi_4.7.bb: upgrade to latest good version

[Herve Jourdain]

Hi Khem,

If I may, I have an interest in keeping 4.7 for a few more months (2 or 3 I
guess).
I'm using it for a few things, and I don't currently plan to switch to 4.8,
but rather to 4.9 when it's more stable (hence the 2 or 3 additional
months).
As you already know, 4.9 is supposed to be the next LTS (if Greg
Kroah-Hartman doesn't change his mind), and I'd like to wait for it while
keep using the version I already use.

This said, given the recent rebasing on the raspberrypi github, at least for
version 4.7, it definitely is a maintenance burden.
If that can help, I'm volunteering to maintain the revision for the 4.7
raspberrypi linux kernel, for the next 2 to 3 months.

After that, the question that will remain is what revisions do we keep: we
currently have 4.1, 4.4, 4.7 and 4.8.
We will soon have 4.9.
4.1 and 4.4 are LTS (EOL = 09/2017 & 02/2018), neither 4.7 nor 4.8 will be,
and 4.9 is supposed to be.
What do you think we should do, scrap 4.1 and 4.7, leaving 4.4, 4.8 and 4.9?
Or keep only the LTS ones?

Herve

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: jeudi 17 novembre 2016 18:17
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi_4.7.bb:
upgrade to latest good version



On 11/17/16 5:13 AM, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.7.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.7.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> index 0315f8f..4a8fe36 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>  
> -LINUX_VERSION ?= "4.7.7"
> +LINUX_VERSION ?= "4.7.10"

I think, we should abandon all non-lts recipes except one which will be
latest release ( 4.8 ) as of today.

>  
> -SRCREV = "a45a35c08598b23f9fd82e49c83b46c7d536244f"
> +SRCREV = "e7fa325a40f260ed9fb86391a0b65150eba8c112"
>  SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.7.y \
> file://0001-fix-dtbo-rules.patch \  "
> 


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

[yocto] [meta-raspberrypi][PATCH 2/2] Support for 64bits target on raspberrypi3 (patches for supporting 64bits on linux 4.7)

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0001-fix-dtbo-rules.patch  |   19 +-
 .../0002-support-64bits.patch  | 2080 
 recipes-kernel/linux/linux-raspberrypi_4.7.bb  |2 +
 3 files changed, 2098 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
index 5113e23..96f3c32 100644
--- a/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
+++ b/recipes-kernel/linux/linux-raspberrypi-4.7/0001-fix-dtbo-rules.patch
@@ -1,7 +1,7 @@
-From 13c8784da3dbd977f64cec740eba775b6fab11c2 Mon Sep 17 00:00:00 2001
+From 13c8784da3dbd977f64cec740eba775b6fab11c2 Sat Nov 19 00:00:00 2001
 From: Herve Jourdain <herve.jourd...@neuf.fr>
-Date: Fri, 20 May 2016 16:02:23 +0800
-Subject: [yocto][meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc:
+Date: Sat, 19 Nov 2016 16:02:23 +0800
+Subject: [yocto][meta-raspberrypi][PATCH] linux-raspberrypi_4.7.inc:
  support for .dtbo files for dtb overlays
 
 Upstream-Status: Pending
@@ -28,6 +28,19 @@ index a2e7cf7..673c1cb 100644
  
  PHONY += dtbs dtbs_install
  
+diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
+index 648a32c..68b8147 100644
+--- a/arch/arm64/Makefile
 b/arch/arm64/Makefile
+@@ -103,6 +103,8 @@ zinstall install:
+ 
+ %.dtb: scripts
+   $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
++%.dtbo: scripts
++  $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
+ 
+ PHONY += dtbs dtbs_install
+ 
 diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
 index 3079c4f..6cc3766 100644
 --- a/scripts/Makefile.lib
diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch
new file mode 100644
index 000..681e05a
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch
@@ -0,0 +1,2080 @@
+From dbf41aef92421f5601e2122cbee921561a56ad4b Mon Sep 17 00:00:00 2001
+From: Herve Jourdain <herve.jourd...@neuf.fr>
+Date: Wed, 31 Aug 2016 19:30:33 +0800
+Subject: [PATCH] Support for 64bits (aarch64) v4.7 kernel on RaspberryPi3
+
+---
+ arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi  |   19 +
+ arch/arm/boot/dts/bcm283x.dtsi   |2 +
+ arch/arm64/Kconfig.platforms |   13 +
+ arch/arm64/boot/dts/broadcom/Makefile|5 +
+ arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts |   47 +
+ arch/arm64/boot/dts/broadcom/bcm2837.dtsi|   76 ++
+ arch/arm64/boot/dts/broadcom/overlays|1 +
+ arch/arm64/configs/bcm2837_defconfig | 1273 ++
+ arch/arm64/include/asm/dma-mapping.h |   15 +-
+ drivers/irqchip/irq-bcm2835.c|   22 +
+ drivers/irqchip/irq-bcm2836.c|8 +-
+ drivers/mmc/host/bcm2835-sdhost.c|  104 ++
+ drivers/spi/spi-bcm2835.c|4 +
+ drivers/tty/serial/amba-pl011.c  |2 +
+ drivers/video/fbdev/bcm2708_fb.c |4 +
+ 15 files changed, 1592 insertions(+), 3 deletions(-)
+ create mode 100644 arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi
+ create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts
+ create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837.dtsi
+ create mode 12 arch/arm64/boot/dts/broadcom/overlays
+ create mode 100644 arch/arm64/configs/bcm2837_defconfig
+
+diff --git a/arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi 
b/arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi
+new file mode 100644
+index 000..3f0a56e
+--- /dev/null
 b/arch/arm/boot/dts/bcm283x-rpi-smsc9514.dtsi
+@@ -0,0 +1,19 @@
++/ {
++  aliases {
++  ethernet = 
++  };
++};
++
++ {
++  usb1@1 {
++  compatible = "usb424,9514";
++  reg = <1>;
++  #address-cells = <1>;
++  #size-cells = <0>;
++
++  ethernet: usbether@1 {
++  compatible = "usb424,ec00";
++  reg = <1>;
++  };
++  };
++};
+diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
+index 10b27b9..b982522 100644
+--- a/arch/arm/boot/dts/bcm283x.dtsi
 b/arch/arm/boot/dts/bcm283x.dtsi
+@@ -287,6 +287,8 @@
+   compatible = "brcm,bcm2835-usb";
+   reg = <0x7e98 0x1>;
+   interrupts = <1 9>;
++  #address-cells = <1>;
++  #size-cells = <0>;
+   };
+ 
+   v3d: v3d@7ec0 {
+diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
+index 7ef1d05..ea88402

[yocto] [meta-raspberrypi][PATCH 0/2] Support for 64bits target on raspberrypi3

[Herve Jourdain]

This adds the support of 64bits, for raspberrypi3 only (because based on 
cortexa53).
It's composed of a "generic" part, which should apply to all 64bits ports on 
future kernels,
and of a port to Linux kernel 4.7.
The port to Linux kernel 4.7 was finished early August, initially on 4.7.0, 
then was moved to 4.7.2.
Since the revisions I used then seem to have vanished from the raspberrypi 
tree, it was ported
to the latest 4.7 "good version" (4.7.10).
There are a few things to know about the 64bits ports on raspberrypi:
* userland doesn't work. It's mostly because the binary blob in the GPU 
communicates with the CPU using 32bits pointers... And since 64bits is not 
officially supported by raspberrypi foundation, they will not modify the binary 
blob (until they decide it's officially supported)
* VC4 should work (but I didn't test it). Boot messages seem to show it 
initialized correctly.
* Some drivers selected are different than the stock 32bits drivers, which can 
lead to some different log messages.

It's been tested with ethernet, sdcards support, USB support, and a few others, 
and seemed to work fine with those.
It's not been tested with HATs.

This is mostly for people who have an interest in 64bits, and can bear the 
limitations.

Herve Jourdain (2):
  Support for 64bits target on raspberrypi3 (generic part)
  Support for 64bits target on raspberrypi3 (patches for supporting
64bits on linux 4.7)

 classes/sdcard_image-rpi.bbclass   |2 +
 conf/machine/include/rpi-base.inc  |   21 +
 recipes-bsp/bootfiles/rpi-config_git.bb|6 +
 .../0001-fix-dtbo-rules.patch  |   19 +-
 .../0002-support-64bits.patch  | 2080 
 recipes-kernel/linux/linux-raspberrypi.inc |2 +
 recipes-kernel/linux/linux-raspberrypi_4.7.bb  |2 +
 recipes-kernel/linux/linux-rpi.inc |   38 +-
 8 files changed, 2157 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.7/0002-support-64bits.patch

-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi3-64.conf | 19 +++
 conf/machine/raspberrypi3.conf|  8 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)
 create mode 100644 conf/machine/raspberrypi3-64.conf

diff --git a/conf/machine/raspberrypi3-64.conf 
b/conf/machine/raspberrypi3-64.conf
new file mode 100644
index 000..a5ceddb
--- /dev/null
+++ b/conf/machine/raspberrypi3-64.conf
@@ -0,0 +1,19 @@
+#@TYPE: Machine
+#@NAME: RaspberryPi 3 Development Board
+#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 bits mode
+
+DEFAULTTUNE ?= "cortexa53-64"
+
+MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
+
+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
+
+PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
+
+require conf/machine/include/tune-cortexa53.inc
+include conf/machine/include/rpi-base.inc
+
+SERIAL_CONSOLE = "115200 ttyS0"
+VC4_CMA_SIZE ?= "cma-256"
+
+UBOOT_MACHINE = "rpi_3_config"
diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 9820209..ab6a481 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -2,12 +2,16 @@
 #@NAME: RaspberryPi 3 Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi 3
 
-MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
+DEFAULTTUNE ?= "cortexa53hf-32"
+
+MACHINEOVERRIDES = "raspberrypi2:raspberrypi:${MACHINE}"
 
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
 
-include conf/machine/raspberrypi2.conf
+require conf/machine/include/tune-cortexa53.inc
+include conf/machine/include/rpi-base.inc
 
 SERIAL_CONSOLE = "115200 ttyS0"
 VC4_CMA_SIZE ?= "cma-256"
 
+UBOOT_MACHINE = "rpi_3_config"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 0/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Modify raspberrypi3.conf to use cortexa53 instead of being treated like a 
raspberrypi2
Add raspberrypi3-64.conf, to support armv8 / 64 bits on raspberrypi3

Herve Jourdain (1):
  Modify raspberrypi3.conf to use cortexa53 instead of being treated
like a raspberrypi2 Add raspberrypi3-64.conf, to support armv8 /
64 bits on raspberrypi3

 conf/machine/raspberrypi3-64.conf | 19 +++
 conf/machine/raspberrypi3.conf|  8 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)
 create mode 100644 conf/machine/raspberrypi3-64.conf

-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Hi Khem,

FYI, I am sending a slightly modified version (cortexa53hf-32 instead of
cortexa53-32 for raspberrypi3.conf).
They still depend on modifications in oe-core (heavier this time than
before), also posted to the list.

Herve

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: samedi 19 novembre 2016 19:19
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf
and add raspberrypi3-64.conf

Nevermind, I managed to apply it, there are some CR changes I guess which
was freaking git

On 11/19/16 5:03 AM, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  conf/machine/raspberrypi3-64.conf | 19 +++
>  conf/machine/raspberrypi3.conf|  8 ++--
>  2 files changed, 25 insertions(+), 2 deletions(-)  create mode 100644 
> conf/machine/raspberrypi3-64.conf
> 
> diff --git a/conf/machine/raspberrypi3-64.conf 
> b/conf/machine/raspberrypi3-64.conf
> new file mode 100644
> index 000..a5ceddb
> --- /dev/null
> +++ b/conf/machine/raspberrypi3-64.conf
> @@ -0,0 +1,19 @@
> +#@TYPE: Machine
> +#@NAME: RaspberryPi 3 Development Board
> +#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 bits 
> +mode
> +
> +DEFAULTTUNE ?= "cortexa53-64"
> +
> +MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
> +
> +MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
> +
> +PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
> +
> +require conf/machine/include/tune-cortexa53.inc
> +include conf/machine/include/rpi-base.inc
> +
> +SERIAL_CONSOLE = "115200 ttyS0"
> +VC4_CMA_SIZE ?= "cma-256"
> +
> +UBOOT_MACHINE = "rpi_3_config"
> diff --git a/conf/machine/raspberrypi3.conf 
> b/conf/machine/raspberrypi3.conf index 9820209..f142323 100644
> --- a/conf/machine/raspberrypi3.conf
> +++ b/conf/machine/raspberrypi3.conf
> @@ -2,12 +2,16 @@
>  #@NAME: RaspberryPi 3 Development Board
>  #@DESCRIPTION: Machine configuration for the RaspberryPi 3
>  
> -MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> +DEFAULTTUNE ?= "cortexa53-32"
> +
> +MACHINEOVERRIDES = "raspberrypi2:raspberrypi:${MACHINE}"
>  
>  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
>  
> -include conf/machine/raspberrypi2.conf
> +require conf/machine/include/tune-cortexa53.inc
> +include conf/machine/include/rpi-base.inc
>  
>  SERIAL_CONSOLE = "115200 ttyS0"
>  VC4_CMA_SIZE ?= "cma-256"
>  
> +UBOOT_MACHINE = "rpi_3_config"
> 


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

Re: [yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Please disregard this patch, I will send a - slightly - modified version
(cortexa53hf-32 instead of cortexa53-32)

Herve

-Original Message-
From: Herve Jourdain [mailto:herve.jourd...@neuf.fr] 
Sent: samedi 19 novembre 2016 14:04
To: yocto@yoctoproject.org
Cc: Herve Jourdain <herve.jourd...@neuf.fr>
Subject: [yocto][meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and
add raspberrypi3-64.conf

Modify raspberrypi3.conf to use cortexa53 instead of being treated like a
raspberrypi2 Add raspberrypi3-64.conf, to support armv8 / 64 bits on
raspberrypi3

Herve Jourdain (2):
  Modify raspberrypi3.conf to use cortexa53 instead of being treated
like a raspberrypi2 Add raspberrypi3-64.conf, to support armv8 /
64 bits on raspberrypi3

 conf/machine/raspberrypi3-64.conf | 19 +++
 conf/machine/raspberrypi3.conf|  8 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)  create mode 100644
conf/machine/raspberrypi3-64.conf

--
2.7.4

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

Re: [yocto] [raspberrypi] raspi3 vs raspi2

[Herve Jourdain]

Hi Khem, Trevor,

I've submitted part of it yesterday, the rest should come out today
hopefully.
The 2 machine types - raspberrypi3 and raspberrypi3-64 - have been submitted
to yocto/meta-raspberrypi.
They will need tune-cortexa53.inc - I've sent a version to oe-core, but I
got it wrong again, so I will resend it hopefully again, along with a
modified version of arch-armv8.inc.

I have some patches to support 64bits on Raspberrypi3 that should be pushed
-hopefully - today. They're on 4.7.10, though.

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Khem Raj
Sent: samedi 19 novembre 2016 18:30
To: Trevor Woerner 
Cc: yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] [raspberrypi] raspi3 vs raspi2

On Fri, Nov 18, 2016 at 1:20 PM, Trevor Woerner  wrote:
> Hi,
>
> I was wondering if there were any plans to create a 
> MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it 
> is instead of generating images that are backwards compatible with the
CortexA7 that is the raspi2?

Thats a good question. I know few folks who have done 64bit port of OE on
rpi3 so I would be interested in such patches where we add rpi3-64 machine
type.
do you have patches to submit ? Please do

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

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

[yocto] [meta-raspberrypi][PATCH 1/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi3-64.conf | 19 +++
 conf/machine/raspberrypi3.conf|  8 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)
 create mode 100644 conf/machine/raspberrypi3-64.conf

diff --git a/conf/machine/raspberrypi3-64.conf 
b/conf/machine/raspberrypi3-64.conf
new file mode 100644
index 000..a5ceddb
--- /dev/null
+++ b/conf/machine/raspberrypi3-64.conf
@@ -0,0 +1,19 @@
+#@TYPE: Machine
+#@NAME: RaspberryPi 3 Development Board
+#@DESCRIPTION: Machine configuration for the RaspberryPi 3 in 64 bits mode
+
+DEFAULTTUNE ?= "cortexa53-64"
+
+MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
+
+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
+
+PREFERRED_VERSION_linux-raspberrypi_raspberrypi3-64 ?= "4.7.%"
+
+require conf/machine/include/tune-cortexa53.inc
+include conf/machine/include/rpi-base.inc
+
+SERIAL_CONSOLE = "115200 ttyS0"
+VC4_CMA_SIZE ?= "cma-256"
+
+UBOOT_MACHINE = "rpi_3_config"
diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 9820209..f142323 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -2,12 +2,16 @@
 #@NAME: RaspberryPi 3 Development Board
 #@DESCRIPTION: Machine configuration for the RaspberryPi 3
 
-MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
+DEFAULTTUNE ?= "cortexa53-32"
+
+MACHINEOVERRIDES = "raspberrypi2:raspberrypi:${MACHINE}"
 
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
 
-include conf/machine/raspberrypi2.conf
+require conf/machine/include/tune-cortexa53.inc
+include conf/machine/include/rpi-base.inc
 
 SERIAL_CONSOLE = "115200 ttyS0"
 VC4_CMA_SIZE ?= "cma-256"
 
+UBOOT_MACHINE = "rpi_3_config"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH 0/1] Modify raspberrypi3.conf and add raspberrypi3-64.conf

[Herve Jourdain]

Modify raspberrypi3.conf to use cortexa53 instead of being treated like a 
raspberrypi2
Add raspberrypi3-64.conf, to support armv8 / 64 bits on raspberrypi3

Herve Jourdain (2):
  Modify raspberrypi3.conf to use cortexa53 instead of being treated
like a raspberrypi2 Add raspberrypi3-64.conf, to support armv8 /
64 bits on raspberrypi3

 conf/machine/raspberrypi3-64.conf | 19 +++
 conf/machine/raspberrypi3.conf|  8 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)
 create mode 100644 conf/machine/raspberrypi3-64.conf

-- 
2.7.4

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

Re: [yocto] ***SPAM*** [raspberrypi] raspi3 vs raspi2

[Herve Jourdain]

Hi,

I'm in the process of pushing something that should hopefully do that - and 
more.
I hope I can finish pushing it in the next few days.

Cheers,

Herve

> On 19 nov. 2016, at 05:20, Trevor Woerner  wrote:
> 
> Hi,
> 
> I was wondering if there were any plans to create a MACHINE=raspberrypi3 that
> treats the raspi3 like the CortexA53 that it is instead of generating images
> that are backwards compatible with the CortexA7 that is the raspi2?
> 
> Best regards,
>Trevor
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi_4.7.bb: upgrade to latest good version

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-raspberrypi_4.7.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.7.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
index 0315f8f..4a8fe36 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.7.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.7.7"
+LINUX_VERSION ?= "4.7.10"
 
-SRCREV = "a45a35c08598b23f9fd82e49c83b46c7d536244f"
+SRCREV = "e7fa325a40f260ed9fb86391a0b65150eba8c112"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.7.y \
file://0001-fix-dtbo-rules.patch \
 "
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH 0/1] linux-raspberrypi_4.7.bb: upgrade to latest good version

[Herve Jourdain]

There seems to be a lot of rebasing these days on the raspberrypi linux 
repository for 4.7, with previously well-known revisions not existing anymore 
in the tree.
Also, some files have mysteriously disappeared from the tree when they were 
available 2 months ago, and just re-appeared 3 weeks ago...
This attempts to upgrade to the latest "good" version for 4.7, with all the 
files that should be there being present.
It does compile, as of today - until when depends highly on what's going on in 
the raspberrypi tree.

Herve Jourdain (1):
  linux-raspberrypi_4.7.bb: upgrade to latest good version

 recipes-kernel/linux/linux-raspberrypi_4.7.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH v6 3/4] linux-raspberrypi-base.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Hi François,

Actually, I tried to use a -overlay.dtb as a device tree overlay with the 
4.4.9, and it didn't load it...
If you don't use the tools dedicated to debug device trees (like vcdbg), there 
is no error message nor complaint, but the device tree is not loaded. Only when 
I used vcdbg did I see it complained that it could not find the .dtbo file.
I'm not sure if the loader has changed since then, but if it has not then you 
probably need to impose .dtbo for kernels > 4.4.6. Or issue an error if the 
KERNEL_DEVICETREE variable is not consistent with the kernel version...

The current behaviour is following some remark/proposal from Andrei - the very 
first proposal had different versions of KERNEL_DEVICETREE, depending on the 
kernel version actually.
But I agree with Andrei that it would be easier to just maintain one set of 
default values for the KERNEL_DEVICETREE.
One thing I didn't consider is the override of that variable, maybe a warning 
message could be added if we have to change the -overlay.dtb into .dtbo.
But we should probably do the change to 'dtbo regardless, because it's very 
likely it would not load properly later, with no message except with vcdbg...

Would that solution be OK with you?

Andrei, do you have any comment on this?

Herve

> Le 25 juil. 2016 à 10:45, Francois Muller <forlor...@gmail.com> a écrit :
> 
> Hi Hervé,
> 
> Thank you for giving us up and running .dtbo overlays functionality through 
> this patch, it is running fine for me.
> 
> Nevertheless, I have a concern about the processing applied to overlay 
> filenames.
> 
> According to this post 
> https://www.raspberrypi.org/forums/viewtopic.php?f=107=139732, 
> '-overlay.dtb' suffixes have been superseded by '.dtbo' suffix to reflect an 
> improvement in overlay functionalities and thus overlay binary format (or 
> simply content, I don't know).
> Moreover, changing the suffix gives a chance for older and newer overlay 
> formats to coexist in a boot folder.
> 
> So, I'm not very fond of a build system changing the inputs I give to it 
> (i.e. KERNEL_DEVICETREE) depending on another input from my side (kernel 
> version) without at least notifying me the change occurred.
> I would highly prefer a bbwarn (or should it even fail?) if the requested 
> overlay filenames don't suit the kernel version being chosen (btw device 
> trees are theoretically aimed to be kernel version and even OS independent as 
> it should only contain pure hardware platform description).
> I understand and appreciate the intention of offering a kind of compatibility 
> for kernels prior to 4.4.6 but I don't think it's needed here. 
> 
> If KERNEL_DEVICETREE isn't empty for kernels prior to 3.18 => let's disable 
> device trees (or simply remove this test, this layer doesn't provide any)
> If KERNEL_DEVICETREE asks for -overlay.dtb and kernel >= 3.18 => let's 
> compile it, it has been requested
> If KERNEL_DEVICETREE asks for .dtbo and kernel < 4.4.6 => let's fail with a 
> comprehensive message (these kernels even don't know what a .dtbo file is!)
> If KERNEL_DEVICETREE asks for -overlay.dtb and/or .dtbo and kernel >= 4.4.6 
> => let's compile it, it has been requested
> 
> The tough thing will be to keep consistency between KERNEL_DEVICETREE content 
> and kernel version to build.
> So as long as 4.1 is the layer's kernel preferred version, KERNEL_DEVICETREE 
> should only contain '-overlay.dtb' overlays, along with the next to be used 
> KERNEL_DEVICETREE variable (containing .dtbo) that is commented out.
> As soon as 4.4 is chosen, let's default to .dtbo overlays and comment out 
> KERNEL_DEVICETREE variable containing '-overlay.dtb' overlays.
> 
> What do you think about this behavior ?
> 
> As side notes, you may use some existing utility function to compare software 
> versions like bb.utils.vercmp_string_op and overlays filtering may be done in 
> a single pass : I've attached a proposal.
> 
> BR,
> François
> 
>> Le jeudi 21 juillet 2016 à 06:00 +0800, Herve Jourdain a écrit :
>> Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of 
>> .dtb.
>> Add support for both variants of overlays ("-overlay.dtb" and ".dtbo")
>> Change which variant needs to be supported based on the kernel version
>> 
>> CAUTION: when called from IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
>> 'STAGING_KERNEL_BUILDDIR' to not be expanded, causing 
>> get_kernelversion_file() to fail!
>> To avoid this problem, get_dts() and split_overlays() MUST be called with 
>> the kernel version parameter set, when called from IMAGE_CMD_rpi-sdimg!
>> 
>> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
>> ---
>>  classes/linux-ra

Re: [yocto] [meta-raspberrypi] linux-raspberrypi versions

[Herve Jourdain]

Hi Paul,

I had the same line of thoughts...
I believe 3.18 should be dropped, maybe even 4.1, default to 4.4, and maybe
add 4.7 to the mix, since 4.7 seems to be where the bulk of the work is done
now.

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Paul Barker
Sent: jeudi 21 juillet 2016 09:03
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi] linux-raspberrypi versions

Hi all,

I'm planning to look at the linux-raspberypi recipes once I've had time to
send V2 of my u-boot patches. I'd like to know people's thoughts on the
available kernel versions in the meta-raspberrypi layer:

Is anyone still using the linux-raspberrypi 3.18 recipe? The commit
referenced in SRCREV is from June 2015. I think it's probably time to retire
this unless anyone has a reason to keep it around.

Is there any reason to keep linux-raspberrypi 4.1 as the default recipe? The
last commit to the 4.1 branch was in April and the default branch on the
linux-raspberrypi GitHub repository has been
4.4 since then. I think we should change the default version to 4.4 unless
there's a good reason not to.

If there's no objections I'll send a couple of patches to drop 3.18 and
change the default to 4.4.

Thanks,
Paul Barker
--
___
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 v4 12/12] linux-raspberrypi-4.4: add patch to enable proper operation of renderD128 device

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0002-vc4-ioctl-rendering-allow.patch   | 29 ++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 2 files changed, 30 insertions(+)
 create 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
new file mode 100644
index 000..59d0ed7
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
@@ -0,0 +1,29 @@
+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 <herve.jourd...@neuf.fr>
+---
+
+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 b13925c..8fe5330 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -5,5 +5,6 @@ LINUX_VERSION ?= "4.4.13"
 SRCREV = "680be5e27a9593cf26079c6e5744a04cc2809d13"
 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.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 11/12] linux-rpi.inc: add the configuration options required to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-rpi.inc | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/recipes-kernel/linux/linux-rpi.inc 
b/recipes-kernel/linux/linux-rpi.inc
index 4b65fc2..3eeefee 100644
--- a/recipes-kernel/linux/linux-rpi.inc
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -111,6 +111,16 @@ do_configure_prepend() {
 # Activate CONFIG_LEGACY_PTYS
 kernel_configure_variable LEGACY_PTYS y
 
+# Activate the configuration options for VC4
+VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
"0", d)}"
+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_VC4 y
+kernel_configure_variable FB_BCM2708 n
+fi
+
 # Keep this the last line
 # Remove all modified configs and add the rest to .config
 sed -e "${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config'
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 10/12] mesa_%.bbappend: new file to add the correct configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/mesa/mesa_%.bbappend | 4 
 1 file changed, 4 insertions(+)
 create mode 100644 recipes-graphics/mesa/mesa_%.bbappend

diff --git a/recipes-graphics/mesa/mesa_%.bbappend 
b/recipes-graphics/mesa/mesa_%.bbappend
new file mode 100644
index 000..b182388
--- /dev/null
+++ b/recipes-graphics/mesa/mesa_%.bbappend
@@ -0,0 +1,4 @@
+PACKAGECONFIG_append_rpi = " gallium"
+GALLIUMDRIVERS_rpi = "vc4"
+DRIDRIVERS_rpi = ""
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 09/12] weston/weston_%.bbappend: modify configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/weston/weston_%.bbappend | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/recipes-graphics/weston/weston_%.bbappend 
b/recipes-graphics/weston/weston_%.bbappend
index 3ec311d..70f4360 100644
--- a/recipes-graphics/weston/weston_%.bbappend
+++ b/recipes-graphics/weston/weston_%.bbappend
@@ -1,7 +1,8 @@
-EXTRA_OECONF += "--enable-rpi-compositor \
- --disable-resize-optimization \
- --disable-setuid-install \
- --disable-xwayland-test \
- --disable-simple-egl-clients \
- WESTON_NATIVE_BACKEND=rpi-backend.so \
+PACKAGECONFIG_rpi_remove = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', ' fbdev', '', d)}"
+EXTRA_OECONF += "--disable-xwayland-test \
+ --disable-simple-egl-clients \
 "
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--enable-rpi-compositor', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-resize-optimization', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-setuid-install', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 08/12] wayland/weston_%.bbappend: modify configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/wayland/weston_%.bbappend | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/recipes-graphics/wayland/weston_%.bbappend 
b/recipes-graphics/wayland/weston_%.bbappend
index c3a7421..57b8079 100644
--- a/recipes-graphics/wayland/weston_%.bbappend
+++ b/recipes-graphics/wayland/weston_%.bbappend
@@ -1,4 +1,2 @@
-EXTRA_OECONF_append_rpi = "\
---enable-rpi-compositor \
-WESTON_NATIVE_BACKEND=rpi-backend.so \
-   "
+EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', '', ' --enable-rpi-compositor 
WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 07/12] rpi-config_git.bb: add v4c overlay to config.txt to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-bsp/bootfiles/rpi-config_git.bb | 10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4bc8eb7..f610718 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -13,12 +13,14 @@ SRC_URI = 
"git://github.com/Evilpaul/RPi-config.git;protocol=git;branch=master \
 
 S = "${WORKDIR}/git"
 
-PR = "r4"
+PR = "r5"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
 PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
 
+VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", "0", 
d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -102,6 +104,12 @@ do_deploy() {
 echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# VC4 Graphics support
+if [ "${VC4GRAPHICS}" = "1" ]; then
+echo "# Enable VC4 Graphics" >> 
${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=vc4-kms-v3d,${VC4_CMA_SIZE}" >> 
${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 06/12] raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi3.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index cb6056e..438c6e6 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -9,3 +9,5 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
 include conf/machine/raspberrypi2.conf
 
 SERIAL_CONSOLE = "115200 ttyS0"
+VC4_CMA_SIZE ?= "cma-256"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 05/12] raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi2.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf
index d50ef70..3f13dc0 100644
--- a/conf/machine/raspberrypi2.conf
+++ b/conf/machine/raspberrypi2.conf
@@ -10,3 +10,5 @@ include conf/machine/include/rpi-base.inc
 SERIAL_CONSOLE = "115200 ttyAMA0"
 
 UBOOT_MACHINE = "rpi_2_config"
+VC4_CMA_SIZE ?= "cma-256"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 04/12] raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi0.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf
index ccf9ae7..0df9121 100644
--- a/conf/machine/raspberrypi0.conf
+++ b/conf/machine/raspberrypi0.conf
@@ -6,3 +6,5 @@ MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
 include conf/machine/raspberrypi.conf
 
 SERIAL_CONSOLE = "115200 ttyAMA0"
+VC4_CMA_SIZE ?= "cma-128"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 02/12] rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 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 47eb23b..aabc131 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,6 +37,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/w1-gpio.dtbo \
 overlays/w1-gpio-pullup.dtbo \
 overlays/pi3-miniuart-bt.dtbo \
+overlays/vc4-kms-v3d.dtbo \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 03/12] raspberrypi.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf
index 72beeb8..df8194c 100644
--- a/conf/machine/raspberrypi.conf
+++ b/conf/machine/raspberrypi.conf
@@ -10,3 +10,5 @@ include conf/machine/include/rpi-base.inc
 SERIAL_CONSOLE = "115200 ttyAMA0"
 
 UBOOT_MACHINE = "rpi_config"
+VC4_CMA_SIZE_raspberrypi ?= "cma-64"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 01/12] rpi-default-providers.inc: change default providers to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/include/rpi-default-providers.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/conf/machine/include/rpi-default-providers.inc 
b/conf/machine/include/rpi-default-providers.inc
index 359870d..078e9d6 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -2,8 +2,8 @@
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
-PREFERRED_PROVIDER_virtual/egl ?= "userland"
-PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
-PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
+PREFERRED_PROVIDER_virtual/egl ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "userland", d)}"
+PREFERRED_PROVIDER_virtual/libgles2 ?= 
"${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "userland", 
d)}"
+PREFERRED_PROVIDER_virtual/libgl ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "mesa-gl", d)}"
+PREFERRED_PROVIDER_virtual/mesa ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "mesa-gl", d)}"
 PREFERRED_PROVIDER_jpeg ?= "jpeg"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 00/12] Support for VC4 graphics driver

[Herve Jourdain]

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

[yocto] [meta-raspberrypi][PATCH v6 4/4] sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both extensions for overlays (".dtb" and ".dtbo")

CAUTION: in IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_dts() to not being 
able to get the kernel version!
To avoid this problem, the kernel version is added in a new variable outside 
the scope of IMAGE_CMD_rpi-sdimg, and its value passed to get_dts() and 
split_overlays()!

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 classes/sdcard_image-rpi.bbclass | 15 +--
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 57cefea..a04204a 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -75,6 +75,8 @@ IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
 IMAGE_CMD_rpi-sdimg[vardepsexclude] += "IMAGEDATESTAMP"
 IMAGE_CMD_rpi-sdimg[vardepsexclude] += "DATETIME"
 
+RPI_KERNEL_VERSION := 
"${@get_kernelversion_file('${STAGING_KERNEL_BUILDDIR}')}"
+
 IMAGE_CMD_rpi-sdimg () {
 
# Align partitions
@@ -85,7 +87,7 @@ IMAGE_CMD_rpi-sdimg () {
echo "Creating filesystem with Boot partition ${BOOT_SPACE_ALIGNED} KiB 
and RootFS $ROOTFS_SIZE KiB"
 
# Check if we are building with device tree support
-   DTS="${@get_dts(d, None)}"
+   DTS="${@get_dts(d, '${RPI_KERNEL_VERSION}')}"
 
# Initialize sdcard image file
dd if=/dev/zero of=${SDIMG} bs=1024 count=0 seek=${SDIMG_SIZE}
@@ -105,9 +107,9 @@ IMAGE_CMD_rpi-sdimg () {
mkfs.vfat -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img 
$BOOT_BLOCKS
mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles/* 
::/
if test -n "${DTS}"; then
-   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' string and will be put in a dedicated folder
-   DT_OVERLAYS="${@split_overlays(d, 0)}"
-   DT_ROOT="${@split_overlays(d, 1)}"
+   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' (4.1.x) or by '.dtbo' (4.4.9+) string and will be put in a 
dedicated folder
+   DT_OVERLAYS="${@split_overlays(d, '${RPI_KERNEL_VERSION}', 0)}"
+   DT_ROOT="${@split_overlays(d, '${RPI_KERNEL_VERSION}', 1)}"
 
# Copy board device trees to root folder
for DTB in ${DT_ROOT}; do
@@ -119,9 +121,10 @@ IMAGE_CMD_rpi-sdimg () {
# Copy device tree overlays to dedicated folder
mmd -i ${WORKDIR}/boot.img overlays
for DTB in ${DT_OVERLAYS}; do
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_EXT=${DTB##*.}
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
 
-   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb 
::overlays/${DTB_BASE_NAME}.dtb
+   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.${DTB_EXT} 
::overlays/${DTB_BASE_NAME}.${DTB_EXT}
done
fi
case "${KERNEL_IMAGETYPE}" in
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v6 3/4] linux-raspberrypi-base.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both variants of overlays ("-overlay.dtb" and ".dtbo")
Change which variant needs to be supported based on the kernel version

CAUTION: when called from IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_kernelversion_file() 
to fail!
To avoid this problem, get_dts() and split_overlays() MUST be called with the 
kernel version parameter set, when called from IMAGE_CMD_rpi-sdimg!

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 classes/linux-raspberrypi-base.bbclass | 19 ---
 1 file changed, 12 insertions(+), 7 deletions(-)

diff --git a/classes/linux-raspberrypi-base.bbclass 
b/classes/linux-raspberrypi-base.bbclass
index 40beef1..930fc44 100644
--- a/classes/linux-raspberrypi-base.bbclass
+++ b/classes/linux-raspberrypi-base.bbclass
@@ -1,7 +1,8 @@
 inherit linux-kernel-base
 
-
 def get_dts(d, ver):
+import re
+
 staging_dir = d.getVar("STAGING_KERNEL_BUILDDIR", True)
 dts = d.getVar("KERNEL_DEVICETREE", True)
 
@@ -20,20 +21,24 @@ def get_dts(d, ver):
 
 # Always turn off device tree support for kernel's < 3.18
 try:
-if int(min_ver[0]) <= 3:
-if int(min_ver[1]) < 18:
-dts = ""
+if int(min_ver[0]) >= 4:
+if (int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and 
int(min_ver[2]) < 6):
+dts = ' '.join([(re.sub(r'(.*)\.dtbo$', r'\1-overlay.dtb', x)) 
for x in dts.split()])
+elif int(min_ver[1]) < 18:
+dts = ""
 except IndexError:
 min_ver = None
 
 return dts
 
 
-def split_overlays(d, out):
-dts = get_dts(d, None)
+def split_overlays(d, ver, out):
+dts = get_dts(d, ver)
 if out:
 overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter_out('\S+\.dtbo$', overlays, d)
 else:
-overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d) + \
+   " " + oe.utils.str_filter('\S+\.dtbo$', dts, d)
 
 return overlays
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v6 2/4] rpi-base.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for .dtbo variant of overlays for the default KERNEL_DEVICETREE 
variable
(the list will be turned into "-overlay.dtb" by linux-raspberry-base.bbclass, 
if needed, depending on the kernel version)

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/include/rpi-base.inc | 30 +++---
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 56ca83e..47eb23b 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -22,21 +22,21 @@ KERNEL_DEVICETREE ?= " \
 bcm2709-rpi-2-b.dtb \
 bcm2710-rpi-3-b.dtb \
 \
-overlays/hifiberry-amp-overlay.dtb \
-overlays/hifiberry-dac-overlay.dtb \
-overlays/hifiberry-dacplus-overlay.dtb \
-overlays/hifiberry-digi-overlay.dtb \
-overlays/i2c-rtc-overlay.dtb \
-overlays/iqaudio-dac-overlay.dtb \
-overlays/iqaudio-dacplus-overlay.dtb \
-overlays/lirc-rpi-overlay.dtb \
-overlays/pitft22-overlay.dtb \
-overlays/pitft28-resistive-overlay.dtb \
-overlays/pps-gpio-overlay.dtb \
-overlays/rpi-ft5406-overlay.dtb \
-overlays/w1-gpio-overlay.dtb \
-overlays/w1-gpio-pullup-overlay.dtb \
-overlays/pi3-miniuart-bt-overlay.dtb \
+overlays/hifiberry-amp.dtbo \
+overlays/hifiberry-dac.dtbo \
+overlays/hifiberry-dacplus.dtbo \
+overlays/hifiberry-digi.dtbo \
+overlays/i2c-rtc.dtbo \
+overlays/iqaudio-dac.dtbo \
+overlays/iqaudio-dacplus.dtbo \
+overlays/lirc-rpi.dtbo \
+overlays/pitft22.dtbo \
+overlays/pitft28-resistive.dtbo \
+overlays/pps-gpio.dtbo \
+overlays/rpi-ft5406.dtbo \
+overlays/w1-gpio.dtbo \
+overlays/w1-gpio-pullup.dtbo \
+overlays/pi3-miniuart-bt.dtbo \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v6 1/4] linux-raspberrypi_4.4.bb: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Patch the kernel, which has faulty rules to generate .dtbo the way yocto does

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0001-fix-dtbo-rules.patch  | 44 ++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 2 files changed, 45 insertions(+)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
new file mode 100644
index 000..5113e23
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
@@ -0,0 +1,44 @@
+From 13c8784da3dbd977f64cec740eba775b6fab11c2 Mon Sep 17 00:00:00 2001
+From: Herve Jourdain <herve.jourd...@neuf.fr>
+Date: Fri, 20 May 2016 16:02:23 +0800
+Subject: [yocto][meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc:
+ support for .dtbo files for dtb overlays
+
+Upstream-Status: Pending
+
+Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
+Patch the kernel, which has faulty rules to generate .dtbo the way yocto does
+
+Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
+---
+ .../0001-fix-dtbo-rules.patch  | 27 ++
+ 1 file changed, 27 insertions(+)
+ create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
+
+diff --git a/arch/arm/Makefile b/arch/arm/Makefile
+index a2e7cf7..673c1cb 100644
+--- a/arch/arm/Makefile
 b/arch/arm/Makefile
+@@ -333,6 +333,8 @@ $(INSTALL_TARGETS):
+ 
+ %.dtb: | scripts
+   $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++%.dtbo: | scripts
++  $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
+ 
+ PHONY += dtbs dtbs_install
+ 
+diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
+index 3079c4f..6cc3766 100644
+--- a/scripts/Makefile.lib
 b/scripts/Makefile.lib
+@@ -293,7 +293,8 @@ $(obj)/%.dtb: $(src)/%.dts FORCE
+   $(call if_changed_dep,dtc)
+ 
+ quiet_cmd_dtco = DTCO$@
+-cmd_dtco = $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
++cmd_dtco = mkdir -p $(dir ${dtc-tmp}) ; \
++  $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
+   $(objtree)/scripts/dtc/dtc -@ -H epapr -O dtb -o $@ -b 0 \
+   -i $(dir $<) $(DTC_FLAGS) \
+   -d $(depfile).dtc.tmp $(dtc-tmp) ; \
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 3291ffd..b13925c 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -4,5 +4,6 @@ LINUX_VERSION ?= "4.4.13"
 
 SRCREV = "680be5e27a9593cf26079c6e5744a04cc2809d13"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
+   file://0001-fix-dtbo-rules.patch \
 "
 require linux-raspberrypi.inc
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v6 0/4] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

[Herve Jourdain]

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

[yocto] [meta-raspberrypi][PATCH 1/1] Patch for implementing GstGlMemoryEGL for gstreamer 1.8.2

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0001-gl-implement-GstGlMemoryEGL.patch | 494 +
 .../gstreamer1.0-plugins-bad_1.8.2.bbappend|   6 +
 2 files changed, 500 insertions(+)
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad-1.8.2/0001-gl-implement-GstGlMemoryEGL.patch
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.8.2.bbappend

diff --git 
a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad-1.8.2/0001-gl-implement-GstGlMemoryEGL.patch
 
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad-1.8.2/0001-gl-implement-GstGlMemoryEGL.patch
new file mode 100644
index 000..bd7258c
--- /dev/null
+++ 
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad-1.8.2/0001-gl-implement-GstGlMemoryEGL.patch
@@ -0,0 +1,494 @@
+From 806bbe75b0b6947f589bce3960c28fee51b5c6c2 Mon Sep 17 00:00:00 2001
+From: Gwang Yoon Hwang <y...@igalia.com>
+Date: Thu, 21 Jan 2016 22:18:17 +0900
+Subject: [PATCH] gl: implement GstGLMemoryEGL
+
+Because current GstEGLImageMemory does not inherit GstGLMemory, GLUpload
+allocates additional GLMemory and upload the decoded contents from the decoder
+which uses EGLImage (e.g. gst-omx in RPi).
+
+This work adds GstGLMemoryEGL to avoid this overhead. Decoders allocate
+GstGLMemoryEGL and decode its contents to the EGLImage of GstGLMemoryEGL.  And
+GLUpload uses this memory without allocation of additional textures and blit
+operations.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=760916
+---
+ gst-libs/gst/gl/egl/Makefile.am|   2 +
+ gst-libs/gst/gl/egl/gstgldisplay_egl.c |   2 +
+ gst-libs/gst/gl/egl/gstglmemoryegl.c   | 241 +
+ gst-libs/gst/gl/egl/gstglmemoryegl.h   | 108 +++
+ gst-libs/gst/gl/gstgl_fwd.h|   4 +
+ gst-libs/gst/gl/gstgldisplay.c |   2 +
+ gst-libs/gst/gl/gstglupload.c  |   8 ++
+ 7 files changed, 367 insertions(+)
+ create mode 100644 gst-libs/gst/gl/egl/gstglmemoryegl.c
+ create mode 100644 gst-libs/gst/gl/egl/gstglmemoryegl.h
+
+diff --git a/gst-libs/gst/gl/egl/Makefile.am b/gst-libs/gst/gl/egl/Makefile.am
+index b808178..878f16c 100644
+--- a/gst-libs/gst/gl/egl/Makefile.am
 b/gst-libs/gst/gl/egl/Makefile.am
+@@ -5,6 +5,7 @@ noinst_LTLIBRARIES = libgstgl-egl.la
+ libgstgl_egl_la_SOURCES = \
+   gstgldisplay_egl.c \
+   gstglcontext_egl.c \
++  gstglmemoryegl.c \
+   gsteglimagememory.c
+ 
+ noinst_HEADERS =
+@@ -13,6 +14,7 @@ libgstgl_eglincludedir = 
$(includedir)/gstreamer-@GST_API_VERSION@/gst/gl/egl
+ libgstgl_eglinclude_HEADERS = \
+   gstgldisplay_egl.h \
+   gstglcontext_egl.h \
++  gstglmemoryegl.h \
+   gsteglimagememory.h \
+   gstegl.h
+ 
+diff --git a/gst-libs/gst/gl/egl/gstgldisplay_egl.c 
b/gst-libs/gst/gl/egl/gstgldisplay_egl.c
+index 9acf4f0..20816c2 100644
+--- a/gst-libs/gst/gl/egl/gstgldisplay_egl.c
 b/gst-libs/gst/gl/egl/gstgldisplay_egl.c
+@@ -24,6 +24,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ GST_DEBUG_CATEGORY_STATIC (gst_gl_display_debug);
+ #define GST_CAT_DEFAULT gst_gl_display_debug
+@@ -51,6 +52,7 @@ gst_gl_display_egl_init (GstGLDisplayEGL * display_egl)
+   display_egl->foreign_display = FALSE;
+ 
+   gst_egl_image_memory_init ();
++  gst_gl_memory_egl_init_once ();
+ }
+ 
+ static void
+diff --git a/gst-libs/gst/gl/egl/gstglmemoryegl.c 
b/gst-libs/gst/gl/egl/gstglmemoryegl.c
+new file mode 100644
+index 000..03cf432
+--- /dev/null
 b/gst-libs/gst/gl/egl/gstglmemoryegl.c
+@@ -0,0 +1,241 @@
++/*
++ * GStreamer
++ * Copyright (C) 2012 Collabora Ltd.
++ *   @author: Sebastian Dröge <sebastian.dro...@collabora.co.uk>
++ * Copyright (C) 2014 Julien Isorce <julien.iso...@gmail.com>
++ * Copyright (C) 2015 Igalia
++ *Author: Gwang Yoon Hwang <y...@igalia.com>
++ *
++ * This library is free software; you can redistribute it and/or
++ * modify it under the terms of the GNU Library General Public
++ * License as published by the Free Software Foundation; either
++ * version 2 of the License, or (at your option) any later version.
++ *
++ * This library is distributed in the hope that it will be useful,
++ * but WITHOUT ANY WARRANTY; without even the implied warranty of
++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
++ * Library General Public License for more details.
++ *
++ * You should have received a copy of the GNU Library General Public
++ * License along with this library; if not, write to the
++ * Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
++ * Boston, MA 02110-1301, USA.
++ */
++
++#ifdef HAVE_CONFIG_H
++#include "config.h"
++#endif
++
++#include 
++
++#include 
++
++static GstAllocator *_gl_memory_egl_allocator;
++
++GST_DEBUG_CATEGORY_STATIC (GST_CAT_GL_MEMORY);
++#define GST_CAT_DEFAULT GST_CAT_GL_MEMORY
++
++#define parent_class gst_gl_memory_egl_allocator_parent_class
++G_DEFINE_TYPE (GstGLMemo

[yocto] [meta-raspberrypi][PATCH 0/1] Patch for implementing GstGlMemoryEGL for gstreamer 1.8.2

[Herve Jourdain]

Commit 2745399f75d7564fcc586d0365ff73be47849d0e breaks compilation of 
gstreamer1.0-omx on raspberrypi.
This is because it relies on a patch to gstreamer 1.8.2, that seems was not 
added/sent.
This patch adds the missing patch, but in meta-raspberrypi instead of oe, to 
fix the issue where it happens - currently in meta-raspberrypi.
But it should probably be moved to meta/recipes-multimedia/gstreamer once it's 
properly tested.

Herve Jourdain (1):
  Patch for implementing GstGlMemoryEGL for gstreamer 1.8.2

 .../0001-gl-implement-GstGlMemoryEGL.patch | 494 +
 .../gstreamer1.0-plugins-bad_1.8.2.bbappend|   6 +
 2 files changed, 500 insertions(+)
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad-1.8.2/0001-gl-implement-GstGlMemoryEGL.patch
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.8.2.bbappend

-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi] problem with building gstreamer1.0-omx

[Herve Jourdain]

Hi,

I have the exact same problem...
I believe the patch that Khem has sent depends on another patch in
gstreamer, that wasn't sent...
I'll send a patch soon to fix that "locally" (with a .bbappend to gstreamer
in meta-raspberrypi), though it should end up ultimately in oe, once
properly tested on other platforms.

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of piotr.lewicki
Sent: mercredi 20 juillet 2016 13:58
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi] problem with building gstreamer1.0-omx

Hi,

After recent update of meta-raspberrypi I have a problem with building
gstreamer1.0-omx package.

I have one strange warning and one error due to missing gstglmemoryegl.h
file (marked with pluses below):

| In file included from ../../gst-omx-1.2.0/omx/gstomx.h:48:0,
|  from ../../gst-omx-1.2.0/omx/gstomx.c:30:
| 
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/sysroots/raspberryp
i3/usr/include/IL/OMX_Core.h:45:4: 
warning: #warning OMX_SKIP64BIT is not defined - this will be incompatible
with the VC GPU code. [-Wcpp]
|#warning OMX_SKIP64BIT is not defined - this will be
incompatible with the VC GPU code.
| ^
| ../../gst-omx-1.2.0/omx/gstomxvideodec.c:41:39: fatal error: 
gst/gl/egl/gstglmemoryegl.h: No such file or directory
| compilation terminated.
| make[2]: *** [libgstomx_la-gstomxvideodec.lo] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory
`/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-
poky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/build/omx'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-
poky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/build'
| make: *** [all] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/tmp/work/raspberrypi3-p
oky-linux-gnueabi/gstreamer1.0-omx/1.2.0-r1/temp/log.do_compile.4424)
ERROR: Task
/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/../layers/poky/meta/rec
ipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bb:do_compile
(/home/piotr.lewicki/yocto-raspberry/2016-07-18/build/../layers/poky/meta/re
cipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bb:do_compile)
failed with exit code '1'


Do you have any idea why I have those messages?

I use gstreamer1.0 1.8.2 and corresponding plugin versions.

I have noticed that after removing
file://0007-omxvideodec-Use-gstglmemoryegl-for-the-RPi.patch from
gstreamer1.0-omx_1.2.0.bbappend - the package builds..

Any hint why I don't have this gstglmemoryegl.h header?


Thanks,

Piotr

--
___
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] ***SPAM*** Re: [meta-raspberrypi][PATCH v5 3/4] linux-raspberrypi-base.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Hi François,

 

Sorry for the late response, I’ve been busy on other things recently.

 

Actually, it’s not a typo, it’s just that we’re using the “overlays” variable 
for storing 2 things, depending on the value of the parameter “out” of the 
split_overlays() function:

1. either all the overlays

2. or all the dtb that are not overlays

 

The case you’re mentioning is for “out” being selected, so you want to exclude 
all the overlays from the dts, and store that in the “overlays” variable (the 
naming of the variable is a bit unfortunate in this context, I must admit, but 
I only re-used the existing one).

So now, you not only need to exclude the “-overlay.dtb” files, but also the 
“.dtbo” files.

So the second pass takes the output of the first pass, in “overlays”, and 
filters out the “.dtbo” if any.

 

Hope that helps,

 

Hervé

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Francois Muller
Sent: samedi 25 juin 2016 17:48
To: yocto@yoctoproject.org
Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi][PATCH v5 3/4] 
linux-raspberrypi-base.bbclass: support for .dtbo files for dtb overlays

 

Hi Hervé,

 

I haven't tested your patch yet, but while reviewing the diff I'm a bit 
surprised about this:

 overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)

+overlays = oe.utils.str_filter_out('\S+\.dtbo$', overlays, d)

Shouldn't .dtbo files be filtered out from 'dts' instead of 'overlays' in the 
added line?

Seems like a typo to me.

 

BR,

François

 

Le vendredi 17 juin 2016 à 23:35 +0800, Herve Jourdain a écrit :

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both variants of overlays ("-overlay.dtb" and ".dtbo")
Change which variant needs to be supported based on the kernel version
 
CAUTION: when called from IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_kernelversion_file() 
to fail!
To avoid this problem, get_dts() and split_overlays() MUST be called with the 
kernel version parameter set, when called from IMAGE_CMD_rpi-sdimg!
 
Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr 
<mailto:herve.jourd...@neuf.fr> >
---
 classes/linux-raspberrypi-base.bbclass | 19 ---
 1 file changed, 12 insertions(+), 7 deletions(-)
 
diff --git a/classes/linux-raspberrypi-base.bbclass 
b/classes/linux-raspberrypi-base.bbclass
index 40beef1..930fc44 100644
--- a/classes/linux-raspberrypi-base.bbclass
+++ b/classes/linux-raspberrypi-base.bbclass
@@ -1,7 +1,8 @@
 inherit linux-kernel-base
 
-
 def get_dts(d, ver):
+import re
+
 staging_dir = d.getVar("STAGING_KERNEL_BUILDDIR", True)
 dts = d.getVar("KERNEL_DEVICETREE", True)
 
@@ -20,20 +21,24 @@ def get_dts(d, ver):
 
 # Always turn off device tree support for kernel's < 3.18
 try:
-if int(min_ver[0]) <= 3:
-if int(min_ver[1]) < 18:
-dts = ""
+if int(min_ver[0]) >= 4:
+if (int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and 
int(min_ver[2]) < 6):
+dts = ' '.join([(re.sub(r'(.*)\.dtbo$', r'\1-overlay.dtb', x)) 
for x in dts.split()])
+elif int(min_ver[1]) < 18:
+dts = ""
 except IndexError:
 min_ver = None
 
 return dts
 
 
-def split_overlays(d, out):
-dts = get_dts(d, None)
+def split_overlays(d, ver, out):
+dts = get_dts(d, ver)
 if out:
 overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter_out('\S+\.dtbo$', overlays, d)
 else:
-overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d) + \
+   " " + oe.utils.str_filter('\S+\.dtbo$', dts, d)
 
 return overlays
-- 
2.7.4
 

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

[yocto] [meta-raspberrypi][PATCH v5 4/4] sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both extensions for overlays (".dtb" and ".dtbo")

CAUTION: in IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_dts() to not being 
able to get the kernel version!
To avoid this problem, the kernel version is added in a new variable outside 
the scope of IMAGE_CMD_rpi-sdimg, and its value passed to get_dts() and 
split_overlays()!

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 classes/sdcard_image-rpi.bbclass | 15 +--
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 4dfd7a3..560d2c3 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -74,6 +74,8 @@ FATPAYLOAD ?= ""
 IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
 IMAGE_CMD_rpi-sdimg[vardepsexclude] = "IMAGEDATESTAMP"
 
+RPI_KERNEL_VERSION := 
"${@get_kernelversion_file('${STAGING_KERNEL_BUILDDIR}')}"
+
 IMAGE_CMD_rpi-sdimg () {
 
# Align partitions
@@ -84,7 +86,7 @@ IMAGE_CMD_rpi-sdimg () {
echo "Creating filesystem with Boot partition ${BOOT_SPACE_ALIGNED} KiB 
and RootFS $ROOTFS_SIZE KiB"
 
# Check if we are building with device tree support
-   DTS="${@get_dts(d, None)}"
+   DTS="${@get_dts(d, '${RPI_KERNEL_VERSION}')}"
 
# Initialize sdcard image file
dd if=/dev/zero of=${SDIMG} bs=1024 count=0 seek=${SDIMG_SIZE}
@@ -110,9 +112,9 @@ IMAGE_CMD_rpi-sdimg () {
;;
*)
if test -n "${DTS}"; then
-   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' string and will be put in a dedicated folder
-   DT_OVERLAYS="${@split_overlays(d, 0)}"
-   DT_ROOT="${@split_overlays(d, 1)}"
+   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' (4.1.x) or by '.dtbo' (4.4.9+) string and will be put in a 
dedicated folder
+   DT_OVERLAYS="${@split_overlays(d, 
'${RPI_KERNEL_VERSION}', 0)}"
+   DT_ROOT="${@split_overlays(d, '${RPI_KERNEL_VERSION}', 
1)}"
 
# Copy board device trees to root folder
for DTB in ${DT_ROOT}; do
@@ -124,9 +126,10 @@ IMAGE_CMD_rpi-sdimg () {
# Copy device tree overlays to dedicated folder
mmd -i ${WORKDIR}/boot.img overlays
for DTB in ${DT_OVERLAYS}; do
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_EXT=${DTB##*.}
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
 
-   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb 
::overlays/${DTB_BASE_NAME}.dtb
+   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.${DTB_EXT} 
::overlays/${DTB_BASE_NAME}.${DTB_EXT}
done
fi
mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin 
::${SDIMG_KERNELIMAGE}
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v5 3/4] linux-raspberrypi-base.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both variants of overlays ("-overlay.dtb" and ".dtbo")
Change which variant needs to be supported based on the kernel version

CAUTION: when called from IMAGE_CMD_rpi-sdimg, 'TMPDIR' is not set, causing 
'STAGING_KERNEL_BUILDDIR' to not be expanded, causing get_kernelversion_file() 
to fail!
To avoid this problem, get_dts() and split_overlays() MUST be called with the 
kernel version parameter set, when called from IMAGE_CMD_rpi-sdimg!

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 classes/linux-raspberrypi-base.bbclass | 19 ---
 1 file changed, 12 insertions(+), 7 deletions(-)

diff --git a/classes/linux-raspberrypi-base.bbclass 
b/classes/linux-raspberrypi-base.bbclass
index 40beef1..930fc44 100644
--- a/classes/linux-raspberrypi-base.bbclass
+++ b/classes/linux-raspberrypi-base.bbclass
@@ -1,7 +1,8 @@
 inherit linux-kernel-base
 
-
 def get_dts(d, ver):
+import re
+
 staging_dir = d.getVar("STAGING_KERNEL_BUILDDIR", True)
 dts = d.getVar("KERNEL_DEVICETREE", True)
 
@@ -20,20 +21,24 @@ def get_dts(d, ver):
 
 # Always turn off device tree support for kernel's < 3.18
 try:
-if int(min_ver[0]) <= 3:
-if int(min_ver[1]) < 18:
-dts = ""
+if int(min_ver[0]) >= 4:
+if (int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and 
int(min_ver[2]) < 6):
+dts = ' '.join([(re.sub(r'(.*)\.dtbo$', r'\1-overlay.dtb', x)) 
for x in dts.split()])
+elif int(min_ver[1]) < 18:
+dts = ""
 except IndexError:
 min_ver = None
 
 return dts
 
 
-def split_overlays(d, out):
-dts = get_dts(d, None)
+def split_overlays(d, ver, out):
+dts = get_dts(d, ver)
 if out:
 overlays = oe.utils.str_filter_out('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter_out('\S+\.dtbo$', overlays, d)
 else:
-overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d)
+overlays = oe.utils.str_filter('\S+\-overlay\.dtb$', dts, d) + \
+   " " + oe.utils.str_filter('\S+\.dtbo$', dts, d)
 
 return overlays
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v5 2/4] rpi-base.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for .dtbo variant of overlays for the default KERNEL_DEVICETREE 
variable
(the list will be turned into "-overlay.dtb" by linux-raspberry-base.bbclass, 
if needed, depending on the kernel version)

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/include/rpi-base.inc | 30 +++---
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 56ca83e..47eb23b 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -22,21 +22,21 @@ KERNEL_DEVICETREE ?= " \
 bcm2709-rpi-2-b.dtb \
 bcm2710-rpi-3-b.dtb \
 \
-overlays/hifiberry-amp-overlay.dtb \
-overlays/hifiberry-dac-overlay.dtb \
-overlays/hifiberry-dacplus-overlay.dtb \
-overlays/hifiberry-digi-overlay.dtb \
-overlays/i2c-rtc-overlay.dtb \
-overlays/iqaudio-dac-overlay.dtb \
-overlays/iqaudio-dacplus-overlay.dtb \
-overlays/lirc-rpi-overlay.dtb \
-overlays/pitft22-overlay.dtb \
-overlays/pitft28-resistive-overlay.dtb \
-overlays/pps-gpio-overlay.dtb \
-overlays/rpi-ft5406-overlay.dtb \
-overlays/w1-gpio-overlay.dtb \
-overlays/w1-gpio-pullup-overlay.dtb \
-overlays/pi3-miniuart-bt-overlay.dtb \
+overlays/hifiberry-amp.dtbo \
+overlays/hifiberry-dac.dtbo \
+overlays/hifiberry-dacplus.dtbo \
+overlays/hifiberry-digi.dtbo \
+overlays/i2c-rtc.dtbo \
+overlays/iqaudio-dac.dtbo \
+overlays/iqaudio-dacplus.dtbo \
+overlays/lirc-rpi.dtbo \
+overlays/pitft22.dtbo \
+overlays/pitft28-resistive.dtbo \
+overlays/pps-gpio.dtbo \
+overlays/rpi-ft5406.dtbo \
+overlays/w1-gpio.dtbo \
+overlays/w1-gpio-pullup.dtbo \
+overlays/pi3-miniuart-bt.dtbo \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v5 1/4] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Patch the kernel, which has faulty rules to generate .dtbo the way yocto does

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0001-fix-dtbo-rules.patch  | 44 ++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 2 files changed, 45 insertions(+)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
new file mode 100644
index 000..5113e23
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
@@ -0,0 +1,44 @@
+From 13c8784da3dbd977f64cec740eba775b6fab11c2 Mon Sep 17 00:00:00 2001
+From: Herve Jourdain <herve.jourd...@neuf.fr>
+Date: Fri, 20 May 2016 16:02:23 +0800
+Subject: [yocto][meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc:
+ support for .dtbo files for dtb overlays
+
+Upstream-Status: Pending
+
+Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
+Patch the kernel, which has faulty rules to generate .dtbo the way yocto does
+
+Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
+---
+ .../0001-fix-dtbo-rules.patch  | 27 ++
+ 1 file changed, 27 insertions(+)
+ create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
+
+diff --git a/arch/arm/Makefile b/arch/arm/Makefile
+index a2e7cf7..673c1cb 100644
+--- a/arch/arm/Makefile
 b/arch/arm/Makefile
+@@ -333,6 +333,8 @@ $(INSTALL_TARGETS):
+ 
+ %.dtb: | scripts
+   $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++%.dtbo: | scripts
++  $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
+ 
+ PHONY += dtbs dtbs_install
+ 
+diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
+index 3079c4f..6cc3766 100644
+--- a/scripts/Makefile.lib
 b/scripts/Makefile.lib
+@@ -293,7 +293,8 @@ $(obj)/%.dtb: $(src)/%.dts FORCE
+   $(call if_changed_dep,dtc)
+ 
+ quiet_cmd_dtco = DTCO$@
+-cmd_dtco = $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
++cmd_dtco = mkdir -p $(dir ${dtc-tmp}) ; \
++  $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
+   $(objtree)/scripts/dtc/dtc -@ -H epapr -O dtb -o $@ -b 0 \
+   -i $(dir $<) $(DTC_FLAGS) \
+   -d $(depfile).dtc.tmp $(dtc-tmp) ; \
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index ba47b22..789fef1 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -4,5 +4,6 @@ LINUX_VERSION ?= "4.4.9"
 
 SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
+   file://0001-fix-dtbo-rules.patch \
 "
 require linux-raspberrypi.inc
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v5 0/4] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

[Herve Jourdain]

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.inc: 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

Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Hi Andrei,

So I've found a solution, I'll send a patch for it soon, but I'd like to
know your opinion, not sure you will like it...
In sdcard_image-rpi.bbclass, just before defining IMAGE_CMD_rpi-sdimg, I
add:
RPI_KERNEL_VERSION :=
"${@get_kernelversion_file('${STAGING_KERNEL_BUILDDIR}')}'

Then inside of IMAGE_CMD_rpi-sdimg, I use that variable when calling
get_dts(), instead of None, for the kernel version.
Also, I needed to add a 'version' parameter to split_overlays, because
without it it has the same problem - called from the same IMAGE_CMD without
TMPDIR.

It works, but it means that contrary to what there was before,
sdcard_image-rpi.bbclass needs to get "awareness" of the kernel version.
Do you think it's a problem?
If it is, what are your suggestions?

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Herve Jourdain
Sent: vendredi 17 juin 2016 09:51
To: 'Andrei Gherzan' <and...@gherzan.ro>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support
for .dtbo files for dtb overlays

Hi Andrei,

Sorry for the delay, but I've met some unexpected issue: when calling
IMAGE_CMD (which is the code that lives in sdcard_image-rpi.bbclass in
raspberrypi's case), TMPDIR is willfully deleted before the call...
But STAGING_KERNEL_BUILDDIR, which is used to find out what version of
kernel is used in case it's not passed, actually depends on it, so it's not
expanded.
So the kernel version test in linux-raspberrypi-base.bbclass fails when
get_dts is called from sdcard_image-rpi.bbclass without specifying the
kernel version - then just returns the default KERNEL_DEVICETREE value!

I believe it happens the same when testing with 3.18 - but I didn't build
3.18, and maybe it doesn't matter for building the image.

I'm trying to work around this issue without too much side-effects, and I
haven't found a nice solution so far - short from removing the line that
deletes TMPDIR...

Any suggestion is appreciated.

Herve

-Original Message-
From: Andrei Gherzan [mailto:and...@gherzan.ro]
Sent: mercredi 15 juin 2016 02:12
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support
for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:33AM +0800, Herve Jourdain wrote:
> Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead 
> of
.dtb.
> Add support for both variants of overlays ("-overlay.dtb" and ".dtbo") 
> for the default KERNEL_DEVICETREE variable
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  conf/machine/include/rpi-base.inc | 36
> +++-
>  1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/conf/machine/include/rpi-base.inc
> b/conf/machine/include/rpi-base.inc
> index 56ca83e..2c9d8e0 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -16,7 +16,7 @@ XSERVER = " \
>  "
>
>  # Really supported starting from linux-raspberrypi 3.18.y only 
> -KERNEL_DEVICETREE ?= " \
> +KERNEL_DEVICETREE_OVERLAYS_DTB = " \
>  bcm2708-rpi-b.dtb \
>  bcm2708-rpi-b-plus.dtb \
>  bcm2709-rpi-2-b.dtb \
> @@ -38,6 +38,40 @@ KERNEL_DEVICETREE ?= " \
>  overlays/w1-gpio-pullup-overlay.dtb \
>  overlays/pi3-miniuart-bt-overlay.dtb \
>  "
> +KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
> +bcm2708-rpi-b.dtb \
> +bcm2708-rpi-b-plus.dtb \
> +bcm2709-rpi-2-b.dtb \
> +bcm2710-rpi-3-b.dtb \
> +\
> +overlays/hifiberry-amp.dtbo \
> +overlays/hifiberry-dac.dtbo \
> +overlays/hifiberry-dacplus.dtbo \
> +overlays/hifiberry-digi.dtbo \
> +overlays/i2c-rtc.dtbo \
> +overlays/iqaudio-dac.dtbo \
> +overlays/iqaudio-dacplus.dtbo \
> +overlays/lirc-rpi.dtbo \
> +overlays/pitft22.dtbo \
> +overlays/pitft28-resistive.dtbo \
> +overlays/pps-gpio.dtbo \
> +overlays/rpi-ft5406.dtbo \
> +overlays/w1-gpio.dtbo \
> +overlays/w1-gpio-pullup.dtbo \
> +overlays/pi3-miniuart-bt.dtbo \
> +"
> +
> +def cmpver_strings(ver1, ver2, truevalue, falsevalue):
> +from distutils.version import LooseVersion
> +ver1 = ''.join(ch for ch in ver1 if ch in '0123456789.')
> +ver2 = ''.join(ch for ch in ver2 if ch in '0123456789.')
> +if LooseVersion(ver1) >= LooseVersion(ver2):
> +return truevalue
> +else:
> +return falsevalue
> +
> +KERNEL_DEVICETREE ?=
"${@cmpver_strings("${PREFERRED_VERSION_linux-raspberrypi}", "4.4",
"${KERNEL_DEVICETREE_OVERLAYS_DTBO}", "${KERNEL_DEVICETREE_OVERL

Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Hi Andrei,

Sorry for the delay, but I've met some unexpected issue: when calling
IMAGE_CMD (which is the code that lives in sdcard_image-rpi.bbclass in
raspberrypi's case), TMPDIR is willfully deleted before the call...
But STAGING_KERNEL_BUILDDIR, which is used to find out what version of
kernel is used in case it's not passed, actually depends on it, so it's not
expanded.
So the kernel version test in linux-raspberrypi-base.bbclass fails when
get_dts is called from sdcard_image-rpi.bbclass without specifying the
kernel version - then just returns the default KERNEL_DEVICETREE value!

I believe it happens the same when testing with 3.18 - but I didn't build
3.18, and maybe it doesn't matter for building the image.

I'm trying to work around this issue without too much side-effects, and I
haven't found a nice solution so far - short from removing the line that
deletes TMPDIR...

Any suggestion is appreciated.

Herve

-Original Message-
From: Andrei Gherzan [mailto:and...@gherzan.ro] 
Sent: mercredi 15 juin 2016 02:12
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support
for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:33AM +0800, Herve Jourdain wrote:
> Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of
.dtb.
> Add support for both variants of overlays ("-overlay.dtb" and ".dtbo") 
> for the default KERNEL_DEVICETREE variable
>
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  conf/machine/include/rpi-base.inc | 36 
> +++-
>  1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/conf/machine/include/rpi-base.inc 
> b/conf/machine/include/rpi-base.inc
> index 56ca83e..2c9d8e0 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -16,7 +16,7 @@ XSERVER = " \
>  "
>
>  # Really supported starting from linux-raspberrypi 3.18.y only 
> -KERNEL_DEVICETREE ?= " \
> +KERNEL_DEVICETREE_OVERLAYS_DTB = " \
>  bcm2708-rpi-b.dtb \
>  bcm2708-rpi-b-plus.dtb \
>  bcm2709-rpi-2-b.dtb \
> @@ -38,6 +38,40 @@ KERNEL_DEVICETREE ?= " \
>  overlays/w1-gpio-pullup-overlay.dtb \
>  overlays/pi3-miniuart-bt-overlay.dtb \
>  "
> +KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
> +bcm2708-rpi-b.dtb \
> +bcm2708-rpi-b-plus.dtb \
> +bcm2709-rpi-2-b.dtb \
> +bcm2710-rpi-3-b.dtb \
> +\
> +overlays/hifiberry-amp.dtbo \
> +overlays/hifiberry-dac.dtbo \
> +overlays/hifiberry-dacplus.dtbo \
> +overlays/hifiberry-digi.dtbo \
> +overlays/i2c-rtc.dtbo \
> +overlays/iqaudio-dac.dtbo \
> +overlays/iqaudio-dacplus.dtbo \
> +overlays/lirc-rpi.dtbo \
> +overlays/pitft22.dtbo \
> +overlays/pitft28-resistive.dtbo \
> +overlays/pps-gpio.dtbo \
> +overlays/rpi-ft5406.dtbo \
> +overlays/w1-gpio.dtbo \
> +overlays/w1-gpio-pullup.dtbo \
> +overlays/pi3-miniuart-bt.dtbo \
> +"
> +
> +def cmpver_strings(ver1, ver2, truevalue, falsevalue):
> +from distutils.version import LooseVersion
> +ver1 = ''.join(ch for ch in ver1 if ch in '0123456789.')
> +ver2 = ''.join(ch for ch in ver2 if ch in '0123456789.')
> +if LooseVersion(ver1) >= LooseVersion(ver2):
> +return truevalue
> +else:
> +return falsevalue
> +
> +KERNEL_DEVICETREE ?=
"${@cmpver_strings("${PREFERRED_VERSION_linux-raspberrypi}", "4.4",
"${KERNEL_DEVICETREE_OVERLAYS_DTBO}", "${KERNEL_DEVICETREE_OVERLAYS_DTB}")}"
> +
>  KERNEL_IMAGETYPE ?= "Image"
>

Can we avoid this duplication by translating dtbo->dtb for kernels before
4.4? And I would suggest doing this in linux-raspberrypi-base.bbclass . What
do you think? We should reuse code there for version too.

>  MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen
alsa bluetooth wifi sdio"
> --
> 2.7.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

Re: [yocto] [meta-raspberrypi][PATCH v4 5/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Hi Andrei,

OK, I will push a v5, based on your comments.

Herve

-Original Message-
From: Andrei Gherzan [mailto:and...@gherzan.ro] 
Sent: mercredi 15 juin 2016 01:55
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v4 5/5]
linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:35AM +0800, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> index ba47b22..789fef1 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> @@ -4,5 +4,6 @@ LINUX_VERSION ?= "4.4.9"
>
>  SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y 
> \
> +   file://0001-fix-dtbo-rules.patch \
>  "
>  require linux-raspberrypi.inc
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Can we merge this patch in the 4th one? Only if you decide to push another
version based on other comments.

--
Andrei Gherzan

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

Re: [yocto] [meta-raspberrypi][PATCH v4 0/5] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

[Herve Jourdain]

Hi Andrei,

I believe it still has not been merged...
Shall I send a ping?

Herve

-Original Message-
From: Andrei Gherzan [mailto:and...@gherzan.ro] 
Sent: mercredi 15 juin 2016 01:54
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v4 0/5] Support for .dtbo
files for dtb overlays, required by kernels 4.4.6+

On Tue, May 31, 2016 at 04:46:30AM +0800, Herve Jourdain wrote:
> 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.
>

Is the poky patch merged? It doesn't seem it was.

--
Andrei Gherzan

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

Re: [yocto] gcc-6.1 and raspi

[Herve Jourdain]

Hi,

This one is a different issue, that was caused by a patch in oe 1 week ago.
I did send a patch to solve it last wednesday, I believe.
The root cause is KERNEL_OUTPUT has been removed from kernel.bbclass, but 
meta-raspberrypi uses it.
This is the link to the patch:
http://article.gmane.org/gmane.linux.embedded.yocto.general/30093/

Herve

> On 6 juin 2016, at 04:08, Trevor Woerner <twoer...@gmail.com> wrote:
> 
>> On Sun 2016-06-05 @ 04:55:47 PM, Herve Jourdain wrote:
>> It seems like you are building the 4.1.21 kernel.
>> Did you set PREFERRED_VERSION_linux-raspberrypi = "4.4.%" in your
>> distro.conf or local.conf?
> 
> I was trying to save myself the time required to rebuild with the 4.4 kernel.
> I knew from my experiments that the result was the same for both, but here it
> is anyway:
> 
>ERROR: linux-raspberrypi-1_4.4.9+gitAUTOINC+3b440738b5-r0 
> do_rpiboot_mkimage: Function failed: do_rpiboot_mkimage
>Log data follows:
>| DEBUG: Executing shell function do_rpiboot_mkimage
>| Usage: mkknlimg [--dtok] [--283x] <vmlinux|zImage|bzImage> 
>| WARNING: 
> /z/layerindex-master/raspi2/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/1_4.4.9+gitAUTOINC+3b440738b5-r0/temp/run.do_rpiboot_mkimage.18615:1
>  exit 1 from 
> '/z/layerindex-master/raspi2/tmp/sysroots/x86_64-linux/usr/bin/mkknlimg 
> --dtok ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}'
>| ERROR: Function failed: do_rpiboot_mkimage (log file is located at 
> /z/layerindex-master/raspi2/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/1_4.4.9+gitAUTOINC+3b440738b5-r0/temp/log.do_rpiboot_mkimage.18615)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ***SPAM*** Re: gcc-6.1 and raspi

[Herve Jourdain]

Hi,

It seems like you are building the 4.1.21 kernel.
Did you set PREFERRED_VERSION_linux-raspberrypi = "4.4.%" in your
distro.conf or local.conf?

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Trevor Woerner
Sent: dimanche 5 juin 2016 14:58
To: 'Yocto Project' <yocto@yoctoproject.org>
Subject: ***SPAM*** Re: [yocto] gcc-6.1 and raspi

On Sun 2016-06-05 @ 02:14:29 PM, Herve Jourdain wrote:
> I'm using kernel 4.4, and it does build properly with gcc 6.1.
> But the build does fail on other packages later on, so I ended up 
> reverting to 5.3 for now.

Both the official meta-raspberrypi and Khem Raj's meta-raspberrypi layers
have recipes for the 4.4% kernel. I tried them but I keep getting:

ERROR: linux-raspberrypi-1_4.1.21+gitAUTOINC+ff45bc0e89-r0
do_rpiboot_mkimage: Function failed: do_rpiboot_mkimage
Log data follows:
| DEBUG: Executing shell function do_rpiboot_mkimage
| Usage: mkknlimg [--dtok] [--283x] <vmlinux|zImage|bzImage>

| WARNING:
/z/layerindex-master/raspi2/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-r
aspberrypi/1_4.1.21+gitAUTOINC+ff45bc0e89-r0/temp/run.do_rpiboot_mkimage.125
4:1 exit 1 from
'/z/layerindex-master/raspi2/tmp/sysroots/x86_64-linux/usr/bin/mkknlimg
--dtok ${KERNEL_OUTPUT} ${KERNEL_OUTPUT}'
| ERROR: Function failed: do_rpiboot_mkimage (log file is located at
/z/layerindex-master/raspi2/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-r
aspberrypi/1_4.1.21+gitAUTOINC+ff45bc0e89-r0/temp/log.do_rpiboot_mkimage.125
4)

So I'm not sure what's going on there.
--
___
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] gcc-6.1 and raspi

[Herve Jourdain]

Hi,

I'm using kernel 4.4, and it does build properly with gcc 6.1.
But the build does fail on other packages later on, so I ended up reverting
to 5.3 for now.
I also think we should make 4.4 the default kernel version for
meta-raspberrypi, to follow the raspberrypi repository. The fixes on 4.1 are
far from what can be seen on 4.4 now (on the part that I'm involved with,
vc4 on 4.1 is not functional, while it is on 4.4 and later). And it will
only grow worse.

Herve

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Paul Barker
Sent: dimanche 5 juin 2016 13:22
To: Jonathan Liu 
Cc: Yocto Project 
Subject: Re: [yocto] gcc-6.1 and raspi

On Sun, 5 Jun 2016 20:44:42 +1000
Jonathan Liu  wrote:

> On 5 June 2016 at 09:00, Trevor Woerner  wrote:
> > Has anyone tried building a raspi image lately from master?
> >
> > ERROR: linux-raspberrypi-1_4.1.21+gitAUTOINC+ff45bc0e89-r0
> > do_compile: Function failed: do_compile
> >
> > | In file included
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/compiler.h:54:0,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/stddef.h:1,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/stddef.h:4,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/posix_types.h:4,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/uapi/linux/types.h:13,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/types.h:5,
> > |
> > from 
> > /z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-sour
> > ce/include/linux/mod_devicetable.h:11,
> > |
> > from
/z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-source/scrip
ts/mod/devicetable-offsets.c:2:
> > |
/z/layerindex-master/raspi2/tmp/work-shared/raspberrypi2/kernel-source/inclu
de/linux/compiler-gcc.h:121:30:
> > fatal error: linux/compiler-gcc6.h: No such file or directory
> 
> I can confirm this issue.
> 
> Regards,
> Jonathan

I can get a successful build with my kernel branch where I've merged the
latest 4.1.y upstream stable release into the Raspberry Pi 4.1.y branch
(https://gitlab.com/oryx/linux-oryx-rpi). I don't have the time to bisect
this right now but one commit stands out as an obvious candidate for being
the fix:

compiler-gcc: integrate the various compiler-gcc[345].h files
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/
?h=linux-4.1.y=f320793e52aee78f0fbb8bcaf10e6614d2e67bfc

I can also get a successful build using the recipe for the 4.4.y branch in
meta-raspberrypi. The Raspberry Pi repository has moved over to the 4.4.y
branch as the default, we should probably do the same in meta-raspberrypi.

Thanks,
Paul Barker
--
___
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 1/1] linux-raspberrypi.inc: KERNEL_OUTPUT has been removed in kernel.bbclass

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-raspberrypi.inc | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 4799c74..6133b02 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -66,7 +66,9 @@ do_rpiboot_mkimage() {
 if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
 if test -n "${KERNEL_DEVICETREE}"; then
 # Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok ${KERNEL_OUTPUT} 
${KERNEL_OUTPUT}
+for type in ${KERNEL_IMAGETYPES} ; do
+${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type ${KERNEL_OUTPUT_DIR}/$type
+done
 fi
 fi
 }
@@ -76,7 +78,9 @@ do_bundle_initramfs_append() {
 if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
 if test -n "${KERNEL_DEVICETREE}"; then
 # Add RPi bootloader trailer to kernel image to enable 
DeviceTree support
-${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT}.initramfs ${KERNEL_OUTPUT}.initramfs
+for type in ${KERNEL_IMAGETYPES} ; do
+${STAGING_BINDIR_NATIVE}/mkknlimg --dtok 
${KERNEL_OUTPUT_DIR}/$type.initramfs ${KERNEL_OUTPUT_DIR}/$type.initramfs
+done
 fi
 fi
 fi
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH 0/1] KERNEL_OUTPUT has been removed in kernel.bbclass

[Herve Jourdain]

The following patch has removed the KERNEL_OUTPUT variable:
http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/80172
But meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc does use it in
do_rpiboot_mkimage() and do_bundle_initramfs_append()!
Use the new KERNEL_OUTPUT_DIR variable, along with parsing the types from 
KERNEL_IMAGETYPES,
which is what the patch that removed KERNEL_OUTPUT is about

Herve Jourdain (1):
  linux-raspberrypi.inc: KERNEL_OUTPUT has been removed in
kernel.bbclass

 recipes-kernel/linux/linux-raspberrypi.inc | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

-- 
2.7.4

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

Re: [yocto] [PATCH v3] Support for .dtbo files for dtb overlays

[Herve Jourdain]

Oh, sorry for that...
Just sent to oe-core as well.
Thanks :)

Herve

-Original Message-
From: Andreas Müller [mailto:schnitzelt...@googlemail.com] 
Sent: mardi 31 mai 2016 09:21
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [yocto] [PATCH v3] Support for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 9:08 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote:
> v3: rebased
> Recent kernels tend to use .dtbo files for device tree overlays, instead of 
> .dtb before.
> .dtb are still used, but only for the "real" device trees (not the overlays).
>
> On some platforms (meta-raspberrypi for instance), recent firmware only loads 
> .dtbo files for overlays.
>
> This patch tries to address this issue, while not breaking support for .dtb 
> overlays.
> It allows the installation/deployment of both .dtb and .dtbo files, for 
> device trees and overlays.
>
> This is in line with the behavior of kernels 4.4.6+
>
> Herve Jourdain (1):
>   linux-dtb.inc: Support for .dtbo files for dtb overlays
>
>  meta/recipes-kernel/linux/linux-dtb.inc | 18 +++---
>  1 file changed, 11 insertions(+), 7 deletions(-)
>
If I am not mistaken this is a patch for oe-core layer and should be send to

openembedded-c...@lists.openembedded.org

Andreas

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

[yocto] [PATCH v3] linux-dtb.inc: Support for .dtbo files for dtb overlays

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 meta/recipes-kernel/linux/linux-dtb.inc | 18 +++---
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dtb.inc 
b/meta/recipes-kernel/linux/linux-dtb.inc
index 74f5ef8..8528d64 100644
--- a/meta/recipes-kernel/linux/linux-dtb.inc
+++ b/meta/recipes-kernel/linux/linux-dtb.inc
@@ -33,12 +33,13 @@ do_compile_append() {
 do_install_append() {
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_EXT=${DTB##*.}
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
-   install -m 0644 ${DTB_PATH} 
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
+   install -m 0644 ${DTB_PATH} 
${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT}
done
done
 }
@@ -46,7 +47,8 @@ do_install_append() {
 do_deploy_append() {
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_EXT=${DTB##*.}
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
base_name=${type}"-"${KERNEL_IMAGE_BASE_NAME}
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
@@ -54,8 +56,8 @@ do_deploy_append() {
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
DTB_PATH=`get_real_dtb_path_in_kernel "${DTB}"`
install -d ${DEPLOYDIR}
-   install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
-   ln -sf ${DTB_NAME}.dtb 
${DEPLOYDIR}/${DTB_SYMLINK_NAME}.dtb
+   install -m 0644 ${DTB_PATH} 
${DEPLOYDIR}/${DTB_NAME}.${DTB_EXT}
+   ln -sf ${DTB_NAME}.${DTB_EXT} 
${DEPLOYDIR}/${DTB_SYMLINK_NAME}.${DTB_EXT}
done
done
 }
@@ -65,9 +67,10 @@ pkg_postinst_kernel-devicetree () {
for DTB in ${KERNEL_DEVICETREE}; do
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
+   DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print 
$1}'`
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   update-alternatives --install 
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.dtb ${DTB_BASE_NAME}.dtb 
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
+   update-alternatives --install 
/${KERNEL_IMAGEDEST}/${DTB_BASE_NAME}.${DTB_EXT} ${DTB_BASE_NAME}.${DTB_EXT} 
/boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} ${KERNEL_PRIORITY} || true
done
done
 }
@@ -77,9 +80,10 @@ pkg_postrm_kernel-devicetree () {
for DTB in ${KERNEL_DEVICETREE}; do
for type in ${KERNEL_IMAGETYPE_FOR_MAKE}; do
symlink_name=${type}"-"${KERNEL_IMAGE_SYMLINK_NAME}
+   DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} | awk -F "." '{print 
$1}'`
DTB_SYMLINK_NAME=`echo ${symlink_name} | sed 
"s/${MACHINE}/${DTB_BASE_NAME}/g"`
-   update-alternatives --remove ${DTB_BASE_NAME}.dtb 
/boot/devicetree-${DTB_SYMLINK_NAME}.dtb ${KERNEL_PRIORITY} || true
+   update-alternatives --remove 
${DTB_BASE_NAME}.${DTB_EXT} /boot/devicetree-${DTB_SYMLINK_NAME}.${DTB_EXT} 
${KERNEL_PRIORITY} || true
done
done
 }
-- 
2.7.4

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

[yocto] [PATCH v3] Support for .dtbo files for dtb overlays

[Herve Jourdain]

v3: rebased
Recent kernels tend to use .dtbo files for device tree overlays, instead of 
.dtb before.
.dtb are still used, but only for the "real" device trees (not the overlays).

On some platforms (meta-raspberrypi for instance), recent firmware only loads 
.dtbo files for overlays.

This patch tries to address this issue, while not breaking support for .dtb 
overlays.
It allows the installation/deployment of both .dtb and .dtbo files, for device 
trees and overlays.

This is in line with the behavior of kernels 4.4.6+

Herve Jourdain (1):
  linux-dtb.inc: Support for .dtbo files for dtb overlays

 meta/recipes-kernel/linux/linux-dtb.inc | 18 +++---
 1 file changed, 11 insertions(+), 7 deletions(-)

-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 14/14] linux-raspberrypi-4.4: add patch to enable proper operation of renderD128 device

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0002-vc4-ioctl-rendering-allow.patch   | 23 ++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  1 +
 2 files changed, 24 insertions(+)
 create 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
new file mode 100644
index 000..823ffd8
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0002-vc4-ioctl-rendering-allow.patch
@@ -0,0 +1,23 @@
+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 02016fe..ba0973d 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -5,5 +5,6 @@ LINUX_VERSION ?= "4.4.10"
 SRCREV = "d7646fd3757515dfda0fd4ecd33212d175786ac4"
 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.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 13/14] linux-raspberrypi_4.4.bb: bump the kernel revision to 4.4.10 to support vc4graphics (including renderD128 device)

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 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 789fef1..02016fe 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.9"
+LINUX_VERSION ?= "4.4.10"
 
-SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
+SRCREV = "d7646fd3757515dfda0fd4ecd33212d175786ac4"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-fix-dtbo-rules.patch \
 "
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 12/14] firmware.inc: bump version to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 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 bf11e4c..b467fc6 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,5 +1,5 @@
-RPIFW_SRCREV ?= "3816e1ce1e6ebc6d2bf0596dbd52849e16aa7e94"
-RPIFW_DATE ?= "20160512"
+RPIFW_SRCREV ?= "c17fa41b8e8321d891230f97837fee98feebc1ac"
+RPIFW_DATE ?= "20160513"
 RPIFW_SRC_URI ?= 
"git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
 RPIFW_S ?= "${WORKDIR}/git"
 
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 11/14] linux-rpi.inc: add the configuration options required to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-rpi.inc | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/recipes-kernel/linux/linux-rpi.inc 
b/recipes-kernel/linux/linux-rpi.inc
index 1755685..c120dbd 100644
--- a/recipes-kernel/linux/linux-rpi.inc
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -111,6 +111,16 @@ do_configure_prepend() {
 # Activate CONFIG_LEGACY_PTYS
 kernel_configure_variable LEGACY_PTYS y
 
+# Activate the configuration options for VC4
+VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
"0", d)}"
+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_VC4 y
+kernel_configure_variable FB_BCM2708 n
+fi
+
 # Keep this the last line
 # Remove all modified configs and add the rest to .config
 sed -e "${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config'
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 10/14] mesa_%.bbappend: new file to add the correct configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/mesa/mesa_%.bbappend | 4 
 1 file changed, 4 insertions(+)
 create mode 100644 recipes-graphics/mesa/mesa_%.bbappend

diff --git a/recipes-graphics/mesa/mesa_%.bbappend 
b/recipes-graphics/mesa/mesa_%.bbappend
new file mode 100644
index 000..b182388
--- /dev/null
+++ b/recipes-graphics/mesa/mesa_%.bbappend
@@ -0,0 +1,4 @@
+PACKAGECONFIG_append_rpi = " gallium"
+GALLIUMDRIVERS_rpi = "vc4"
+DRIDRIVERS_rpi = ""
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 09/14] weston/weston_%.bbappend: modify configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/weston/weston_%.bbappend | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/recipes-graphics/weston/weston_%.bbappend 
b/recipes-graphics/weston/weston_%.bbappend
index 3ec311d..70f4360 100644
--- a/recipes-graphics/weston/weston_%.bbappend
+++ b/recipes-graphics/weston/weston_%.bbappend
@@ -1,7 +1,8 @@
-EXTRA_OECONF += "--enable-rpi-compositor \
- --disable-resize-optimization \
- --disable-setuid-install \
- --disable-xwayland-test \
- --disable-simple-egl-clients \
- WESTON_NATIVE_BACKEND=rpi-backend.so \
+PACKAGECONFIG_rpi_remove = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', ' fbdev', '', d)}"
+EXTRA_OECONF += "--disable-xwayland-test \
+ --disable-simple-egl-clients \
 "
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--enable-rpi-compositor', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-resize-optimization', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-setuid-install', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 07/14] rpi-config_git.bb: add v4c overlay to config.txt to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-bsp/bootfiles/rpi-config_git.bb | 10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 4bc8eb7..f610718 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -13,12 +13,14 @@ SRC_URI = 
"git://github.com/Evilpaul/RPi-config.git;protocol=git;branch=master \
 
 S = "${WORKDIR}/git"
 
-PR = "r4"
+PR = "r5"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
 PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 PITFT28r="${@bb.utils.contains("MACHINE_FEATURES", "pitft28r", "1", "0", d)}"
 
+VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", "0", 
d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -102,6 +104,12 @@ do_deploy() {
 echo "# Enable UART" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "enable_uart=1" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# VC4 Graphics support
+if [ "${VC4GRAPHICS}" = "1" ]; then
+echo "# Enable VC4 Graphics" >> 
${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=vc4-kms-v3d,${VC4_CMA_SIZE}" >> 
${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 08/14] wayland/weston_%.bbappend: modify configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/wayland/weston_%.bbappend | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/recipes-graphics/wayland/weston_%.bbappend 
b/recipes-graphics/wayland/weston_%.bbappend
index c3a7421..57b8079 100644
--- a/recipes-graphics/wayland/weston_%.bbappend
+++ b/recipes-graphics/wayland/weston_%.bbappend
@@ -1,4 +1,2 @@
-EXTRA_OECONF_append_rpi = "\
---enable-rpi-compositor \
-WESTON_NATIVE_BACKEND=rpi-backend.so \
-   "
+EXTRA_OECONF_append_rpi = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', '', ' --enable-rpi-compositor 
WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 06/14] raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi3.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index cb6056e..438c6e6 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -9,3 +9,5 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
 include conf/machine/raspberrypi2.conf
 
 SERIAL_CONSOLE = "115200 ttyS0"
+VC4_CMA_SIZE ?= "cma-256"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 05/14] raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi2.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi2.conf b/conf/machine/raspberrypi2.conf
index b6346e6..3a82d66 100644
--- a/conf/machine/raspberrypi2.conf
+++ b/conf/machine/raspberrypi2.conf
@@ -8,3 +8,5 @@ require conf/machine/include/tune-cortexa7.inc
 include conf/machine/include/rpi-base.inc
 
 SERIAL_CONSOLE = "115200 ttyAMA0"
+VC4_CMA_SIZE ?= "cma-256"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 03/14] raspberrypi.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi.conf b/conf/machine/raspberrypi.conf
index 0f95f1a..b369c67 100644
--- a/conf/machine/raspberrypi.conf
+++ b/conf/machine/raspberrypi.conf
@@ -8,3 +8,5 @@ require conf/machine/include/tune-arm1176jzf-s.inc
 include conf/machine/include/rpi-base.inc
 
 SERIAL_CONSOLE = "115200 ttyAMA0"
+VC4_CMA_SIZE_raspberrypi ?= "cma-64"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 04/14] raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/raspberrypi0.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi0.conf b/conf/machine/raspberrypi0.conf
index ccf9ae7..0df9121 100644
--- a/conf/machine/raspberrypi0.conf
+++ b/conf/machine/raspberrypi0.conf
@@ -6,3 +6,5 @@ MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
 include conf/machine/raspberrypi.conf
 
 SERIAL_CONSOLE = "115200 ttyAMA0"
+VC4_CMA_SIZE ?= "cma-128"
+
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 02/14] rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 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 2c9d8e0..23f8619 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -59,6 +59,7 @@ KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
 overlays/w1-gpio.dtbo \
 overlays/w1-gpio-pullup.dtbo \
 overlays/pi3-miniuart-bt.dtbo \
+overlays/vc4-kms-v3d.dtbo \
 "
 
 def cmpver_strings(ver1, ver2, truevalue, falsevalue):
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 01/14] rpi-default-providers.inc: change default providers to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/include/rpi-default-providers.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/conf/machine/include/rpi-default-providers.inc 
b/conf/machine/include/rpi-default-providers.inc
index cabbd43..0bc8838 100644
--- a/conf/machine/include/rpi-default-providers.inc
+++ b/conf/machine/include/rpi-default-providers.inc
@@ -3,8 +3,8 @@
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
 PREFERRED_PROVIDER_u-boot ?= "u-boot-rpi"
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
-PREFERRED_PROVIDER_virtual/egl ?= "userland"
-PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
-PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
+PREFERRED_PROVIDER_virtual/egl ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "userland", d)}"
+PREFERRED_PROVIDER_virtual/libgles2 ?= 
"${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "userland", 
d)}"
+PREFERRED_PROVIDER_virtual/libgl ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "mesa-gl", d)}"
+PREFERRED_PROVIDER_virtual/mesa ?= "${@bb.utils.contains("MACHINE_FEATURES", 
"vc4graphics", "mesa", "mesa-gl", d)}"
 PREFERRED_PROVIDER_jpeg ?= "jpeg"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v3 00/14] Support for VC4 graphics driver

[Herve Jourdain]

This v3 series addresses the following issues with the v2 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 (14):
  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
  firmware.inc: bump version to support vc4graphics
  linux-raspberrypi_4.4.bb: bump the kernel revision to 4.4.10 to
support vc4graphics (including renderD128 device)
  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-bsp/common/firmware.inc|  4 ++--
 recipes-graphics/mesa/mesa_%.bbappend  |  4 
 recipes-graphics/wayland/weston_%.bbappend |  6 ++
 recipes-graphics/weston/weston_%.bbappend  | 13 ++--
 .../0002-vc4-ioctl-rendering-allow.patch   | 23 ++
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  5 +++--
 recipes-kernel/linux/linux-rpi.inc | 10 ++
 14 files changed, 73 insertions(+), 19 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

[yocto] [meta-raspberrypi][PATCH v4 5/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index ba47b22..789fef1 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -4,5 +4,6 @@ LINUX_VERSION ?= "4.4.9"
 
 SRCREV = "3b440738b5c1adc3ec3ee72ceca799d1b8d264df"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
+   file://0001-fix-dtbo-rules.patch \
 "
 require linux-raspberrypi.inc
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Patch the kernel, which has faulty rules to generate .dtbo the way yocto does

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 .../0001-fix-dtbo-rules.patch  | 27 ++
 1 file changed, 27 insertions(+)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch 
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
new file mode 100644
index 000..ef04a72
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
@@ -0,0 +1,27 @@
+diff --git a/arch/arm/Makefile b/arch/arm/Makefile
+index a2e7cf7..673c1cb 100644
+--- a/arch/arm/Makefile
 b/arch/arm/Makefile
+@@ -333,6 +333,8 @@ $(INSTALL_TARGETS):
+ 
+ %.dtb: | scripts
+   $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
++%.dtbo: | scripts
++  $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
+ 
+ PHONY += dtbs dtbs_install
+ 
+diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
+index 3079c4f..6cc3766 100644
+--- a/scripts/Makefile.lib
 b/scripts/Makefile.lib
+@@ -293,7 +293,8 @@ $(obj)/%.dtb: $(src)/%.dts FORCE
+   $(call if_changed_dep,dtc)
+ 
+ quiet_cmd_dtco = DTCO$@
+-cmd_dtco = $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
++cmd_dtco = mkdir -p $(dir ${dtc-tmp}) ; \
++  $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
+   $(objtree)/scripts/dtc/dtc -@ -H epapr -O dtb -o $@ -b 0 \
+   -i $(dir $<) $(DTC_FLAGS) \
+   -d $(depfile).dtc.tmp $(dtc-tmp) ; \
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both variants of overlays ("-overlay.dtb" and ".dtbo") for the 
default KERNEL_DEVICETREE variable

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 conf/machine/include/rpi-base.inc | 36 +++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index 56ca83e..2c9d8e0 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -16,7 +16,7 @@ XSERVER = " \
 "
 
 # Really supported starting from linux-raspberrypi 3.18.y only
-KERNEL_DEVICETREE ?= " \
+KERNEL_DEVICETREE_OVERLAYS_DTB = " \
 bcm2708-rpi-b.dtb \
 bcm2708-rpi-b-plus.dtb \
 bcm2709-rpi-2-b.dtb \
@@ -38,6 +38,40 @@ KERNEL_DEVICETREE ?= " \
 overlays/w1-gpio-pullup-overlay.dtb \
 overlays/pi3-miniuart-bt-overlay.dtb \
 "
+KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
+bcm2708-rpi-b.dtb \
+bcm2708-rpi-b-plus.dtb \
+bcm2709-rpi-2-b.dtb \
+bcm2710-rpi-3-b.dtb \
+\
+overlays/hifiberry-amp.dtbo \
+overlays/hifiberry-dac.dtbo \
+overlays/hifiberry-dacplus.dtbo \
+overlays/hifiberry-digi.dtbo \
+overlays/i2c-rtc.dtbo \
+overlays/iqaudio-dac.dtbo \
+overlays/iqaudio-dacplus.dtbo \
+overlays/lirc-rpi.dtbo \
+overlays/pitft22.dtbo \
+overlays/pitft28-resistive.dtbo \
+overlays/pps-gpio.dtbo \
+overlays/rpi-ft5406.dtbo \
+overlays/w1-gpio.dtbo \
+overlays/w1-gpio-pullup.dtbo \
+overlays/pi3-miniuart-bt.dtbo \
+"
+
+def cmpver_strings(ver1, ver2, truevalue, falsevalue):
+from distutils.version import LooseVersion
+ver1 = ''.join(ch for ch in ver1 if ch in '0123456789.')
+ver2 = ''.join(ch for ch in ver2 if ch in '0123456789.')
+if LooseVersion(ver1) >= LooseVersion(ver2):
+return truevalue
+else:
+return falsevalue
+
+KERNEL_DEVICETREE ?= 
"${@cmpver_strings("${PREFERRED_VERSION_linux-raspberrypi}", "4.4", 
"${KERNEL_DEVICETREE_OVERLAYS_DTBO}", "${KERNEL_DEVICETREE_OVERLAYS_DTB}")}"
+
 KERNEL_IMAGETYPE ?= "Image"
 
 MACHINE_FEATURES += "apm usbhost keyboard vfat ext2 screen touchscreen alsa 
bluetooth wifi sdio"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v4 2/5] sdcard_image-rpi.bbclass: support for .dtbo files for dtb overlays

[Herve Jourdain]

Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Add support for both extensions for overlays (".dtb" and ".dtbo")

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 classes/sdcard_image-rpi.bbclass | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/classes/sdcard_image-rpi.bbclass b/classes/sdcard_image-rpi.bbclass
index 4dfd7a3..b3a8bc0 100644
--- a/classes/sdcard_image-rpi.bbclass
+++ b/classes/sdcard_image-rpi.bbclass
@@ -110,7 +110,7 @@ IMAGE_CMD_rpi-sdimg () {
;;
*)
if test -n "${DTS}"; then
-   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' string and will be put in a dedicated folder
+   # Device Tree Overlays are assumed to be suffixed by 
'-overlay.dtb' (4.1.x) or by '.dtbo' (4.4.9+) string and will be put in a 
dedicated folder
DT_OVERLAYS="${@split_overlays(d, 0)}"
DT_ROOT="${@split_overlays(d, 1)}"
 
@@ -124,9 +124,10 @@ IMAGE_CMD_rpi-sdimg () {
# Copy device tree overlays to dedicated folder
mmd -i ${WORKDIR}/boot.img overlays
for DTB in ${DT_OVERLAYS}; do
-   DTB_BASE_NAME=`basename ${DTB} .dtb`
+   DTB_EXT=${DTB##*.}
+   DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
 
-   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.dtb 
::overlays/${DTB_BASE_NAME}.dtb
+   mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${DTB_BASE_NAME}.${DTB_EXT} 
::overlays/${DTB_BASE_NAME}.${DTB_EXT}
done
fi
mcopy -i ${WORKDIR}/boot.img -s 
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin 
::${SDIMG_KERNELIMAGE}
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics driver

[Herve Jourdain]

Hi Piotr,

I know that the omxplayer would not build at this time, because VC4 and
userland will conflict, and currently omxplayer depends on userland.
I will check if it can be supported with VC4 driver enabled, but for the
moment it's true I disabled it in my build.

Regarding your patches:
1. Are you using linux kernel 4.4? You should set
PREFERRED_VERSION_linux-raspberrypi = "4.4.%" somewhere, either in your
distro configuration file, or your local.conf.
If you do so, it should get kernel 4.4.10, which requires .dtbo files
for overlay. As mentioned in the patch, support for VC4 in 4.1 is not
stable, and therefore not supported.
2. I've seen only one TODO, did you make only one modification?
3. There are other patches that are needed to be applied, before this patch
series is applied: 2 for .dtbo support (1 in meta-raspberrypi, 1 in meta), 1
for mesa (to allow packaging with empty DRI).

I'll take a look at the omxplayer issue as soon as I can, in the meanwhile I
recommend to not use it...

Herve

-Original Message-
From: piotr.lewicki [mailto:piotr.lewi...@elfin.de] 
Sent: mardi 24 mai 2016 11:59
To: Herve Jourdain <herve.jourd...@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4
graphics driver

I have tried these patches, but there were some hunks and errors during
applying to current master revision
(69840c0bbe03c2e61601e2377c8e2adc264e0478).
Building 'rpi-hwup-image' passed, but while building 'rpi-test-image' 
(omxplayer recipe) I have noticed some errors due to missing files:
- IL/OMX_Core.h
- VG/openvg.h
- bcm_host.h

I'm attaching omxplayer_build_errors.txt with build log and my patch with
changes created by Herve (adapted to current master revision) -
Support_for_VC4_graphics_driver.patch (Herve- if you decide to use that and
resend v3 of patches - please remove my TODO from
"conf/machine/include/rpi-base.inc"

Could you take a look at that and help me resolve those issues?


I currently have a problem that I'm forced to use Raspbian because playing
FHD/1080p videos with omxplayer from Yocto runs choppy (I'm not sure if
that's the right word, but playback is not smooth) while with Raspbian it
works perfect.
Do you think that enabling VC4 graphics driver can solve my issue?
Did any of you experienced similar problems? Do you have some other solution
or do you know what's the cause of this?


Thanks,
Piotr Lewicki


On 20.05.2016 13:51, Herve Jourdain wrote:
> This v2 series addresses the following issues with the first 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 (13):
>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
>raspber

[yocto] [meta-raspberrypi][PATCH v2 13/13] linux-rpi.inc: add the configuration options required to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-kernel/linux/linux-rpi.inc | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/recipes-kernel/linux/linux-rpi.inc 
b/recipes-kernel/linux/linux-rpi.inc
index fae78b7..9b91bd5 100644
--- a/recipes-kernel/linux/linux-rpi.inc
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -107,6 +107,16 @@ do_configure_prepend() {
 # Activate CONFIG_LEGACY_PTYS
 kernel_configure_variable LEGACY_PTYS y
 
+# Activate the configuration options for VC4
+VC4GRAPHICS="${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "1", 
"0", d)}"
+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_VC4 y
+kernel_configure_variable FB_BCM2708 n
+fi
+
 # Keep this the last line
 # Remove all modified configs and add the rest to .config
 sed -e "${CONF_SED_SCRIPT}" < '${WORKDIR}/defconfig' >> '${B}/.config'
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 12/13] linux-raspberrypi_4.4.bb: bump the kernel revision to 4.4.10 to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 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 831ac5a..79a6e65 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.8"
+LINUX_VERSION ?= "4.4.10"
 
-SRCREV = "fe7ad6aa5c6940817fe971d80a7b2a1d6052190a"
+SRCREV = "c317a023583b17a4350f066924d5fff47a81f91e"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-fix-dtbo-rules.patch \
 "
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 10/13] weston/weston_%.bbappend: modify configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/weston/weston_%.bbappend | 13 +++--
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/recipes-graphics/weston/weston_%.bbappend 
b/recipes-graphics/weston/weston_%.bbappend
index 3ec311d..70f4360 100644
--- a/recipes-graphics/weston/weston_%.bbappend
+++ b/recipes-graphics/weston/weston_%.bbappend
@@ -1,7 +1,8 @@
-EXTRA_OECONF += "--enable-rpi-compositor \
- --disable-resize-optimization \
- --disable-setuid-install \
- --disable-xwayland-test \
- --disable-simple-egl-clients \
- WESTON_NATIVE_BACKEND=rpi-backend.so \
+PACKAGECONFIG_rpi_remove = "${@bb.utils.contains('MACHINE_FEATURES', 
'vc4graphics', ' fbdev', '', d)}"
+EXTRA_OECONF += "--disable-xwayland-test \
+ --disable-simple-egl-clients \
 "
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--enable-rpi-compositor', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-resize-optimization', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'--disable-setuid-install', d)}"
+EXTRA_OECONF += "${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', '', 
'WESTON_NATIVE_BACKEND=rpi-backend.so', d)}"
-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH v2 11/13] mesa_%.bbappend: new file to add the correct configuration options to support vc4graphics

[Herve Jourdain]

Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr>
---
 recipes-graphics/mesa/mesa_%.bbappend | 4 
 1 file changed, 4 insertions(+)
 create mode 100644 recipes-graphics/mesa/mesa_%.bbappend

diff --git a/recipes-graphics/mesa/mesa_%.bbappend 
b/recipes-graphics/mesa/mesa_%.bbappend
new file mode 100644
index 000..b182388
--- /dev/null
+++ b/recipes-graphics/mesa/mesa_%.bbappend
@@ -0,0 +1,4 @@
+PACKAGECONFIG_append_rpi = " gallium"
+GALLIUMDRIVERS_rpi = "vc4"
+DRIDRIVERS_rpi = ""
+
-- 
2.7.4

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