On 9/13/23 10:14, Jocelyn Falempe wrote:
> On 12/09/2023 17:57, Michel Dänzer wrote:
>> On 9/11/23 10:38, Pekka Paalanen wrote:
>>> On Fri, 8 Sep 2023 17:10:46 +0200
>>> Thomas Zimmermann wrote:
Am 08.09.23 um 16:41 schrieb Pekka Paalanen:
> On Fri, 8 Sep 2023 15:56:51 +0200
> Thomas
On 12/09/2023 17:57, Michel Dänzer wrote:
On 9/11/23 10:38, Pekka Paalanen wrote:
On Fri, 8 Sep 2023 17:10:46 +0200
Thomas Zimmermann wrote:
Am 08.09.23 um 16:41 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 15:56:51 +0200
Thomas Zimmermann wrote:
I have a number of concerns. My point it not
On 9/11/23 10:38, Pekka Paalanen wrote:
> On Fri, 8 Sep 2023 17:10:46 +0200
> Thomas Zimmermann wrote:
>> Am 08.09.23 um 16:41 schrieb Pekka Paalanen:
>>> On Fri, 8 Sep 2023 15:56:51 +0200
>>> Thomas Zimmermann wrote:
I have a number of concerns. My point it not that we shouldn't
On Fri, Sep 08, 2023 at 05:37:27PM +0200, Thomas Zimmermann wrote:
> > > Please note that the kernel's conversion code uses memory allocation
> > > of intermediate buffers. We even recently had a discussion about
> > > allocation overhead during display updates. Userspace can surely do
> > > a
Hi
Am 11.09.23 um 12:05 schrieb Jocelyn Falempe:
[...]
Optimization always depends on the workload; something that the driver
doesn't know. For example, as we mostly move the mouse cursor around
the screen, the damages areas are usually small. Optimizing this might
be pointless in any case.
Hi
Am 11.09.23 um 10:38 schrieb Pekka Paalanen:
[...]
In the kernel, we reduce the copying to the changed parts, if we have
damage information from userspace. IDK Mesa's software renderer, but it
could certainly apply a similar optimization.
I have already assumed that everything uses damage
On 08/09/2023 17:37, Thomas Zimmermann wrote:
Hi
Am 08.09.23 um 16:48 schrieb Jocelyn Falempe:
On 08/09/2023 15:56, Thomas Zimmermann wrote:
Hi
Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn
On Fri, 8 Sep 2023 17:10:46 +0200
Thomas Zimmermann wrote:
> Hi
>
> Am 08.09.23 um 16:41 schrieb Pekka Paalanen:
> > On Fri, 8 Sep 2023 15:56:51 +0200
> > Thomas Zimmermann wrote:
> >
> >> Hi
> >>
> >> Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
> >>> On Fri, 8 Sep 2023 11:21:51 +0200
>
Hi
Am 08.09.23 um 16:48 schrieb Jocelyn Falempe:
On 08/09/2023 15:56, Thomas Zimmermann wrote:
Hi
Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But there are two
Hi
Am 08.09.23 um 16:41 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 15:56:51 +0200
Thomas Zimmermann wrote:
Hi
Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ *
On 08/09/2023 15:56, Thomas Zimmermann wrote:
Hi
Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But there are two exceptions only for dumb buffers:
+ * * To
On Fri, 8 Sep 2023 15:56:51 +0200
Thomas Zimmermann wrote:
> Hi
>
> Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
> > On Fri, 8 Sep 2023 11:21:51 +0200
> > Thomas Zimmermann wrote:
> >
> >> Hi
> >>
> >> Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
> >> [...]
> >>> + *
> >>> + * But
Hi Jocelyn
Am 08.09.23 um 16:06 schrieb Jocelyn Falempe:
[...]
And know I find that this patch (even in its v1) contains language that
retroactively legitimizes the mgag200 patch. I wrote 'apparently' I my
reply, as I assume that there's more to it, but how does it not look
like an attempt to
Hi Javier
Am 08.09.23 um 15:46 schrieb Javier Martinez Canillas:
Thomas Zimmermann writes:
Hello Thomas,
Hi Maxime
Am 08.09.23 um 12:58 schrieb Maxime Ripard:
Hi,
On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
On 08/09/2023 15:46, Javier Martinez Canillas wrote:
Thomas Zimmermann writes:
Hello Thomas,
Hi Maxime
Am 08.09.23 um 12:58 schrieb Maxime Ripard:
Hi,
On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But
Hi
Am 08.09.23 um 13:16 schrieb Pekka Paalanen:
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But there are two exceptions only for dumb buffers:
+ * * To support XRGB if it's not supported by the
Thomas Zimmermann writes:
Hello Thomas,
> Hi Maxime
>
> Am 08.09.23 um 12:58 schrieb Maxime Ripard:
>> Hi,
>>
>> On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
>>> Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
>>> [...]
+ *
+ * But there are two exceptions
On Friday, September 8th, 2023 at 22:22, Thomas Zimmermann
wrote:
> Am 08.09.23 um 12:58 schrieb Maxime Ripard:
>
> > Hi,
> >
> > On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
> >
> > > Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
> > > [...]
> > >
> > > > + *
> > > >
Hi Maxime
Am 08.09.23 um 12:58 schrieb Maxime Ripard:
Hi,
On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But there are two exceptions only for dumb buffers:
+ * * To support XRGB if it's not supported
On Fri, 8 Sep 2023 11:21:51 +0200
Thomas Zimmermann wrote:
> Hi
>
> Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
> [...]
> > + *
> > + * But there are two exceptions only for dumb buffers:
> > + * * To support XRGB if it's not supported by the hardware.
>
>
> > + * * Any
Hi,
On Fri, Sep 08, 2023 at 11:21:51AM +0200, Thomas Zimmermann wrote:
> Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
> [...]
> > + *
> > + * But there are two exceptions only for dumb buffers:
> > + * * To support XRGB if it's not supported by the hardware.
>
>
> > + * * Any
Hi
Am 25.08.23 um 16:04 schrieb Jocelyn Falempe:
[...]
+ *
+ * But there are two exceptions only for dumb buffers:
+ * * To support XRGB if it's not supported by the hardware.
+ * * Any driver is free to modify its internal representation of the
format,
+ * as long as
On Fri, 25 Aug 2023 16:04:18 +0200
Jocelyn Falempe wrote:
> After discussions on IRC, the consensus is that the DRM drivers should
> avoid software color conversion, and only advertise the formats supported
> by hardware.
> Update the doc accordingly so that the rule and exceptions are clear for
Jocelyn Falempe writes:
Hello Jocelyn,
> After discussions on IRC, the consensus is that the DRM drivers should
> avoid software color conversion, and only advertise the formats supported
> by hardware.
> Update the doc accordingly so that the rule and exceptions are clear for
> everyone.
>
>
On Fri, 25 Aug 2023 16:04:18 +0200, Jocelyn Falempe wrote:
> After discussions on IRC, the consensus is that the DRM drivers should
> avoid software color conversion, and only advertise the formats supported
> by hardware.
> Update the doc accordingly so that the rule and exceptions are clear for
After discussions on IRC, the consensus is that the DRM drivers should
avoid software color conversion, and only advertise the formats supported
by hardware.
Update the doc accordingly so that the rule and exceptions are clear for
everyone.
Acked-by: Simon Ser
Signed-off-by: Jocelyn Falempe
---
26 matches
Mail list logo
