Rob McDonald from LKML contacted me about a thread currently going on on that list about open source vs. closed source drivers in the Linux kernel. He suggested that I/we may want to get involved in that discussion, both as a point of view and also as a way to get more attention for our project.
[quote] This is the latest thread... http://www.ussg.iu.edu/hypermail/linux/kernel/0512.0/0972.html Which was spawned from this... http://www.ussg.iu.edu/hypermail/linux/kernel/0512.0/0634.html Which is related to this thread I tried to point out two weeks ago... http://www.ussg.iu.edu/hypermail/linux/kernel/0511.2/1873.html [/quote] There is any number of different ways for us to get involved in that discussion. With your assistance, I could write one big letter, expressing our encouragement of remaining strictly open source and its advantages, etc. Or some of you who are on both lists could represent us there and personally get involved. Or both. Here kindof a draft I have in mind: I am the founder of the Open Graphics Project, a founder of Traversal Technology, and the moderator of the Open Graphics Mailing List. We've made it our goal to develop new graphics hardware that is fully open architecture for the purpose of having fully open source drivers that fully support all features of the hardware. One of your list members pointed me to the discussion you have been having on a related topic and suggested that I put in a statement. I used to be a LKML member, but I had to leave once the OGML traffic got too high, so if you want to contact me, you'll have to email me directly. Having been faced with Linux hardware-support challenges many times myself, I've certainly thought of circumstances where allowing binary drivers would be a good short-term solution, but I believe condoning that is a slippery slope that will lead to the corruption of the Free Software ideal. I'm not the kind of purist that believes all proprietary software is evil, but Linux is great in large part because it's open source (and stays that way because it's free software). One idea I have seen is to develop a limited kernel ABI that goes between the ever-changing interfaces of the main kernel and some fixed interface. As the kernel chances, more kruft would be added to this abstraction layer, but it would be added ONLY to that abstraction layer. It's kinda like DRI, but more generalized. This would have the advantage of allowing paranoid hardware vendors to write "legal" closed-source drivers but also discourage them from doing it, because there would be unavoidable performance disadvantages. This sounds great, but it amounts to us bending to the will of the old ways, and the old ways are broken. The monent we give them that opening is the moment we lose a lot of ground in our progress towards ubiquitous free software. It is this open source requirement for Linux that has spawned so much innovation and sharing of ideas and is the only reason why you can use so many x86-specific peripherals on a PowerPC platforms. "Don't go there," I say, because if you do, you're shooting yourself in the foot. As for other graphics vendors like ATI and nVidia, I honestly don't fault them for their business models. To them, it's far more profitable to sell to Windows users, and Linux users are in such small number by comparison that it likely costs them more to support us than they make from selling us cards. Even if I'm wrong, businesses can hurt themselves by stretching themselves too thin and trying to make too many disparate groups happy. So why don't ATI and nVidia just release specs so we can write drivers for them? Because their drivers are a huge part of their competitive advantage. As a hardware designer, I always strive to strike the best balance between software and hardware. Hardware costs a lot of money, so when you can do something in software instead without it being a burden on the system, that's what you should do. For ATI and nVidia, exposing their interfaces would expose too much about the internal workings of their designs, thereby giving away too much information to each other and other competitors. It is the capitalist thing to do to compete in whatever way makes the most sense, and those secrets are all they have to compete with each other. For Traversal Technology, the Open Graphics Project is an interesting risk. To some extent, we can afford to do this, because we are small and have integrated ourselves into the community to a huge degree. We stand as a niche player, and based on that, we create a reasonable business model. What will sell our products is the fact that they are open architecture. Although the near-term business goals of ATI and nVidial make sense, the future goes beyond just open source. It isn't enough to just release source to your drivers. Other developers need to be able to understand them and add support for features in your hardware that you didn't. And they need to be able to use your hardware in ways that you didn't anticipate. (That's one of the funnest parts, IMHO.) Although I don't expect hardware vendors in the future to release the internals of their hardware, as Traversal intends to do, I do believe we'll reach a point where every piece of hardware we use has published specs with sufficient detail that we can write good drivers for them. That's the direction we need to be headed. Let's not delay that inevitable outcome by giving hardware vendors an excuse to slide back into the old ways of doing things. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
