From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] maintainer-wanted: x11-drivers/nvidia-drivers
Date: Tue, 5 Mar 2013 02:01:31 -0500 [thread overview]
Message-ID: <20130305070131.GA21752@waltdnes.org> (raw)
In-Reply-To: <CA+ZvHYHeKe0CFb99C-eZXtAbi7x=T2Cr9bdsXZx64R-=XcrGiQ@mail.gmail.com>
On Mon, Mar 04, 2013 at 03:44:33PM -0100, Carlos Silva wrote
> On Mon, Mar 4, 2013 at 3:28 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
>
> > 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
>
>
> Just read this file and you'll have the answer:
> /usr/src/linux/Documentation/stable_api_nonsense.txt
Thanks. That was an eye-opener. If user-space drivers are really
that slow, we may as well stick with VESA as a fallback.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2013-03-05 7:01 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 [this message]
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
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=20130305070131.GA21752@waltdnes.org \
--to=waltdnes@waltdnes.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