From: Linus Walleij <linus.walleij@linaro.org>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111
Date: Fri, 24 Mar 2017 09:08:33 +0100 [thread overview]
Message-ID: <CACRpkdZVA74Lxp2=704xd2-UcHiFPay7Y_NjR_j3uRx+hM1Jqw@mail.gmail.com> (raw)
In-Reply-To: <20170323233107.GB7909@n2100.armlinux.org.uk>
On Fri, Mar 24, 2017 at 12:31 AM, Russell King - ARM Linux
<linux@armlinux.org.uk> wrote:
> On Thu, Mar 23, 2017 at 10:54:53PM +0100, Linus Walleij wrote:
>> Hm, I certainly want it... but it would be unreasonable of me to expect
>> Eric to cold-code a big upfront design for systems he can't even test
>> this on.
>>
>> What I would request would rather be: please do not put in any
>> immediate roadblocks and keep it in the back of your head that I will
>> maybe come in and add support for the PL110 systems once this
>> works. (Of course that would be with the aim to deprecate and
>> delete the old fbdev driver in favor of this one.)
>
> I'm only suggesting that it doesn't match the PL110 hardware as long as
> it doesn't support the PL110...
Of course. Let's proceed like this.
Yours,
Linus Walleij
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-24 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 22:47 [PATCH 0/2] ARM CLCD DRM driver Eric Anholt
2017-03-17 22:47 ` [PATCH 1/2] video: ARM CLCD: Move registers to a separate header Eric Anholt
2017-03-17 22:47 ` [PATCH 2/2] drm/pl111: Initial drm/kms driver for pl111 Eric Anholt
2017-03-17 23:09 ` Russell King - ARM Linux
2017-03-18 0:45 ` Eric Anholt
2017-03-23 21:54 ` Linus Walleij
2017-03-23 23:31 ` Russell King - ARM Linux
2017-03-24 8:08 ` Linus Walleij [this message]
2017-03-20 8:34 ` Daniel Vetter
2017-03-20 18:23 ` Eric Anholt
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='CACRpkdZVA74Lxp2=704xd2-UcHiFPay7Y_NjR_j3uRx+hM1Jqw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).