Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Ruschival <thomas@ruschival.de>
To: buildroot@buildroot.org
To: Arnout Vandecappelle <arnout@mind.be>
Subject: [Buildroot] RFC: Patch "Gallium VC4 driver depends on NEON"?
Date: Thu, 17 Mar 2022 20:23:01 +0100	[thread overview]
Message-ID: <8735jgs7sa.fsf@ruschival.de> (raw)

Hi Arnout, 

the Patch "package/mesa3d: Gallium VC4 driver depends on NEON"
commit a5cdb54ed78b136c83dd44aebfa27f715cda5ea3 prevents using VC4 and
hence OpenGL on Raspberry Pi Zero.

From the referenced autobuild logs I gathered that the build that failed
used the bootlin-armv5-uclibc toolchain.

Since I wanted to use OpenGL for Qt on a Raspberry Pi Zero I reverted
the commit. The package compiled without errors and the system works as
expected.  Since my build is using a buildroot toolchain
arm-buildroot-linux-gnueabihf (gcc 10, glibc) I guess the assembler
errors are due to the toolchain.

I am not sure how to proceed in this case.

Should I investigate further on a more elaborate dependency logic to
allow for usage of VC4 on Raspberry Pi Zero that doesn't break
autobuild with bootlin-armv5-uclibc?

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

             reply	other threads:[~2022-03-17 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 19:23 Thomas Ruschival [this message]
2022-03-17 20:53 ` [Buildroot] RFC: Patch "Gallium VC4 driver depends on NEON"? Arnout Vandecappelle

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=8735jgs7sa.fsf@ruschival.de \
    --to=thomas@ruschival.de \
    --cc=buildroot@buildroot.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox