On Sat, 2016-07-16 at 15:34 +0200, Michael Thayer wrote:
> On 15.07.2016 17:33, Adam Jackson wrote:
> > On Tue, 2016-07-12 at 15:56 +0200, Michael Thayer wrote:
> >
> > > I know it has just been two days, but still, a polite ping. I would
> > > also generally be interested in the question of
On 15.07.2016 17:33, Adam Jackson wrote:
On Tue, 2016-07-12 at 15:56 +0200, Michael Thayer wrote:
I know it has just been two days, but still, a polite ping. I would
also generally be interested in the question of what I can do to get
this sort of patch moving. Would reviewing other people's
On Tue, 2016-07-12 at 15:56 +0200, Michael Thayer wrote:
> I know it has just been two days, but still, a polite ping. I would
> also generally be interested in the question of what I can do to get
> this sort of patch moving. Would reviewing other people's patches be
> the right way to go,
On 10.07.2016 12:23, Michael Thayer wrote:
Hello Adam,
On 05.07.2016 20:40, Adam Jackson wrote:
On Mon, 2016-07-04 at 21:43 +0200, Michael Thayer wrote:
When submitting dirty rectangles to the kernel driver,
modesetting checks the return value, and if it gets ENOSYS
(driver does not support
Hello Adam,
On 05.07.2016 20:40, Adam Jackson wrote:
On Mon, 2016-07-04 at 21:43 +0200, Michael Thayer wrote:
When submitting dirty rectangles to the kernel driver, modesetting checks
the return value, and if it gets ENOSYS (driver does not support reporting)
or EINVAL (invalid data submitted
On 05.07.2016 22:15, Michael Thayer wrote:
On 05.07.2016 20:40, Adam Jackson wrote:
On Mon, 2016-07-04 at 21:43 +0200, Michael Thayer wrote:
When submitting dirty rectangles to the kernel driver, modesetting
checks
the return value, and if it gets ENOSYS (driver does not support
reporting)
or
On 05.07.2016 20:40, Adam Jackson wrote:
On Mon, 2016-07-04 at 21:43 +0200, Michael Thayer wrote:
When submitting dirty rectangles to the kernel driver, modesetting checks
the return value, and if it gets ENOSYS (driver does not support reporting)
or EINVAL (invalid data submitted to the kernel
On Mon, 2016-07-04 at 21:43 +0200, Michael Thayer wrote:
> When submitting dirty rectangles to the kernel driver, modesetting checks
> the return value, and if it gets ENOSYS (driver does not support reporting)
> or EINVAL (invalid data submitted to the kernel driver) it disables reporting
> for
When submitting dirty rectangles to the kernel driver, modesetting checks
the return value, and if it gets ENOSYS (driver does not support reporting)
or EINVAL (invalid data submitted to the kernel driver) it disables reporting
for the rest of the session. The second is clearly wrong, and has
