From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libdrm: disable drivers for sparcv8
Date: Mon, 18 Jan 2016 22:43:53 +0100 [thread overview]
Message-ID: <20160118224353.2e02cf1b@free-electrons.com> (raw)
In-Reply-To: <20160118210041.GA19430@waldemar-brodkorb.de>
Waldemar,
On Mon, 18 Jan 2016 22:00:42 +0100, Waldemar Brodkorb wrote:
> The drivers use atomic ops as CAS, which fails
> to compile for sparcv8, but works fine for leon3.
>
> Fixes following autobuild error:
> http://autobuild.buildroot.net/results/fa0ac44d3c7953b2e2afa03cd7570d8a5d49fcc4/
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/libdrm/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/libdrm/Config.in b/package/libdrm/Config.in
> index 445a85b..bacbeac 100644
> --- a/package/libdrm/Config.in
> +++ b/package/libdrm/Config.in
> @@ -15,6 +15,7 @@ config BR2_PACKAGE_LIBDRM_INSTALL_TESTS
> This option allows to install the libdrm test programs.
>
> menu "DRM Drivers"
> +depends on !BR2_sparc_v8 # drivers need atomic ops
What about the packages that select some libdrm drivers? I'm thinking
for example of:
config BR2_PACKAGE_MESA3D_DRI_DRIVER_NOUVEAU
bool "DRI nouveau driver"
select BR2_PACKAGE_MESA3D_DRI_DRIVER
select BR2_PACKAGE_LIBDRM_NOUVEAU
help
Support for Nvidia-based GPUs.
config BR2_PACKAGE_MESA3D_DRI_DRIVER_RADEON
bool "DRI radeon driver"
select BR2_PACKAGE_MESA3D_DRI_DRIVER
select BR2_PACKAGE_LIBDRM_RADEON
help
Legacy Radeon driver for R100 series GPUs.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-18 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 21:00 [Buildroot] [PATCH] libdrm: disable drivers for sparcv8 Waldemar Brodkorb
2016-01-18 21:43 ` Thomas Petazzoni [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=20160118224353.2e02cf1b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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