From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 08/10 v7] package/nvidia-tegra23-binaries: new package
Date: Sat, 7 Mar 2015 09:03:54 +0100 [thread overview]
Message-ID: <20150307090354.60c844a3@free-electrons.com> (raw)
In-Reply-To: <20150306231558.GE4220@free.fr>
Dear Yann E. MORIN,
Adding Bernd in the Cc loop, he might have some insights.
On Sat, 7 Mar 2015 00:15:58 +0100, Yann E. MORIN wrote:
> OK, we have the current situation:
>
> - Buildroot uses Xorg 1.17.1, which implements ABI 19;
>
> - nvidia-tegra23 only has support for ABI up to 14;
>
> - NVidia won't update those drivers.
Correct, that's my understanding.
> Question: is Xorg ABI backward compatible? I.e. are drivers written for
> a specific ABI able to work on a newer ABI?
My understanding is that no, there is no backward compatibility. Maybe
I'm wrong, but I remember a few years ago having to downgrade the X.org
server version + a bunch of other X.org libraries, in order to have a
sufficiently old X.org server to match the ABI used by proprietary ATI
drivers.
Now the question is: is it possible to offer a version selection for
the X.org server ? Will an old X.org server build/work fine with recent
versions of the X.org libraries around it, so that we only have to
change the version of the X.org server, or will we enter an horrible
mess of "if the X.org server is at version <foo>, then we must use
version <bar> of this library, and version <foobar> of this other
library" ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-07 8:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 20:01 [Buildroot] [PATCH 0/10 v7] NVidia GPU binary blobs for x86 and ARM (branch yem/gfx2) Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 01/10 v7] package/python-lxml: new host package Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 02/10 v7] package/python-lxml: add target variant Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 03/10 v7] package/mesa3d-headers: new package Yann E. MORIN
2015-02-11 14:06 ` Nicolas Serafini
2015-02-11 18:02 ` Yann E. MORIN
2015-02-12 17:25 ` Nicolas Serafini
2015-02-20 12:39 ` Jérôme Pouiller
2015-02-14 9:09 ` Thomas Petazzoni
2015-02-14 9:12 ` Yann E. MORIN
2015-02-21 16:43 ` Thomas Petazzoni
2015-02-10 20:01 ` [Buildroot] [PATCH 04/10 v7] package/mesa3d-headers: also install dri header and .pc file Yann E. MORIN
2015-02-21 16:45 ` Thomas Petazzoni
2015-02-10 20:01 ` [Buildroot] [PATCH 05/10 v7] package/nvidia-driver: add NVidia's OpenGL binary blob Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 06/10 v7] package/nvidia-driver: Add gl.pc Yann E. MORIN
2015-04-24 20:16 ` Bernd Kuhls
2015-04-24 20:53 ` Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 07/10 v7] package/nvidia-driver: build the kernel module Yann E. MORIN
2015-02-21 22:30 ` Thomas Petazzoni
2015-02-10 20:01 ` [Buildroot] [PATCH 08/10 v7] package/nvidia-tegra23-binaries: new package Yann E. MORIN
2015-02-11 13:42 ` Nicolas Serafini
2015-02-11 17:52 ` Yann E. MORIN
2015-02-21 22:46 ` Thomas Petazzoni
2015-02-21 22:58 ` Yann E. MORIN
2015-02-23 11:41 ` Nicolas Serafini
2015-03-04 22:39 ` Laurent Colloud
2015-03-06 23:15 ` Yann E. MORIN
2015-03-07 8:03 ` Thomas Petazzoni [this message]
2015-03-07 9:53 ` Bernd Kuhls
2015-03-07 13:01 ` Yann E. MORIN
2015-03-07 13:19 ` Thomas Petazzoni
2015-03-07 15:04 ` Yann E. MORIN
2015-03-09 19:25 ` Laurent Colloud
2015-03-09 21:27 ` Yann E. MORIN
2015-03-10 10:07 ` Nicolas Serafini
2015-03-07 8:05 ` Thomas Petazzoni
2015-03-07 8:06 ` Thomas Petazzoni
2015-02-10 20:01 ` [Buildroot] [PATCH 09/10 v7] package.nvidia-tegra23-binaries: add gstreamer plugins Yann E. MORIN
2015-02-10 20:01 ` [Buildroot] [PATCH 10/10 v7] package/nvidia-tegra23-codecs: new package Yann E. MORIN
2015-02-10 20:10 ` [Buildroot] [PATCH 0/10 v7] NVidia GPU binary blobs for x86 and ARM (branch yem/gfx2) Yann E. MORIN
2015-02-14 8:59 ` 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=20150307090354.60c844a3@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