Slashdot Mirror

That would be relevant if the unused code was very tightly mixed with the used code.

In this case, if you look at the way they detect unused code, you'll see that all the code that was removed consists of whole methods and sometimes whole classes. This means that the vast majority of the code that was removed would probably never be loaded in the instruction cache anyway -- very small methods tend to be inlined by the compiler and so don't cause surrounding (and potentially unused) code to be loaded to the cache.

• Microsoft - Conspiracy theorists find a way to blame Microsoft for every problem in Linux. This time they point out when Microsoft decided to use a vendor's chip in the XBox consoles or chipset vendors puts DirectX 8.0 support you don't get specs any more.
  
• ??? - Patents and fear of competitors or patent scumsucking companies bringing infringement. Vendors claim releasing chipset docs to the public may make it easier for these things to be found; however, most X.org developers have no problem signing suitable NDAs .
  
• Profit - Graphics card manufacturing is a very competitive industry, especially in the high-end gaming, 3-6 month development cycle, grind-out-
  as-many-different-cards-as-you-can. Quake 3 speeds are spotted in binary drivers any way and it doesn't explain fglrx which are some of the most unsuitable drivers for gaming on Linux.

For those who haven't read it yet, David Airlied's LCA 2007 talk is a really good and entertaining piece: http://www.skynet.ie/~airlied/talks/lca07/nouveau. odp (yes, server's mime-type is probably wrong, you have to save it first)

If you don't have Open Office, you can convert it here

http://media-convert.com/convert/index.php

this link might work

http://www.media-convert.com/convert/?xid=jzkoos

I'd understand the "give us our whatever-blobs"-attitude better if the "half" of the proprietary drivers people want wouldn't suck so bad. On my 64-bit Ubuntu, the proprietary ATI fglrx drivers:
- Hang the whole machine every time I logout (apparently because I'm using DVI output... gosh!), so I exit that installation of Ubuntu (which is not my primary, just testing the fglrx drivers etc. there) with alt-sysrq-e/i/s/u/b because it's safer.
- Give only green stripes and a complete hang if using _both_ DVI and VGA outputs at the same time (oh my god, we never though that could happen!).
- Do not give any 3D support if I happen not to disable Composite/AIGLX in Xorg.conf.

...while the reverse-engineered drivers give my Radeon X800 card 3D acceleration, DVI output, DVI+VGA output, accelerated Beryl 3D desktop via AIGLX etc. just finely. So I just don't belive in the FUD (from eg. NVIDIA) that they are so complex and extremely difficult to write, that the worldwide OSS community couldn't do that - those handful of reverse-engineering people are already doing better drivers than ATI with all the in-house knowledge!

I do symphatize with the people who just want "stuff to work", and know that NVIDIA proprietary drivers happen to be better quality at this time, but all my experiences with binary blobs has been so bad that I will take reverse-engineered drivers anytime, even for NVIDIA.

For those who haven't read it yet, David Airlied's LCA 2007 talk is a really good and entertaining piece: http://www.skynet.ie/~airlied/talks/lca07/nouveau. odp (yes, server's mime-type is probably wrong, you have to save it first)

Interesting timing. I have a E6600 system on order with a $50 Asus EAX550 video card based on the hoary ATI R300 core so I could run an open source video driver. Plenty fast enough for 2D and potentially some low-end (non-game) 3D. I tried hard to find something newer and faster, but failed. Matrox has a fully open source driver for some of its older cards, expensive, with lamentable performance, and the second head wouldn't drive the required frequency, which completely negates Matrox's long standing reputation for excellent finals. What I used to like about Matrox is you always knew what you were getting, even if it was a little behind the curve. Then the day came when Microsoft update pushed a new Matrox driver that eliminated multidesk support with narry a "this might screw you over" or "really do this?" I was in the middle of a deadline push and lost half a day discovering that Matrox had fed this into the Microsoft update pipeline in full deliberation. It proved faster to buy an ATI product than research alternative multidesk implementations in software. Still, I have a fondness for what Matrox used to stand for back when NVidia was setting benchmark records with finals that rendered fifty tints of pastel grey.

Since I collected these links just two days ago, I might as well include them:

http://www.skynet.ie/~airlied/talks/ols06/ols2006. odp -- DCC 2006, MIME problem, but opens with evince directly
http://www.skynet.ie/~airlied/talks/ddc05/ddc_pres .sxi -- DCC 2005, didn't read this one myself
http://free3d.org/
http://intellinuxgraphics.org/
http://dri.freedesktop.org/wiki/
http://www.phoronix.com/scan.php?page=article&item =576&num=1
http://www.phoronix.com/scan.php?page=article&item =463&num=1

Interesting timing. I have a E6600 system on order with a $50 Asus EAX550 video card based on the hoary ATI R300 core so I could run an open source video driver. Plenty fast enough for 2D and potentially some low-end (non-game) 3D. I tried hard to find something newer and faster, but failed. Matrox has a fully open source driver for some of its older cards, expensive, with lamentable performance, and the second head wouldn't drive the required frequency, which completely negates Matrox's long standing reputation for excellent finals. What I used to like about Matrox is you always knew what you were getting, even if it was a little behind the curve. Then the day came when Microsoft update pushed a new Matrox driver that eliminated multidesk support with narry a "this might screw you over" or "really do this?" I was in the middle of a deadline push and lost half a day discovering that Matrox had fed this into the Microsoft update pipeline in full deliberation. It proved faster to buy an ATI product than research alternative multidesk implementations in software. Still, I have a fondness for what Matrox used to stand for back when NVidia was setting benchmark records with finals that rendered fifty tints of pastel grey.

Since I collected these links just two days ago, I might as well include them:

http://www.skynet.ie/~airlied/talks/ols06/ols2006. odp -- DCC 2006, MIME problem, but opens with evince directly
http://www.skynet.ie/~airlied/talks/ddc05/ddc_pres .sxi -- DCC 2005, didn't read this one myself
http://free3d.org/
http://intellinuxgraphics.org/
http://dri.freedesktop.org/wiki/
http://www.phoronix.com/scan.php?page=article&item =576&num=1
http://www.phoronix.com/scan.php?page=article&item =463&num=1

Minix runs on Xen (and Xen can be part of Linux).