> of other places too. Especially when the graphics chip maker explains > that keeping their driver source code closed isn't really an attempt > to hide their knowledge under a bushel basket. It's a defensive > measure against having their retail margins destroyed by nitwits who > take out all the busy-wait loops and recompile with -O9 to get another > tenth of a frame per second, and then pretend ignorance when > attempting to return their slagged GPU at Fry's.
Wrong as usual... The Nvidia driver and ATI drivers aren't full of magical delay loops and if there was a way to fry those cards easily in hardware the virus folks would already be doing it. The reverse engineering teams know what is in the existing code thank you. Creating new open source drivers from it is however hard because of all the corner cases. You will instead find that both vendors stopping providing Linux related source code at about the point they got Xbox related contracts. A matter which has been pointed out to various competition and legal authorities and for now where it seems to lie. Fortunately at the moment there is a simple cure - buy Intel hardware. That also has the advantage that you are more likely to get help because some of us only look at AMD processor related problems as part of official work duties nowdays, and plan to do so until AMD (as owner of ATI) behave. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
