From: Linus Walleij <linus.walleij@linaro.org> To: Peter Collingbourne <pcc@google.com>, John Stultz <john.stultz@linaro.org> Cc: Daniel Vetter <daniel@ffwll.ch>, Neil Armstrong <narmstrong@baylibre.com>, Eric Anholt <emma@anholt.net>, Kevin Brodsky <kevin.brodsky@arm.com>, Russell King <linux@armlinux.org.uk>, ML dri-devel <dri-devel@lists.freedesktop.org>, Sean Paul <sean@poorly.run>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] Revert "video: fbdev: amba-clcd: Retire elder CLCD driver" Date: Sun, 5 Dec 2021 14:34:16 +0100 [thread overview] Message-ID: <CACRpkdYGG-6OoWD29Jqo9dnhfWc2KMxpbCdRRYRmpuciiVrLAw@mail.gmail.com> (raw) In-Reply-To: <CAMn1gO7w1wUo3e9vUmGeF7fp0K9mq2ydSskX2xD3H=Kndzhc+A@mail.gmail.com> Hi Peter, [Paging John Stultz on this] On Tue, Sep 29, 2020 at 6:30 PM Peter Collingbourne <pcc@google.com> wrote: > On Tue, Sep 29, 2020 at 2:32 AM Daniel Vetter <daniel@ffwll.ch> wrote: > > On Tue, Sep 29, 2020 at 09:28:56AM +0200, Neil Armstrong wrote: > > > Can't Android FVP use drm-hwcomposer instead ? > > Not without kernel changes. See e.g. > https://www.spinics.net/lists/dri-devel/msg255883.html Has this gotten better in the last year+ so you can now use drm-hwcomposer? I.e. can we now delete the fbdev driver? > > Also, if we need to add more random fbdev ioctls to the drm fbdev > > emulation, then let's do that. Not keep fbdev drivers on life support for > > longer than necessary. I wanted to fix this and started to look at it at one point, however the required Android userspace build was a bit intimidating to get going. I would be able to look into this if a prebuilt Android for the emulation model was available. Yours, Linus Walleij _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org> To: Peter Collingbourne <pcc@google.com>, John Stultz <john.stultz@linaro.org> Cc: Eric Anholt <emma@anholt.net>, Neil Armstrong <narmstrong@baylibre.com>, Kevin Brodsky <kevin.brodsky@arm.com>, Russell King <linux@armlinux.org.uk>, ML dri-devel <dri-devel@lists.freedesktop.org>, Sean Paul <sean@poorly.run>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] Revert "video: fbdev: amba-clcd: Retire elder CLCD driver" Date: Sun, 5 Dec 2021 14:34:16 +0100 [thread overview] Message-ID: <CACRpkdYGG-6OoWD29Jqo9dnhfWc2KMxpbCdRRYRmpuciiVrLAw@mail.gmail.com> (raw) In-Reply-To: <CAMn1gO7w1wUo3e9vUmGeF7fp0K9mq2ydSskX2xD3H=Kndzhc+A@mail.gmail.com> Hi Peter, [Paging John Stultz on this] On Tue, Sep 29, 2020 at 6:30 PM Peter Collingbourne <pcc@google.com> wrote: > On Tue, Sep 29, 2020 at 2:32 AM Daniel Vetter <daniel@ffwll.ch> wrote: > > On Tue, Sep 29, 2020 at 09:28:56AM +0200, Neil Armstrong wrote: > > > Can't Android FVP use drm-hwcomposer instead ? > > Not without kernel changes. See e.g. > https://www.spinics.net/lists/dri-devel/msg255883.html Has this gotten better in the last year+ so you can now use drm-hwcomposer? I.e. can we now delete the fbdev driver? > > Also, if we need to add more random fbdev ioctls to the drm fbdev > > emulation, then let's do that. Not keep fbdev drivers on life support for > > longer than necessary. I wanted to fix this and started to look at it at one point, however the required Android userspace build was a bit intimidating to get going. I would be able to look into this if a prebuilt Android for the emulation model was available. Yours, Linus Walleij
next prev parent reply other threads:[~2021-12-05 13:35 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-28 20:08 [PATCH] Revert "video: fbdev: amba-clcd: Retire elder CLCD driver" Peter Collingbourne 2020-09-28 20:08 ` Peter Collingbourne 2020-09-29 7:28 ` Neil Armstrong 2020-09-29 7:28 ` Neil Armstrong 2020-09-29 9:32 ` Daniel Vetter 2020-09-29 9:32 ` Daniel Vetter 2020-09-29 16:30 ` Peter Collingbourne 2020-09-29 16:30 ` Peter Collingbourne 2020-09-29 16:48 ` Daniel Vetter 2020-09-29 16:48 ` Daniel Vetter 2020-09-29 16:52 ` Daniel Vetter 2020-09-29 16:52 ` Daniel Vetter 2020-09-29 17:49 ` Peter Collingbourne 2020-09-29 17:49 ` Peter Collingbourne 2020-09-29 18:41 ` Daniel Vetter 2020-09-29 18:41 ` Daniel Vetter 2020-09-29 18:44 ` Daniel Vetter 2020-09-29 18:44 ` Daniel Vetter 2020-09-29 20:29 ` Linus Walleij 2020-09-29 20:29 ` Linus Walleij 2020-09-29 21:37 ` Peter Collingbourne 2020-09-29 21:37 ` Peter Collingbourne 2020-09-30 9:40 ` Daniel Vetter 2020-09-30 9:40 ` Daniel Vetter 2020-09-29 20:51 ` Peter Collingbourne 2020-09-29 20:51 ` Peter Collingbourne 2020-09-30 9:43 ` Daniel Vetter 2020-09-30 9:43 ` Daniel Vetter 2020-10-12 12:50 ` Neil Armstrong 2020-10-12 12:50 ` Neil Armstrong 2021-12-05 13:34 ` Linus Walleij [this message] 2021-12-05 13:34 ` Linus Walleij
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=CACRpkdYGG-6OoWD29Jqo9dnhfWc2KMxpbCdRRYRmpuciiVrLAw@mail.gmail.com \ --to=linus.walleij@linaro.org \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=emma@anholt.net \ --cc=john.stultz@linaro.org \ --cc=kevin.brodsky@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux@armlinux.org.uk \ --cc=narmstrong@baylibre.com \ --cc=pcc@google.com \ --cc=sean@poorly.run \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.