linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	Javier Martinez Canillas <javierm@redhat.com>,
	 LKML <linux-kernel@vger.kernel.org>,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	 linux-efi <linux-efi@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	 David Airlie <airlied@linux.ie>,
	Catalin Marinas <catalin.marinas@arm.com>,
	 "the arch/x86 maintainers" <x86@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	 dri-devel <dri-devel@lists.freedesktop.org>,
	Atish Patra <atish.patra@wdc.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Robinson <pbrobinson@gmail.com>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 linux-riscv <linux-riscv@lists.infradead.org>,
	Borislav Petkov <bp@suse.de>,  Will Deacon <will@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v3 0/2] allow simple{fb, drm} drivers to be used on non-x86 EFI platforms
Date: Mon, 19 Jul 2021 09:10:52 +0200	[thread overview]
Message-ID: <CAMj1kXErHteZ+MKYvp=yYmwVxV3A=vjtnG351hZHV+3BPwDQvw@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tyfNPa2f5PDBLm4w_H_riEQ5P3rEhX73YGE1y_ygRox+w@mail.gmail.com>

On Mon, 19 Jul 2021 at 04:59, Dave Airlie <airlied@gmail.com> wrote:
>
> On Thu, 15 Jul 2021 at 18:11, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> >
> > 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.
>
> Can we just merge via drm-misc and make sure the acks are present and
> I'll deal with the fallout if any.
>

Fine with me. Could you stick it on a separate branch so I can double
check whether there are any issues wrt the EFI tree?

Thanks,
Ard.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2021-07-19  7:11 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
2021-07-19  2:59     ` Dave Airlie
2021-07-19  7:10       ` Ard Biesheuvel [this message]
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='CAMj1kXErHteZ+MKYvp=yYmwVxV3A=vjtnG351hZHV+3BPwDQvw@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=aou@eecs.berkeley.edu \
    --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=tzimmermann@suse.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).