On 12/08/2014 07:04 PM, Jani Nikula wrote: > On Mon, 08 Dec 2014, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote: >> On Mon, 08 Dec 2014, Aaron Lu <aaron.lu@xxxxxxxxx> wrote: >>> We have a new bug report that has the same problem: >>> https://bugzilla.kernel.org/show_bug.cgi?id=88941 >>> >>> The posted patch solves the problem. I know it's not perfect, but it >>> doesn't seem it would do any harm to existing systems so should be safe. >>> >>> Better, if someone can shed some light on how this should be properly >>> handled, that would be great. >> >> There was a bug report that I can't find right now that had a similar >> problem. I wrote a few patches, even somewhat polished ones (that I now >> pushed to [1] for reference) to handle extended DIDL. Unfortunately this >> didn't help the bug reporter because the right one was beyond the >> extended DIDL too, so I don't think I even sent these to the list. >> >> Anyway, just one more data point. This might help your reporter, so >> worth a try. But it doesn't solve everything. > > [1] http://cgit.freedesktop.org/~jani/drm/log/?h=didl Thanks for the info, I've asked Dmitry to give it a try. Regards, Aaron _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
