[yocto] ***SPAM*** Re: [meta-raspberrypi] Building rpi-test-image for Pi3 64 bit

[Luca Carlon]

Hello,
thank you very much for your answer. I read about the fw limitations but I
couldn't find what exactly is working and what is not. This explains the
error that I was getting.
Thank you for your help!

Luca

Il 04 Mag 2017 05:46, "Herve Jourdain" <herve.jourdain at neuf.fr> ha scritto:

> 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-bounces at yoctoproject.org [mailto:yocto-bounces@
> yoctoproject.org] *On Behalf Of *Luca Carlon
> *Sent:* mercredi 3 mai 2017 18:19
> *To:* Khem Raj <raj.khem at gmail.com>
> *Cc:* yocto at 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 <raj.khem at gmail.com> wrote:
>
>
>
> On Wed, May 3, 2017 at 8:28 AM Luca Carlon <carlon.luca at gmail.com> 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 <gizero at gmail.com>
> wrote:
>
> On Sat, Apr 29, 2017 at 2:39 AM, Luca Carlon <carlon.luca at gmail.com>
> 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170504/34857741/attachment.html>