public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] maintainer-wanted: x11-drivers/nvidia-drivers
Date: Mon, 04 Mar 2013 12:18:51 -0500	[thread overview]
Message-ID: <1362417531.25648.32.camel@rook> (raw)
In-Reply-To: <20130304162850.GA20808@waltdnes.org>

On Mon, 2013-03-04 at 11:28 -0500, Walter Dnes wrote:
> On Sun, Mar 03, 2013 at 10:48:07PM -0500, Rick "Zero_Chaos" Farina wrote
> 
> > I am sorry that this package has been such a headache for you,
> > unfortunately binary drivers (especially) are often like that. Thanks
> > for all your hard work keeping this usable.
> 
>   I'm not a C programmer, let alone a developer, so this may be a stupid
> question, but here goes... has anyone ever tried doing a HAL (Hardware
> Abstraction Layer) to present a reasonably stable interface to binary
> video drivers?  Think of it as a shim translating a "pseudo-API" into
> "the real API" that the kernel exposes directly.  Surely, we can do
> better than VESA.  Give drivers 2 options...
> 1) direct kernel access like now
> 2) access via the HAL/shim

For video drivers, there are only a few things that can be abstracted
away, e.g. hardware access synchronization, DMA, power management, a
memory manager for GPUs without dedicated video memory. And the kernel
already does have an API for this, called DRM (direct rendering
manager); see https://www.kernel.org/doc/htmldocs/drm.html

However, nvidia-drivers does not use this API, probably because they
want to share code between their Linux and Windows drivers, and the
Linux kernel's DRM API is too different from what Windows does. In
addition, there might be licensing issues: I once read an argument that
if a proprietary kernel module is too closely integrated with features
that exists only in the Linux kernel and that cannot be applicable to
other operating systems, the module might legally become a derived work
of the Linux kernel, and so would need to be open-sourced under the GPL.



  parent reply	other threads:[~2013-03-04 17:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 21:39 [gentoo-dev] maintainer-wanted: x11-drivers/nvidia-drivers Doug Goldstein
2013-03-03 22:07 ` Mike Gilbert
2013-03-03 22:08 ` Andreas K. Huettel
2013-03-04  3:48 ` Rick "Zero_Chaos" Farina
2013-03-04 16:28   ` Walter Dnes
2013-03-04 16:44     ` Carlos Silva
2013-03-05  7:01       ` Walter Dnes
2013-03-05  8:47         ` Greg KH
2013-03-06  3:33           ` Walter Dnes
2013-03-05  9:00         ` Alexander Berntsen
2013-03-04 17:18     ` Alexandre Rostovtsev [this message]
2013-03-04 19:15     ` [gentoo-dev] " Duncan
2013-03-04 11:34 ` [gentoo-dev] " Jeroen Roovers

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=1362417531.25648.32.camel@rook \
    --to=tetromino@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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