public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gareth Hughes <gareth.hughes@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 4.1.0 DRM (was Re: Linux 2.4.6-ac3)
Date: Tue, 17 Jul 2001 12:37:12 +1000	[thread overview]
Message-ID: <3B53A4D8.A9613CFF@acm.org> (raw)
In-Reply-To: <E15M6jC-0005PK-00@the-village.bc.nu>	<3B532BB7.1050300@valinux.com> <3B533578.A4B6C25F@damncats.org> 	<3B53413A.6060501@valinux.com> <995312089.987.8.camel@nomade> <3B534C1F.8080100@valinux.com>

Jeff Hartmann wrote:
> 
> You have to remember this isn't an API that users program to, it is an
> API that a specific driver uses.  Each driver is different, and has a
> different API (at least a subset of it.)  The cards are so different
> that they can't have the same interfaces and remain competitive.  Each
> 3D client side driver packages up state and vertex data in a form that
> only that video card can understand.  Each new drm kernel driver
> requires a new device specific portion of the API.

Exactly.  I don't think of it as an API in the true meaning of the
term.  No one other than that specific driver should (can?) even use it.

> If we want to be secure, we have to have an interface which can remain
> competitive with insecure drivers.

Exactly.  I know myself and Keith Whitwell in particular have put a lot
of effort into making the open source drivers at least in the same
ballpark of performance as their Win32 counterparts.  People will never
seriously use Linux for 3D if performance just plain sucks.  Now, at
least they have the option of buying an NVIDIA card...

-- Gareth

  reply	other threads:[~2001-07-17  2:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 17:36 Linux 2.4.6-ac3 Alan Cox
2001-07-14 20:01 ` Zilvinas Valinskas
2001-07-14 20:05   ` Alan Cox
2001-07-15  1:45     ` Gareth Hughes
2001-07-15 13:12       ` Alan Cox
2001-07-15 14:01         ` Gareth Hughes
2001-07-15 15:31           ` Alan Cox
2001-07-16  1:29             ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Gareth Hughes
2001-07-16  1:51               ` Keith Owens
2001-07-16  2:07                 ` Gareth Hughes
2001-07-16 11:23               ` John Cavan
2001-07-16 11:39                 ` Alan Cox
2001-07-16 18:00                   ` Jeff Hartmann
2001-07-16 18:12                     ` Xavier Bestel
2001-07-16 18:32                       ` Jeff Hartmann
2001-07-16 18:42                     ` John Cavan
2001-07-16 19:32                       ` Jeff Hartmann
2001-07-16 19:34                         ` Xavier Bestel
2001-07-16 20:18                           ` Jeff Hartmann
2001-07-17  2:37                             ` Gareth Hughes [this message]
2001-07-17  8:31                           ` Mike A. Harris
2001-07-16 19:49                         ` John Cavan
2001-07-17  7:19                     ` 4.1.0 DRM Mike A. Harris
2001-07-17  5:28               ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Juan Quintela
2001-07-18  9:06                 ` Gareth Hughes
2001-07-18 16:21                   ` Juan Quintela
2001-07-18 13:30                 ` Mike A. Harris
2001-07-17 13:19             ` Linux 2.4.6-ac3 Zdenek Kabelac
2001-07-15  1:31 ` Linux 2.4.6-ac3 - some unresolved Eyal Lebedinsky
2001-07-15 13:09   ` Alan Cox

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=3B53A4D8.A9613CFF@acm.org \
    --to=gareth.hughes@acm.org \
    --cc=linux-kernel@vger.kernel.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