1 |
On Sunday 03 December 2006 09:24, Neil Bothwick <neil@××××××××××.uk> wrote |
2 |
about 'Re: [gentoo-amd64] Re: URGENT: No more fonts after xorg changes': |
3 |
> On Sun, 3 Dec 2006 07:32:23 -0600, Boyd Stephen Smith Jr. wrote: |
4 |
> > > That leaves Nvidia two choices, distribute closed source drivers for |
5 |
> > > Linux, or remove that code from the Linux drivers |
6 |
> > |
7 |
> > ...or both (release a "free" version and a "full" version), or release |
8 |
> |
9 |
> They'd probably argue that would be extra work. |
10 |
|
11 |
I agree; it's still a choice. Just exposing the lack of truth is |
12 |
the "false dichotomy" that was originally proposed. Maintaining two |
13 |
separate drivers would probably be hell; even if both derived from a |
14 |
common source-tree it would require a code-audit before every release of |
15 |
the "free" version. |
16 |
|
17 |
> > specs so we can write our own drivers (we don't need to know anything |
18 |
> > patentable or even trade-secret-able, just how to talk to the |
19 |
> > hardware) or a half-dozen other options. |
20 |
> |
21 |
> Haven't they done that already? |
22 |
|
23 |
No. The nv driver is reverse engineered, IIRC. |
24 |
|
25 |
> It's just that this doesn't work with |
26 |
> 3D, which is tied into the proprietary code. Without knowing the |
27 |
> details, which would require an NDA and then not being able to discuss |
28 |
> this, there's no way of knowing how closely the 3D stuff is tied into |
29 |
> the proprietary code. |
30 |
|
31 |
What we it is something similar to e.g. the x86 instruction set. That |
32 |
doesn't tell you anything about the specifics inside the chip, but allows |
33 |
to write software that takes advantage of all features. |
34 |
|
35 |
To write a 3D accelerated driver, we need to know what primitive operations |
36 |
the cards support and how to invoke those primitive operations. How to |
37 |
translate application-level function calls (opengl, xlib, whatever) into |
38 |
those primitives is something the F(L)/OSS community would have to figure |
39 |
out. |
40 |
|
41 |
I'm sure it would take a year or more to get to the performance and |
42 |
stability of the closed driver, but at least it would be feasible to write |
43 |
and maintain a 3d-accelerated driver in the "free world". |
44 |
|
45 |
It's possible that we could reverse engineer this information in the |
46 |
future, but that could also mean some broken cards, and it would be nearly |
47 |
impossible to maintain. |
48 |
|
49 |
> > NB: I use the nvidia driver; I don't like it, but I do use it since I |
50 |
> > do occationally play games that require accelerated 3d. |
51 |
> |
52 |
> So use a different make of card that provides equivalent performance |
53 |
> with a free driver. |
54 |
|
55 |
When next I change video cards, I will be doing just that. |
56 |
|
57 |
-- |
58 |
"If there's one thing we've established over the years, |
59 |
it's that the vast majority of our users don't have the slightest |
60 |
clue what's best for them in terms of package stability." |
61 |
-- Gentoo Developer Ciaran McCreesh |