Patrik Stridvall <[EMAIL PROTECTED]> writes:
> I have said it before and I say it again, the device
> driver interface is wrongly designed since fails to
> realize that there are two fundamentally different
> kinds of drivers. This is the _teoretical_ reason.
If they are so fundamentally different, why do you need to leave the
possibility of passing both types of coordinates to all drivers?
They are *not* fundamentally different at all; drivers take logical
coordinates, and do the mapping in the way most appropriate to the
driver. This may mean not doing anything, doing software conversion,
someday maybe using the graphics accelerator to do part of the job,
etc.
> In short, I think there are plenty of reasons both to do
> things differently than we do now as well as reasons to
> do things like I have done in my patch.
In short your reasons are: it's easier to maintain (which I strongly
disagree with), and it's faster (which is not proven at all).
> PS. Do not claim that lack of optimizations is not
> an issue. We have all seen the sucky benchmarks.
> Sure blaiming X is convienient but it isn't the
> whole story.
Fine; come back when you have benchmarks demonstrating the large
performance gains brought by your solution. Theoretical optimizations
do not mean anything.
--
Alexandre Julliard
[EMAIL PROTECTED]
