Re: [PATCH v5 11/13] video: Use VIDEO_DAMAGE for VIDEO_COPY

2023-08-30 Thread Simon Glass
Hi Alper, On Wed, 30 Aug 2023 at 13:07, Alper Nebi Yasak wrote: > > On 2023-08-21 23:06 +03:00, Alexander Graf wrote: > > > > On 21.08.23 21:11, Simon Glass wrote: > >> Hi Alper, > >> > >> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak > >> wrote: > >>> From: Alexander Graf > >>> > >>> CONFIG_

Re: [PATCH v5 11/13] video: Use VIDEO_DAMAGE for VIDEO_COPY

2023-08-30 Thread Alper Nebi Yasak
On 2023-08-21 23:06 +03:00, Alexander Graf wrote: > > On 21.08.23 21:11, Simon Glass wrote: >> Hi Alper, >> >> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak >> wrote: >>> From: Alexander Graf >>> >>> CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we >>> print a single charac

Re: [PATCH v5 11/13] video: Use VIDEO_DAMAGE for VIDEO_COPY

2023-08-21 Thread Alexander Graf
On 21.08.23 21:11, Simon Glass wrote: Hi Alper, On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote: From: Alexander Graf CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we print a single character, it will always copy the full range of bytes from the top left corner of

Re: [PATCH v5 11/13] video: Use VIDEO_DAMAGE for VIDEO_COPY

2023-08-21 Thread Simon Glass
Hi Alper, On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote: > > From: Alexander Graf > > CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we > print a single character, it will always copy the full range of bytes > from the top left corner of the character to the lower right

[PATCH v5 11/13] video: Use VIDEO_DAMAGE for VIDEO_COPY

2023-08-21 Thread Alper Nebi Yasak
From: Alexander Graf CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we print a single character, it will always copy the full range of bytes from the top left corner of the character to the lower right onto the uncached frame buffer. This includes pretty much the full line cont