mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sebastian Raase <linux@sraa.de>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Helge Deller <deller@gmx.de>
Subject: Re: [PATCH 0/2] Add monochrome framebuffer support to simple-framebuffer
Date: Wed, 11 Nov 2026 12:15:36 +0100	[thread overview]
Message-ID: <ae6f7b88-ea9a-49f7-a3ad-ba90185528c2@kernel.org> (raw)
In-Reply-To: <cover.1793758480.git.linux@sraa.de>

Hi Sebastian,

On 4-Nov-26 03:34, Sebastian Raase wrote:
> This patch series adds support for monochrome framebuffers (1 bpp, packed-pixel)
> to simple-framebuffer.
> 
> Monochrome framebuffers require far less video memory and bandwidth than
> 16bpp or 32bpp framebuffers, making them useful for small devices or FPGA
> implementations.

Thank you for your patch-series and I see that Helge has just
applied this to the fbdev tree.

Have you considered also extending the simpledrm driver to also
support these monochrome formats there ?

Most Linux distributions now a days have switched from using simplefb
to using simpledrm.

But I must admit I've no idea how well the drm subsys / kernel-mode-
setting API handles monochrome formats.

Regards,

Hans



      parent reply	other threads:[~2026-11-11 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  2:34 Sebastian Raase
2026-11-04  2:34 ` [PATCH 1/2] fbdev: simplefb: Add mono framebuffer format Sebastian Raase
2026-11-10 23:25   ` Helge Deller
2026-11-04  2:34 ` [PATCH 2/2] dt-bindings: display: simple-framebuffer: Document mono format Sebastian Raase
2026-11-11 11:15 ` Hans de Goede [this message]

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=ae6f7b88-ea9a-49f7-a3ad-ba90185528c2@kernel.org \
    --to=hansg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=deller@gmx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@sraa.de \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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
all inboxes | Powered by JetHome®