Linked by Thom Holwerda on Fri 11th May 2007 18:17 UTC, submitted by diegocg
Intel "The Intel 965GM Express Chipset represents the first mobile product that implements fourth generation Intel graphics architecture. Designed to support advanced rendering features in modern graphics APIs, this chipset includes support for programmable vertex, geometry, and fragment shaders. Extending Intel's commitment to work with the X.org and Mesa communities to continuously improve and enhance the drivers, support for this new chipset is provided through the X.org 2.0 Intel driver and the Mesa 6.5.3 releases. These drivers represent significant work by both Intel and the broader open source community."
Permalink for comment 239532
To read all comments associated with this story, please click here.
RE[4]: OpenGL support
by kaiwai on Fri 11th May 2007 23:10 UTC in reply to "RE[3]: OpenGL support"
kaiwai
Member since:
2005-07-06

FreeBSD and Solaris face challenges because Linux DRI is advancing beyond their capabilities, mainly due to contributions from Intel. FreeBSD and especially Solaris are mostly locked into the frameworks they have. This is the double-edged sword of stable interfaces. As nVidia works to keep their shim in sync with Linux DRI, it becomes a hassle to continue to support these other kernels.


Pardon - you do realise that DRI exists in both Solaris and FreeBSD; Solaris has the Intel driver merged, the DRI merged and Mesa is included with Solaris as well.

There is no double edge to a stable interface - what it does mean is this; when you design an interface, it'll take longer - rather than throwing ideas at a wall and see what sticks, it'll require going away, designing, arguing, debating, analysing then implementing - sure, it'll take longer, but what it means is that the API has been properly thought out before being merged - and better still modular enough so that new features can be added without breaking compatibility.

A prime example of this would be Solaris's new network driver API which covers all the facits of networking, and when features are added, such as WPA support, all wireless drivers support it by virtue of it being in the actual driver API rather than it being an after thought.

I don't want to bash Linux, but to me, it always seems that people just keep throwing ideas and see what sticks rather than sitting down and logically thinking out what the requirements of the API are and all the various issues that surround it.

Reply Parent Score: 5