From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: linux-efi@vger.kernel.org, David Airlie <airlied@linux.ie>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel@lists.freedesktop.org,
Atish Patra <atish.patra@wdc.com>,
linux-riscv@lists.infradead.org, Will Deacon <will@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Peter Robinson <pbrobinson@gmail.com>,
Borislav Petkov <bp@suse.de>, Albert Ou <aou@eecs.berkeley.edu>,
Hans de Goede <hdegoede@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v3 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms
Date: Thu, 15 Jul 2021 10:11:50 +0200 [thread overview]
Message-ID: <8dd26141-a09c-39e2-5174-4cad8d21c49c@suse.de> (raw)
In-Reply-To: <e61cf77c-6bff-dfcc-d3df-2fb6b48e5897@redhat.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1720 bytes --]
Hi
Am 13.07.21 um 18:59 schrieb Javier Martinez Canillas:
> On 6/25/21 3:09 PM, Javier Martinez Canillas wrote:
>> The simplefb and simpledrm drivers match against a "simple-framebuffer"
>> device, but for aarch64 this is only registered when using Device Trees
>> and there's a node with a "simple-framebuffer" compatible string.
>>
>> There is no code to register a "simple-framebuffer" platform device when
>> using EFI instead. In fact, the only platform device that's registered in
>> this case is an "efi-framebuffer", which means that the efifb driver is
>> the only driver supported to have an early console with EFI on aarch64.
>>
>> The x86 architecture platform has a Generic System Framebuffers (sysfb)
>> support, that register a system frambuffer platform device. It either
>> registers a "simple-framebuffer" for the simple{fb,drm} drivers or legacy
>> VGA/EFI FB devices for the vgafb/efifb drivers.
>>
>> The sysfb is generic enough to be reused by other architectures and can be
>> moved out of the arch/x86 directory to drivers/firmware, allowing the EFI
>> logic used by non-x86 architectures to be folded into sysfb as well.
>>
>
> Any more comments on this series? It would be nice for this to land so the
> simpledrm driver could be used on aarch64 EFI systems as well.
>
> The patches have already been acked by x86 and DRM folks.
Time to get this merged, I'd say. People are asking for these patches
already.
Best regards
Thomas
>
> Best regards,
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-07-15 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 13:09 [PATCH v3 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms Javier Martinez Canillas
2021-06-25 13:09 ` [PATCH v3 1/2] drivers/firmware: move x86 Generic System Framebuffers support Javier Martinez Canillas
2021-07-13 16:59 ` [PATCH v3 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms Javier Martinez Canillas
2021-07-15 8:11 ` Thomas Zimmermann [this message]
2021-07-19 2:59 ` Dave Airlie
2021-07-19 7:10 ` Ard Biesheuvel
2021-07-20 13:01 ` Daniel Vetter
2021-07-20 13:42 ` Javier Martinez Canillas
2021-07-20 13:59 ` Daniel Vetter
2021-07-20 18:38 ` Thomas Zimmermann
2021-07-21 5:09 ` Javier Martinez Canillas
2021-07-21 10:07 ` Thomas Zimmermann
2021-07-21 10:15 ` Javier Martinez Canillas
2021-07-21 11:23 ` Daniel Vetter
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=8dd26141-a09c-39e2-5174-4cad8d21c49c@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=atish.patra@wdc.com \
--cc=bp@suse.de \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbrobinson@gmail.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).