On Fri, Jul 22, 2011 at 01:50:04PM -0700, Keith Packard wrote: > On Sat, 23 Jul 2011 00:23:36 +0400, Kirill Smelkov <kirr@xxxxxxxxxx> wrote: > > > What kind of a workaround are you talking about? > > Just reverting the commit -- that makes your machine work, even if it's > wrong for other machines. Yes, I could revert it. But since the driver is reasonably complex, it is better to know what I'm doing and that the change makes sense, especially when it's not "my machine", but lots of target boards located all over the country. That's why I wanted, and imho reasonably, because I did the homework, your feedback - to be not on my own, alone. > > Sorry, to me it all looked like "UMS is being ignored forever". > > You're right, of course -- UMS is a huge wart on the kernel driver at > this point, keeping it working while also adding new functionality > continues to cause challenges. We tend to expect that most people will > run reasonably contemporaneous kernel and user space code, and so three > years after the switch, it continues to surprise us when someone > actually tries UMS. We are planning upgrade to KMS too. The kernel is upgraded more often compared to userspace, because of already mentioned (thanks!) "no regression" rule. Userspace is more complex and more work in my context, so it is lagging, but eventually we'll get there. So I hope some day, when everyone upgrades, UMS support could be "cleaned up" out from the driver. > > I'm out of office till ~ next week's tuesday, and on return I'll try > > to test it on the hardware in question. > > Let me know; I've pushed this patch to my drm-intel-fixes tree on > kernel.org in the meantime; if it does solve the problem, I'd like to > add your Tested-by: line. Yes, sure, I'll let you know the results. Thanks, Kirill _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
