From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Florian Fainelli <f.fainelli@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] gpu/drm/v3d: Add ARCH_BCM2835 to DRM_V3D Kconfig
Date: Wed, 18 Dec 2019 18:51:28 +0100 [thread overview]
Message-ID: <094cccef1119acc5cfa4a357faaa657e2763f949.camel@suse.de> (raw)
In-Reply-To: <f127b960-e374-ce6f-403a-6f592408f9ee@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]
Hi Florian,
On Wed, 2019-12-18 at 09:39 -0800, Florian Fainelli wrote:
> On 12/18/19 6:39 AM, Nicolas Saenz Julienne wrote:
> > Hi Peter,
> >
> > On Wed, 2019-12-18 at 08:43 +0000, Peter Robinson wrote:
> > > On arm64 the config ARCH_BCM doesn't exist so to be able to
> > > build for platforms such as the Raspberry Pi 4 we need to add
> > > ARCH_BCM2835 similar to what has been done on vc4.
> > >
> > > Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> > > ---
> >
> > v3d's upstream implementation doesn't support RPi4 for now. So I don't see
> > how
> > we could benefit from this.
>
> Right, but it should support the Pi3 running in 64-bit mode too, so
> maybe that would be a better justification to put in the commit message?
Correct me if I'm wrong, but this 'v3d' isn't the same as 'vc4_v3d'. From the
initial commit for the driver[1] I understood this is only valid for bcm2711.
Regards,
Nicolas
[1] https://lore.kernel.org/lkml/20180430181058.30181-3-eric@anholt.net/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-18 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 8:43 [PATCH] gpu/drm/v3d: Add ARCH_BCM2835 to DRM_V3D Kconfig Peter Robinson
2019-12-18 14:39 ` Nicolas Saenz Julienne
2019-12-18 17:39 ` Florian Fainelli
2019-12-18 17:51 ` Nicolas Saenz Julienne [this message]
2020-03-05 6:27 ` 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=094cccef1119acc5cfa4a357faaa657e2763f949.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pbrobinson@gmail.com \
/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