From: Javier Martinez Canillas <javierm@redhat.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-kernel@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Helge Deller <deller@gmx.de>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Oded Gabbay <ogabbay@kernel.org>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v6 1/4] video: Add auxiliary display drivers to Graphics support menu
Date: Sat, 22 Jul 2023 02:50:28 +0200 [thread overview]
Message-ID: <87jzusu5uz.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <CANiq72=RBUdFdt8=k-AACxXWrbnqfiaiViNUNxvwzGNCDkjwQA@mail.gmail.com>
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:
> On Sat, Jul 22, 2023 at 2:13 AM Javier Martinez Canillas
> <javierm@redhat.com> wrote:
>>
>> Oh, interesting. I wonder why that couldn't had been a fbdev driver then
>> using FB_VISUAL_MONO01? I'll reword then the commit message before apply
>> to the following instead:
>
> It is :)
>
> .type = FB_TYPE_PACKED_PIXELS,
> .visual = FB_VISUAL_MONO10,
>
Ah! Should had read the driver before commenting then :)
> The original distinction was more about having a place where to put
> small, simple displays that were not your usual "screen", where you
> would typically draw a custom UI, probably controlled with a few
> custom buttons, etc.
>
Got it. Then that's yet another argument for adding the auxdisplay
drivers under the same "Graphics support" menu.
>> Perfect, thanks!
>
> My pleasure!
>
> Cheers,
> Miguel
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-07-22 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 8:15 [PATCH v6 0/4] Allow disabling all native fbdev drivers and only keeping DRM emulation Javier Martinez Canillas
2023-07-19 8:15 ` [PATCH v6 1/4] video: Add auxiliary display drivers to Graphics support menu Javier Martinez Canillas
2023-07-21 22:46 ` Javier Martinez Canillas
2023-07-21 23:47 ` Miguel Ojeda
2023-07-22 0:13 ` Javier Martinez Canillas
2023-07-22 0:43 ` Miguel Ojeda
2023-07-22 0:50 ` Javier Martinez Canillas [this message]
2023-07-22 1:01 ` Miguel Ojeda
2023-07-19 8:15 ` [PATCH v6 2/4] fbdev: Move core fbdev symbols to a separate Kconfig file Javier Martinez Canillas
2023-07-19 8:15 ` [PATCH v6 3/4] fbdev: Split frame buffer support in FB and FB_CORE symbols Javier Martinez Canillas
2023-07-19 17:37 ` [PATCH v6 0/4] Allow disabling all native fbdev drivers and only keeping DRM emulation Helge Deller
2023-07-19 17:49 ` Javier Martinez Canillas
2023-07-22 10:29 ` Javier Martinez Canillas
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=87jzusu5uz.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nipun.gupta@amd.com \
--cc=ogabbay@kernel.org \
--cc=ojeda@kernel.org \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=quic_jhugo@quicinc.com \
--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;
as well as URLs for NNTP newsgroup(s).