From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <nick.whitlock@eizo.com>
Cc: vfazio@xes-inc.com, yann.morin.1998@free.fr, buildroot@buildroot.org
Subject: Re: [Buildroot] [External] - [PATCH] package/nvidia-driver: bump version to 550.78
Date: Wed, 7 Aug 2024 23:22:59 +0200 [thread overview]
Message-ID: <20240807232259.6536f3c9@windsurf> (raw)
In-Reply-To: <OSAPR01MB4561B7C6E4EB47DADDCDF9E084B82@OSAPR01MB4561.jpnprd01.prod.outlook.com>
Hello Nick,
On Wed, 7 Aug 2024 17:16:38 +0000
<nick.whitlock@eizo.com> wrote:
> I can look into adding a version selection mechanism.
Awesome, thanks!
> About the GTK acceleration. The library (from my understanding)
> provides GPU hardware acceleration support for GTK so it renders on
> the GPU instead of on the CPU.
But how does it hook up into Gtk to accelerate it?
> Side note:
> Originally when I wrote this patch, I wrote it with the proprietary
> NVIDIA driver in mind. However, I'm now aware of the
> open-kernel-modules package of NVIDIA and I may submit a different
> patch to add support for this (bearing in mind that the open kernel
> modules only supports Ampere and up).
I'd say it's up to you which version(s) you want to add support for, as
long as support for already supported HW is preserved (by using a
version selection). So if you add support for the open kernel modules,
which means only support for Ampere platforms is added, that's fine by
me.
BTW, instead of a version selection, we could also decide to introduce
a separate package. Maybe rename nvidia-driver to nvidia-driver-legacy,
or something similar, and add a new nvidia-driver package. This would
be sensible if the packages are radically different in their "build"
process for example.
I prefer two separate and simple packages than a single convoluted
package that supports two versions, but with in fact nothing shared
between the two versions supported.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-07 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 15:59 [Buildroot] [PATCH] package/nvidia-driver: bump version to 550.78 Nick Whitlock
2024-05-13 18:03 ` [Buildroot] [External] - " Vincent Fazio
2024-05-13 20:03 ` nick.whitlock
2024-06-12 18:13 ` nick.whitlock
2024-08-06 21:33 ` Thomas Petazzoni via buildroot
2024-08-07 17:16 ` nick.whitlock
2024-08-07 21:22 ` Thomas Petazzoni via buildroot [this message]
2024-08-08 12:57 ` nick.whitlock
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=20240807232259.6536f3c9@windsurf \
--to=buildroot@buildroot.org \
--cc=nick.whitlock@eizo.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox