public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: URGENT: No more fonts after xorg changes
Date: Sun, 3 Dec 2006 15:04:47 -0600	[thread overview]
Message-ID: <200612031504.52901.bss03@volumehost.net> (raw)
In-Reply-To: <20061203152421.53ad8469@krikkit.digimed.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]

On Sunday 03 December 2006 09:24, Neil Bothwick <neil@digimed.co.uk> wrote 
about 'Re: [gentoo-amd64]  Re: URGENT: No more fonts after xorg changes':
> On Sun, 3 Dec 2006 07:32:23 -0600, Boyd Stephen Smith Jr. wrote:
> > > That leaves Nvidia two choices, distribute closed source drivers for
> > > Linux, or remove that code from the Linux drivers
> >
> > ...or both (release a "free" version and a "full" version), or release
>
> They'd probably argue that would be extra work.

I agree; it's still a choice.  Just exposing the lack of truth is 
the "false dichotomy" that was originally proposed.  Maintaining two 
separate drivers would probably be hell; even if both derived from a 
common source-tree it would require a code-audit before every release of 
the "free" version.

> > specs so we can write our own drivers (we don't need to know anything
> > patentable or even trade-secret-able, just how to talk to the
> > hardware) or a half-dozen other options.
>
> Haven't they done that already?

No.  The nv driver is reverse engineered, IIRC.

> It's just that this doesn't work with 
> 3D, which is tied into the proprietary code. Without knowing the
> details, which would require an NDA and then not being able to discuss
> this, there's no way of knowing how closely the 3D stuff is tied into
> the proprietary code.

What we it is something similar to e.g. the x86 instruction set.  That 
doesn't tell you anything about the specifics inside the chip, but allows 
to write software that takes advantage of all features.

To write a 3D accelerated driver, we need to know what primitive operations 
the cards support and how to invoke those primitive operations.  How to 
translate application-level function calls (opengl, xlib, whatever) into 
those primitives is something the F(L)/OSS community would have to figure 
out.

I'm sure it would take a year or more to get to the performance and 
stability of the closed driver, but at least it would be feasible to write 
and maintain a 3d-accelerated driver in the "free world".

It's possible that we could reverse engineer this information in the 
future, but that could also mean some broken cards, and it would be nearly 
impossible to maintain.

> > NB: I use the nvidia driver; I don't like it, but I do use it since I
> > do occationally play games that require accelerated 3d.
>
> So use a different make of card that provides equivalent performance
> with a free driver.

When next I change video cards, I will be doing just that.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-03 21:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 16:10 [gentoo-amd64] URGENT: No more fonts after xorg changes Clip2
2006-12-02 16:26 ` Dieter Ries
2006-12-02 19:10   ` [gentoo-amd64] " Duncan
2006-12-02 19:22     ` Dieter Ries
2006-12-02 22:26       ` Nuitari
2006-12-03 10:53     ` Neil Bothwick
2006-12-03 13:32       ` Boyd Stephen Smith Jr.
2006-12-03 15:24         ` Neil Bothwick
2006-12-03 21:04           ` Boyd Stephen Smith Jr. [this message]
2006-12-04  1:03             ` Thomas Rösner
  -- strict thread matches above, loose matches on Subject: below --
2006-12-02 23:23 Dmitri Pogosyan
2006-12-03 21:18 Dmitri Pogosyan

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=200612031504.52901.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=gentoo-amd64@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