On Mon, Dec 15, 2014 at 4:48 PM, Dave Airlie <airlied@xxxxxxxxx> wrote:
>
> I'd be inclined to just revert this for now, it is annoying we let
> userspace away with this, but we probably need to find a better
> way to enforce it, since the cat is out of the bag.
.. why did that commit ever even get far enough to get to me?
It seems to happen on any reasonably modern Intel graphics - at least
it happens on both my laptop and my desktop. And I'm running
bog-standard F20, so either nobody ever even tested that broken thing,
or nobody bothered to look at the messages to notice it was broken.
Either way, it shows a rather distinct lack of actual testing,
wouldn't you say?
I really see no excuse for crap like this. If I find obvious bugs
immediately, on my very normal hardware and very normal distribution,
that means that there is something wrong in the development process.
If I was some subtle timing-dependent thing, or I were to be using
eally odd hardware, or I had to do something special to trigger it,
that would be one thing. But that's definitely not the case here.
Linus "not happy" Torvalds
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
