Creative to build Linux 3D drivers 131
James Hall writes "Jon Taylor recently posted a message to the linux-ggi list indicating that he is going to be working for Creative Labs to build both Linux sound drivers for the Live cards as well as drivers (binary only) for all the graphics cards Creative makes (including cards based around 3DFX, nVidia, 3DLabs, and Rendition chipsets).
The message has been circulating around (I found it on the opengl-gamedev-l mailing list) but the original can be found
here. "
Creative Labs DVD... (Score:1)
We need *chipset* drivers, not board drivers (Score:1)
What about FreeBSD? (Score:1)
What about X drivers? (Score:1)
It is all very nice to have GGI drivers, but Linus has stated that they will never be included in the standard kernel.
What about X drivers so the rest of us can use them? (these would also be portable to other free unices)
Creative Labs DVD... (Score:1)
Binary-only is support? (Score:1)
In short, I fear that Creative is going to find that having Linux drivers is no good for their sales, since nobody is going to include those drivers with their distributions and many people of the musical persuasion are uncomfortable going somewhere on the Internet to download their drivers. Is the Linux community going to get a black eye over this? You bet! When Creative discontinues Linux support because "Linux people don't use sound cards" (as verified by their FTP download logs, showing negligible downloads of their drivers), it'll make all sorts of other companies currently interested in Linux take a step backwards.
-- Eric
Open Source drivers! (Score:1)
Frisjes (Score:1)
(that's cool in Dutch)
Hmm too bad it's not open-source, but it's a step in the right direction. It's a good thing companies finally dare to step on the Linux platform. With the rate of companies committing at least somewhat to Linux, I dare to say that we have gained a critical mass. Not that anyone noticed that yet.
Anyway, as always, only buy hardware that supports you - whether it be just Linux, open source, or all the way - free software. Make vendors know your needs. Marketing droids only understand sales figures.
- ze Apocalyptic Lawnmower
Open Source drivers! (Score:1)
I hope someone can convince Creative and the other hardware companies to release the specs to thier hardware... They make money selling hardware, not selling drivers...
Yes, yes, yes... (Score:1)
Open Source drivers! (Score:1)
TedC
"Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who
Androids of Tara?
Binary-only is support? (Score:1)
Close, but no cigar. (Score:1)
Close, but no cigar. (Score:1)
imagine you buy a car ... the car company doesn't tell you how to drive it ... you have to use THEIR driver .... you can't hire a different driver ... and you can't drive it yourself ... that's what happens ....
what they should give out is the interface ... NOT the implementation ... the product is the hardware ... not the software ... not to mention that your understanding of patent laws is not that good ... if they have something patented ... they can make it completely public ... no-one can copy it .... plus if you already made something public ... no one can patent it ...
creative should make all the INTERFACES to their hardware public ... and provide sample drivers and smale source code ...
if I were to argument like you ... "CPU companies should keep their instruction sets secret and only provide you with a compiler ..." ... I mean they don't want a bunch of broken compilers ... and they don't want others to discover how their cpu works .... and car companies should not allow you to drive your car by yourself ... you probably aren't as good of a driver ...
your logic is extremely flawed
woohoo! (Score:1)
SBLive drivers (Score:1)
woohoo is right (Score:1)
Coooooooooooollllllllllllllll (Score:1)
HAPPY HAPPY, JOY JOY
Much needed advancment (Score:1)
Binary drivers. (Score:1)
They're better than nothing.
That's not saying a lot though.
As a community, it's our role to say, "Thank you for the support" - but not leave it at that. Long term, we want open source.
Linux plays by different rules than Windows. Hardware vendors will eventually need to realize this, or lose market share and profits.
I hope the community never comes to accept binary-only drivers. At least we can be sure that Debian never will.
Cheers,
- Jim
:O (Score:1)
Yes, at http://www.cnetusa.com [cnetusa.com].
Thank you for your input (Score:1)
BTW, would you care to sign your name to that?
--
Yeah, but we like to program too (Score:1)
Personally, I'm more than happy to leave the driver level stuff to the people who make the card. I long for the day I can buy a hot new video card, install the custom accelerated X server (or module) off of the CD, and be up and running. Same for a sound card. I personally prefer to play with my system as a whole, and not have to worry about compiling or hand reviewing everything that's on it. I'd never have time for Quake if I did. =)
Now if that's your thing, more power to you. There was a time when I was a bit twiddler, poking values to io ports, and polling for status returns. But, most people have no need for the intimate details of hardware specs. It's not something that *has* to be out there. More importantly, if driver level programming is your thing, get out where you can exercise it.
Binary drivers will be disassembled/decompiled (Score:1)
There are at least three very solid reasons why this will (and must) happen:
1. The kernel is not a protected space and this makes it extremely sensitive to programming faults (driver experts are not necessarily total kernel experts, and most are human too). Faults need to be fixed rapidly, and corporate teams cannot always do that because the resource may be committed to another project. Furthermore, if the fault is actually a design fault then corporates may not be keen to acknowledge that they've made a large balls'up, and sometimes don't even acknowledge that there *is* a fault if it's not a showstopper. That is not adequate.
2. The lack of access protection in the kernel makes it a security risk to have unreviewed code there. It is really easy to pop a cracker-infected module into the kernel and unwittingly compromise the operating system's security in just about any way the cracker likes. This is so scary that this reason alone is enough to make binary drivers complete anathema for many.
3. You buy powerful I/O hardware to offload some of the CPU's work onto it, not for the manufacturer to offload some of his hardware processing onto your CPU. If your CPU seems to be spending too many cycles in the driver, the first port of call is to see what the driver is doing.
These are powerful reasons. Manufacturers like Creative don't seem to understand these driving forces at all at present, but in time they will. They will have no option, because fighting the way that the community does things will be commercial suicide in a market that they are trying to attract, not disaffect.
Yeehaw! (Score:1)
Creative and NT (Score:1)
if you care,
took Creative to task for their disastrous NT drivers for Live, and supposed support for that platform. Aside from that,their SB 16 NT drivers as of this last summer were _STILL_ full of bugs! For an integrated chip on a dual processor Tyan board (my experience), you'd think they might get the F***ing drivers up to snuff for NT. Winamp-> 2 seconds -> Blue Screen.
It was that freakin bad.
Zanshin gutted their driver for Live and told them all the stupid mistakes they were making. Nice case of closed source drivers being handed out to good programmers and causing total frustration.
Whatever CL pulls off with cool hardware or graphics fanciness, they'll never get my biz.
I hope this new Linux stud does a good job, at least he's already closer to the customer base.
Wow (Score:1)
Dangerous Precedent (Score:1)
KutUitdrukking (Score:1)
translates to: "All losers suck"
X is crap, and no choice for the future (Score:1)
The biggest obstacle to Linux on the desktop is the vast waste of memory and other processor time of X.
While X certainly uses a fair amount of memory, ps indicates it's only used 1.5% of CPU time for me at the moment. I don't consider that "vast".
X offers very little functionality for a desktop system,
Please explain. What functionality does a desktop system need that can't be implemented as an application using X?
and the networking stuff is inefficient.
Another unsupported statement.
The solution: XFree should focus on making a smaller and more usable package, and leave the direct graphics stuff up to GGI.
Or: Implement only GGI/KGIcon drivers (which should be highly portable as well), and run X via Xggi.
You'll have to come up with a pretty damned good reason to explain exactly how adding an extra layer is going to reduce the "inefficiency" you criticise.
We manufacture open video capture card now (Score:1)
We have fully open, with GPLed drivers, LML33 video capture card with hardware JPEG codec [linuxmedialabs.com].
You're welcome to look at and if you want to support the notion of open hardware and want to
have fun messing with registers and bits - order the darn board.
closed-source == I won't buy it (Score:1)
I realize that probably alot of the reason that things are kept closed are because of NDAs Creative and other companies have with 3dfx and such, and I understand. But you should also understand that my understanding still won't motivate me to throw money at you for your products.
If this were something similar to the Neomagic Xfree86 driver development, where it was almost expected that the driver would be opened later when Neomagic realized it wouldn't hurt them, I'd probably be more optimistic. However, this is quite a different situation, and even this developer admits it. Most of this code is *never* going to see the light of day. Does this guy think he really is *that* much of an uber-coder that he can write all of those drivers *on his own*, without missing something? I don't feel like seeing exploit code for a proprietary sound driver on bugtraq one day, thanks. I'll go without a 3d accelerator and even other basic hardware until the entire industry takes its collective head out of its collective arse.
ATI Video Cards VS. Creative? (Score:1)
I would be interested if anyone has had experience with them from a server or workstation perspective.
Thanks
ATI Video Cards VS. Creative? (Score:1)
Nick
LSG
What the H*ll is a 'Driver'? (Score:1)
After much flame (Score:1)
Should have gone with the Creative TNT... (Score:1)
Proprietary, yes. Crap, no (Score:1)
After much flame (Score:1)
Actually, faxing them is probably one of the best ways to go. Someone will actually take the time to try to work through your problem, unlike the people who are on the phone and are supposed to try to keep the call to a 12 minute average.
Hmm... I guess this makes my choice easy (Score:1)
Creative is moving in the right direction, I hope they reconsider and open-source the drivers... although I guess they don't want release Linux drivers for their cards and thus support every manufacturer's other card that uses the same chipset. Their work/time/money would be benifit other companies as much as it would their own. I can sympathize.
Really what should happen is the chip makers release generic drivers for the chipsets. Overall this is good though. In the long run it won't really be an issue though, eventually every chip maker/manufacturer will be forced to make Linux drivers due to demand (it'll happen). Those who don't will be at a weakness as Linux support is viewed more and more important.
Sound Blaster Pro (Score:1)
ICQ:15037019
Email:15037019@pager.mirabilis.com
Binary-only is support? (Score:1)
Creative Labs DVD... (Score:1)
What trade secrects are in 3D drivers? (Score:1)
-The 3D stuff is done in software.
-Building 3D boards is ridiculously easy and making drivers is the hard part.
Of course, if the first one is the case, doesn't this defeat the purpose of hardware acceleration?
If the second one is the case, then the real difference between the voodoo I and the voodoo II is the driver?
Shouldn't the interface to 3D hardware be similar to the programmer's interface to openGL? I.e. here's a polygon. Here's the textures. Here's the viewport. Draw it. What could possibly be so secret about that. Can someone please answer this, it's been bugging me for a while.
What about other OSs? (Score:1)
What if Intel did this? (Score:1)
Have a cigar. (Score:1)
2) There will be one driver included in standard dists that works 100% in all hardware combinations. As opposed to the one that works at 95% optimal.
One point - in the article he said some parts would be kept secret due to alorithms creative wants to protect. Does this mean he would roughly label what they do and so people can write a (perhaps less efficient) free version?
Open Source drivers! (Score:1)
That's the single most intelligent thing I've heard in the war against "lock and key hardware".
I think it's time manufacturers started listening to those of us who buy the hardware. If I spend money on a high-end card, I want it to be ready to run on whichever Linux I choose
Binary-only is support? (Score:1)
For myself, it will definitely affect a future buy decision if I can look at for example, Gateway or Dell's component list for a system, and determine either directly or by going to the component vendors' web pages, that drivers are available for Linux. It would affect my decision even more directly if the computer vendor provided drivers on their "System Restoration" CD.
Creative Labs DVD... (Score:1)
What the H*ll is a 'Driver'? (Score:1)
In addition he mentioned OpenGL support