Slashdot Mirror
Trident Micro Update
grendelkhan writes: "According to Linux Today, Trident is denying that they are no longer supporting open source developers for XFree86." This message from Eich clarifies the events leading up to this. Looks like Trident chips will continue to be supported, one way or another.
If I read all of the above correctly...
Trident's policy has been, and still is, to require an NDA. That NDA prohibits source code distribution of a driver based off information obtained under NDA. Apparantly, from the successful development of drivers for past Trident chipsets, this part wasn't enforced.
Now, Trident seems to be enforcing that part -- by not providing information to XFree86 developers on the CyberBladeXP and CyberBladeXPm chipsets. The XFree86 developers wanted to amend the NDA to allow source distribution.
Since there has been no change in the NDA, only in enforcement, Trident is claiming that they provide the same support as before. Technically, they do -- sign the NDA and provide binary-only drivers and they'll provide docs.
So, if you support the idea of source code availability for video drivers, keep an eye on the graphics chipset used in your next potential laptop. If it is Trident, look elsewhere.
Learning HOW to think is more important than learning WHAT to think.
I think this is a good lesson for everyone, reminding us of the importance of checking the facts or delving further into the issue when a story is posted on Slashdot before sounding off on it. However, don't feel too bad about what you said. The official reply from Trident didn't address the XF86 developer's request to sign an NDA without the "source code exception clause." Until that is addressed, I don't think the issue has been fully resolved.
The poster has given a dead on assessment of the current Trident situation. Trident will not give documentation to XFree86 under the conditions it has previously agreed to give the documentation. XFree86 cannot accept an NDA agreement that requires obfuscating source code, or receiving only a binary component for a feature supported by XFree86.
Who cares that Trident SAYS they support the Linux community if they make it functionally impossible to produce code based on their "support"?
If you want to have working Trident drivers for Linux, the Linux community will still have to apply its consumer pressure in order for XFree86 to be able to provide Trident drivers.
There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
Which is the entire purpose behind writing a NICE letter instead of a nasty flaming one. At least when you write a well supported polite, yet negative letter and your source of information turns out to not be completely accurate, you're able to say "oops, sorry my bad" and back off gracefully instead of REALLY looking like an idiot.
Its in Trident's best interests to have linux based drivers available, even if they don't want to support them in any way. They have a product to protect and I can understand why they don't want to post the specs publicly, but they realize that in time, given enough effort, someone will eventually reverse engineer their products. The point is, by the time that happens, those products will be obsolete and newer versions will be available. As long as the specs are available under an NDA, the drivers can still be released and the driver source, while maybe revealing more information than a binary driver would, still keeps hidden much of the internal workings of the device, until such time its no longer that important.
However, if Trident decided to completely turn their back on open source developers and suddenly a related OS were to gain a significant hold on the market, they'd be forced to play catch-up, but as long as they have drivers available, even unsupported by the company, they're on an even playing field, with no harm done.
-Restil
Play with my webcams and lights here