On Fri, 2022-07-15 at 11:20 +0100, Dennis Tsiang wrote:
> On 30/06/2022 08:47, Pekka Paalanen wrote:
> > On Wed, 29 Jun 2022 14:53:49 +
> > Simon Ser wrote:
> >
> > > On Wednesday, June 29th, 2022 at 16:46, Dennis Tsiang
> > > wrote:
> > >
> > > > Thanks for your comments. This is not inten
On 30/06/2022 08:47, Pekka Paalanen wrote:
On Wed, 29 Jun 2022 14:53:49 +
Simon Ser wrote:
On Wednesday, June 29th, 2022 at 16:46, Dennis Tsiang
wrote:
Thanks for your comments. This is not intended to be used for KMS, where
indeed there would be no difference. This proposal is for oth
On Wed, 29 Jun 2022 14:53:49 +
Simon Ser wrote:
> On Wednesday, June 29th, 2022 at 16:46, Dennis Tsiang
> wrote:
>
> > Thanks for your comments. This is not intended to be used for KMS, where
> > indeed there would be no difference. This proposal is for other Graphics
> > APIs such as Vulk
On Wednesday, June 29th, 2022 at 16:46, Dennis Tsiang
wrote:
> Thanks for your comments. This is not intended to be used for KMS, where
> indeed there would be no difference. This proposal is for other Graphics
> APIs such as Vulkan, which requires the application to be explicit
> upfront about
On 27/06/2022 15:50, Pekka Paalanen wrote:
On Mon, 27 Jun 2022 13:40:04 +
Dennis Tsiang wrote:
This patch is an early RFC to discuss the viable options and
alternatives for inclusion of unsigned integer formats for the DRM API.
This patch adds a new single component 16-bit and a two compo
This patch is an early RFC to discuss the viable options and
alternatives for inclusion of unsigned integer formats for the DRM API.
This patch adds a new single component 16-bit and a two component 32-bit
DRM fourcc’s that represent unsigned integer formats. The use case for
needing UINT formats,
On Mon, 27 Jun 2022 13:40:04 +
Dennis Tsiang wrote:
> This patch is an early RFC to discuss the viable options and
> alternatives for inclusion of unsigned integer formats for the DRM API.
>
> This patch adds a new single component 16-bit and a two component 32-bit
> DRM fourcc’s that repres
