linux-kernel - Re: VKMS: New plane formats

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <22b20ed0-f3d1-c70c-1f3d-ca897330f7c6@gmail.com>
Date:   Thu, 2 Sep 2021 08:56:06 -0300
From:   Igor Matheus Andrade Torrente <igormtorrente@...il.com>
To:     Simon Ser <contact@...rsion.fr>
Cc:     rodrigosiqueiramelo@...il.com, melissa.srw@...il.com,
        hamohammed.sa@...il.com, daniel@...ll.ch, airlied@...ux.ie,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: VKMS: New plane formats

On 9/1/21 5:24 PM, Simon Ser wrote:
> Ideally the final composition format would have enough precision for
> all of the planes. I think it'd make sense to use ARGB16161616 if the
> primary plane uses ARGB8888 and an overlay plane uses ARGB16161616.
> 
> To simplify the code, maybe it's fine to always use ARGB16161616 for
> the output, and add getters which fetch an ARGB16161616 row for each
> supported plane format.
> 

This makes sense to me. I will try to implement this way.

Thanks!