From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Ser <contact@emersion.fr>
Cc: wayland-devel <wayland-devel@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-media@vger.kernel.org
Subject: Re: [ANNOUNCE] pixfmtdb
Date: Mon, 23 Jan 2023 17:49:36 +0200 [thread overview]
Message-ID: <Y86skCbxY5kZglo8@pendragon.ideasonboard.com> (raw)
In-Reply-To: <nn8qWh16AviRPuLVOg_I-Nn747ncRsuJsZU_VZHvKhxp2hoFBCFsAfezBDkiwM-yn-CXAW_Vos121VKtETNsSZU3EuCuVzcgHBnnWNnww-g=@emersion.fr>
CC'ing the linux-media mailing list.
On Mon, Jan 23, 2023 at 02:10:58PM +0000, Simon Ser wrote:
> Hi all,
>
> In the last few days I've been working on a small new project, pixfmtdb [1].
> It's a Web database of pixel format guides, it can be useful to understand
> how pixels are laid out in memory for a given format and which formats from
> various APIs are compatible with each other.
>
> pixfmtdb relies on the Khronos Data Format Specification [2] to describe
> each format. This means that each format is described with a standardized
> data blob, which can be re-used with other tools for other purposes.
>
> My future plans include adding more formats and format families to pixfmtdb,
> and make it easy to use the data for code generation, in particular for
> automatically generating tables containing metadata about formats, as used
> in Wayland compositors and other projects.
>
> I hope some of you can find this work useful,
>
> Simon
>
> [1]: https://pixfmtdb.emersion.fr
> [2]: https://www.khronos.org/dataformat
--
Regards,
Laurent Pinchart
next parent reply other threads:[~2023-01-23 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nn8qWh16AviRPuLVOg_I-Nn747ncRsuJsZU_VZHvKhxp2hoFBCFsAfezBDkiwM-yn-CXAW_Vos121VKtETNsSZU3EuCuVzcgHBnnWNnww-g=@emersion.fr>
2023-01-23 15:49 ` Laurent Pinchart [this message]
2023-01-23 20:25 ` [ANNOUNCE] pixfmtdb Sebastian Wick
2023-01-23 22:43 ` Simon Ser
2023-01-23 23:54 ` Sebastian Wick
2023-01-24 12:03 ` Pekka Paalanen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y86skCbxY5kZglo8@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=wayland-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox