Hi Drew, Can you add some commit message where this format is doing to be used, how? I'm not sure what Wayland devs' stance is on s-o-b line is, but I'd imagine they won't object to it.
On 14 September 2017 at 21:08, Drew DeVault <[email protected]> wrote: > --- > This patch is pretty straightforward, it does what it says on the tin. > I'm interested in developing wayland compositors for monochrome > displays. > > It may also make sense to add other pixel formats, like 2bpp/4bpp > (grayscale), or 8-bit/16-bit color. > > protocol/wayland.xml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/protocol/wayland.xml b/protocol/wayland.xml > index 29b63be..2f72939 100644 > --- a/protocol/wayland.xml > +++ b/protocol/wayland.xml > @@ -291,6 +291,7 @@ > </description> > <entry name="argb8888" value="0" summary="32-bit ARGB format, [31:0] > A:R:G:B 8:8:8:8 little endian"/> > <entry name="xrgb8888" value="1" summary="32-bit RGB format, [31:0] > x:R:G:B 8:8:8:8 little endian"/> > + <entry name="m1bpp" value="2" summary="1-bit monochrome format, 8 > pixels per octet, ordered most to least significant bit" /> I believe that all the formats* are analogous to the ones used in the kernel, as defined in drm_fourcc.h. Is there such an equivalent, if not should one consider adding one first? HTH Emil * Barring wl_shm's 0 and 1, because hysterical raisins _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
