From: Peter Stuge <peter@stuge.se>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: dri-devel@lists.freedesktop.org, hudson@trmm.net,
markus@raatikainen.cc, sam@ravnborg.org,
linux-usb@vger.kernel.org, th020394@gmail.com, lkundrak@v3.sk,
pontus.fuchs@gmail.com, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v6 3/3] drm: Add GUD USB Display driver
Date: Thu, 25 Feb 2021 09:58:24 +0000 [thread overview]
Message-ID: <20210225095825.6196.qmail@stuge.se> (raw)
In-Reply-To: <20210219121702.50964-4-noralf@tronnes.org>
Hi Noralf,
Noralf Trønnes wrote:
> The driver supports a one bit monochrome transfer format: R1. This is not
> implemented in the gadget driver. It is added in preparation for future
> monochrome e-ink displays.
I forgot, but I have a two-tone (black/red) e-ink display here, and I
also have a 3-bpp RGB TFT display.
Should we add maybe R2 and R3? (or R3/R8 for number of colours?)
I'm particularly considering the 3-bpp RGB panel for GUD use now, and
while it will surely work with say a 16-bit RGB mode many bits will
be wasted in the process.
What are your thoughts? Would you take a patch for that now, later, never?
//Peter
next prev parent reply other threads:[~2021-02-25 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 12:16 [PATCH v6 0/3] GUD USB Display driver Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 1/3] drm/uapi: Add USB connector type Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 2/3] drm/probe-helper: Check epoch counter in output_poll_execute() Noralf Trønnes
2021-02-19 12:17 ` [PATCH v6 3/3] drm: Add GUD USB Display driver Noralf Trønnes
2021-02-19 21:42 ` Peter Stuge
2021-02-20 17:27 ` Noralf Trønnes
2021-02-26 12:09 ` Noralf Trønnes
2021-02-28 1:52 ` Peter Stuge
2021-02-28 21:04 ` Noralf Trønnes
2021-02-25 9:58 ` Peter Stuge [this message]
2021-02-25 18:06 ` Noralf Trønnes
2021-02-25 21:37 ` Peter Stuge
2021-02-26 12:18 ` Noralf Trønnes
[not found] ` <20210225213729.GG20076@stuge.se>
2021-03-01 18:31 ` Peter Stuge
2021-03-01 21:41 ` Noralf Trønnes
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=20210225095825.6196.qmail@stuge.se \
--to=peter@stuge.se \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hudson@trmm.net \
--cc=linux-usb@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=markus@raatikainen.cc \
--cc=noralf@tronnes.org \
--cc=pontus.fuchs@gmail.com \
--cc=sam@ravnborg.org \
--cc=th020394@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).