All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@buildroot.org
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/rpi-userland: add support for aarch64 build
Date: Tue, 8 Mar 2022 21:59:47 +0100	[thread overview]
Message-ID: <20220308215947.665d0fac@gmx.net> (raw)
In-Reply-To: <CA+h8R2rvGjfPkc=AdUXJobisbhHCL6FLJy7D1SGq94mk0HFJ_g@mail.gmail.com>

Hello Christian,

On Mon, 7 Mar 2022 15:03:25 -0800, Christian Stewart via buildroot <buildroot@buildroot.org> wrote:

> Hi Peter,
>
> You're probably right about that:
>
> On Mon, Mar 7, 2022 at 2:54 PM Peter Seiderer <ps.report@gmx.net> wrote:
> > On Mon,  7 Mar 2022 14:42:26 -0800, Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> >
> > > Tested on Pi4 Model B (aarch64).
> > >
> > > Note: rpi-userland and upstream rpi os now support arm64.
> >
> > All issues/questions solved since discussion [1], [2] about
> > missing libraries/features?
> >
> > As far as I know rpi os graphic support is based on mesa3d v3d/vc4
> > instead of rpi-userland libraries?
>
> I use this package on arm64 for vcgencmd (videocore) and other commands,
>
> however I have not verified that graphics work correctly, and you're
> most likely correct,
>
> the arm64 stack probably is using mesa3d vc4. I boot the pi4 64 bit with:
>
> arm_64bit=1
> dtoverlay=vc4-fkms-v3d
>
> So this is using vc4, as you've mentioned here.
>
> I suppose to fix this patch, it needs something like:
>
> ifeq ($(BR2_aarch64),y)
> RPI_USERLAND_CONF_OPTS += -DARM64=ON
> else
> RPI_USERLAND_PROVIDES = libegl libgles libopenmax libopenvg
> endif
>
> Is this correct?

Did not (yet/lately) check if really all the above libs are disabled
with the ARM64 feature, but at least a starting point for the aarch64
use case....

But needs a corresponding aarch64 handling in package/rpi-userland/Config.in
too (select BR2_PACKAGE_HAS_LIBEGL, select BR2_PACKAGE_HAS_LIBGLES
select BR2_PACKAGE_HAS_LIBOPENVG, select BR2_PACKAGE_HAS_LIBOPENMAX, ...)
and maybe the help text needs to be adjusted...

>
> Thanks & best,
> Christian Stewart
>
> > Regards,
> > Peter
> >
> > [1] http://lists.busybox.net/pipermail/buildroot/2020-June/587538.html
> > [2] http://lists.busybox.net/pipermail/buildroot/2021-October/626080.html
>
> PS: I've noticed that my e-mail / name is wrong again:
>
> Christian Stewart via buildroot <buildroot@buildroot.org>
>
> is this on your end or mine?

Maybe both, I got your original email with

	From: Christian Stewart via buildroot <buildroot@buildroot.org>
	CC: Christian Stewart <christian@paral.in>, ...
	Reply-To: Christian Stewart <christian@paral.in>

My email client (Claws Mail) seems to ignore the Reply-To field leading to

	To: Christian Stewart via buildroot <buildroot@buildroot.org>
	CC: Christian Stewart <christian@paral.in>
	CC: ...

But the copy from the mailing list I receive is missing the

	CC: Christian Stewart <christian@paral.in>

but keeps the other CC recipients...

Regards,
Peter

> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-03-08 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 22:42 [Buildroot] [PATCH v2 1/1] package/rpi-userland: add support for aarch64 build Christian Stewart via buildroot
2022-03-07 22:54 ` Peter Seiderer
2022-03-07 23:03   ` Christian Stewart via buildroot
2022-03-07 23:52     ` Charles Steinkuehler
2022-03-08 20:59     ` Peter Seiderer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220308215947.665d0fac@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.