From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2]package/x11r7/xdriver_xf86-video-nouveau:new package
Date: Sat, 19 Dec 2015 17:57:54 +0100 [thread overview]
Message-ID: <itegkcxlsq.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20151219155647.0a4ca4b8@free-electrons.com
Hi Thomas,
Am Sat, 19 Dec 2015 15:56:47 +0100 schrieb Thomas Petazzoni:
> Dear Bernd Kuhls,
> [...]
> I've still applied your package because this issue needs to be fixed
> separately, and address for all three Config.in options.
thanks!
> Essentially, this happens because I'm building on ARM, and the
> BR2_PACKAGE_LIBDRM_NOUVEAU option is only available on i386 and x86_64.
> However, I wonder why BR2_PACKAGE_LIBDRM_NOUVEAU is not available on
> ARM, since I'm pretty sure that the Nouveau driver is used on ARM on
> some Tegra platforms.
Looking at libdrm/Config.in the restriction on Intel hardware was
added in 2013, it seems no one cared until now ;)
$ git blame package/libdrm/Config.in | grep -A2 NOUVEAU
b35acfff (Spenser Gilliland 2013-09-05 23:25:15 -0500 37) config BR2_PACKAGE_LIBDRM_NOUVEAU
b35acfff (Spenser Gilliland 2013-09-05 23:25:15 -0500 38) bool "nouveau"
b35acfff (Spenser Gilliland 2013-09-05 23:25:15 -0500 39) depends on BR2_i386 || BR2_x86_64
> Right now, this causes a build failure:
Should be fixed by
http://patchwork.ozlabs.org/patch/559217/
http://patchwork.ozlabs.org/patch/559218/
Regards, Bernd
next prev parent reply other threads:[~2015-12-19 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 14:22 [Buildroot] [PATCH v4 1/2] package/x11r7/xserver_xorg-server: bump version to 1.18.0 Bernd Kuhls
2015-12-19 14:22 ` [Buildroot] [PATCH v4 2/2] package/x11r7/xdriver_xf86-video-nouveau: new package Bernd Kuhls
2015-12-19 14:56 ` Thomas Petazzoni
2015-12-19 16:57 ` Bernd Kuhls [this message]
2015-12-19 14:53 ` [Buildroot] [PATCH v4 1/2] package/x11r7/xserver_xorg-server: bump version to 1.18.0 Thomas Petazzoni
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=itegkcxlsq.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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