From: Frank Binns <Frank.Binns@imgtec.com>
To: "aford173@gmail.com" <aford173@gmail.com>,
"geert@linux-m68k.org" <geert@linux-m68k.org>
Cc: "marek.vasut@mailbox.org" <marek.vasut@mailbox.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
Matt Coster <Matt.Coster@imgtec.com>,
"javierm@redhat.com" <javierm@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nm@ti.com" <nm@ti.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
Sarah Walker <Sarah.Walker@imgtec.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"mripard@kernel.org" <mripard@kernel.org>
Subject: Re: [PATCH v2] drm/imagination: DRM_POWERVR should depend on ARCH_K3
Date: Tue, 5 Mar 2024 11:58:18 +0000 [thread overview]
Message-ID: <76065296ad514898e2b8c29cd921c104b3692ae0.camel@imgtec.com> (raw)
In-Reply-To: <CAHCN7x+EnSU8qk5dBFco=0vkeknGq18qEN7vFmZs0_q83T_3+w@mail.gmail.com>
Hi Adam,
Sorry for not responding sooner. I've recently just returned from paternity
leave, so just catching up on everything.
On Thu, 2024-02-15 at 11:22 -0600, Adam Ford wrote:
> On Thu, Feb 15, 2024 at 11:10 AM Adam Ford <aford173@gmail.com> wrote:
> > On Thu, Feb 15, 2024 at 10:54 AM Geert Uytterhoeven
> > <geert@linux-m68k.org> wrote:
> > > Hi Maxime,
> > >
> > > On Thu, Feb 15, 2024 at 5:18 PM Maxime Ripard <mripard@kernel.org> wrote:
> > > > On Thu, Feb 15, 2024 at 01:50:09PM +0100, Geert Uytterhoeven wrote:
> > > > > Using the Imagination Technologies PowerVR Series 6 GPU requires a
> > > > > proprietary firmware image, which is currently only available for Texas
> > > > > Instruments K3 AM62x SoCs. Hence add a dependency on ARCH_K3, to
> > > > > prevent asking the user about this driver when configuring a kernel
> > > > > without Texas Instruments K3 Multicore SoC support.
> > > >
> > > > This wasn't making sense the first time you sent it, and now that commit
> > > > log is just plain wrong. We have firmwares for the G6110, GX6250,
> > > > GX6650, BXE-4-32, and BXS-4-64 models, which can be found on (at least)
> > > > Renesas, Mediatek, Rockchip, TI and StarFive, so across three
> > >
> > > I am so happy to be proven wrong!
> > > Yeah, GX6650 is found on e.g. R-Car H3, and GX6250 on e.g. R-Car M3-W.
> > >
> > > > architectures and 5 platforms. In two months.
> > >
> > > That sounds like great progress, thanks a lot!
> > >
> > Geert,
> >
> > > Where can I find these firmwares? Linux-firmware[1] seems to lack all
> > > but the original K3 AM62x one.
> >
> > I think PowerVR has a repo [1], but the last time I checked it, the
> > BVNC for the firmware didn't match what was necessary for the GX6250
> > on the RZ/G2M. I can't remember what the corresponding R-Car3 model
> > is. I haven't tried recently because I was told more documentation
> > for firmware porting would be delayed until everything was pushed into
> > the kernel and Mesa. Maybe there is a better repo and/or newer
> > firmware somewhere else.
> >
> I should have doubled checked the repo contents before I sent my last
> e-mail , but it appears the firmware [2] for the RZ/G2M, might be
> present now. I don't know if there are driver updates necessary. I
> checked my e-mails, but I didn't see any notification, or I would have
> tried it earlier. Either way, thank you Frank for adding it. I'll
> try to test when I have some time.
>
You may have noticed from one of Matt's emails that we now have a set of repos
(linux, linux-firmware and Mesa) in our own area on freedesktop.org GitLab:
https://gitlab.freedesktop.org/imagination/
We'll be using this as a staging area for work that isn't ready to be upstreamed
yet (including firmware binaries).
> > adam
> >
> > [1] https://gitlab.freedesktop.org/frankbinns/linux-firmware/-/tree/powervr/powervr?ref_type=heads
>
> [2] - https://gitlab.freedesktop.org/frankbinns/linux-firmware/-/commit/fecb3caebf29f37221fe0a20236e5e1415d39d0b
>
This is now the place to get the firmware for devices that aren't yet supported
upstream:
https://gitlab.freedesktop.org/imagination/linux-firmware/-/commits/powervr/?ref_type=HEADS
With the firmware for the Renesas variant of GX6250 being found in this commit:
https://gitlab.freedesktop.org/imagination/linux-firmware/-/commit/fecb3caebf29f37221fe0a20236e5e1415d39d0b
Thanks
Frank
> >
> > > Thanks again!
> > >
> > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
> > >
> > > Gr{oetje,eeting}s,
> > >
> > > Geert
> > >
> > > --
> > > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> > >
> > > In personal conversations with technical people, I call myself a hacker. But
> > > when I'm talking to journalists I just say "programmer" or something like that.
> > > -- Linus Torvalds
next prev parent reply other threads:[~2024-03-05 12:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 12:50 Geert Uytterhoeven
2024-02-15 16:17 ` Maxime Ripard
2024-02-15 16:53 ` Geert Uytterhoeven
2024-02-15 17:10 ` Adam Ford
2024-02-15 17:22 ` Adam Ford
2024-02-15 23:36 ` Adam Ford
2024-02-16 8:47 ` Biju Das
2024-02-16 9:05 ` Maxime Ripard
2024-02-16 9:13 ` Biju Das
2024-02-16 14:14 ` Maxime Ripard
2024-02-18 23:26 ` Adam Ford
2024-02-19 7:45 ` Biju Das
2024-02-19 16:38 ` Adam Ford
2024-02-19 16:53 ` Maxime Ripard
2024-02-19 17:32 ` Matt Coster
2024-02-19 9:00 ` Matt Coster
2024-02-19 20:38 ` Adam Ford
2024-02-20 9:21 ` Matt Coster
2024-02-20 11:26 ` Adam Ford
2024-02-20 11:58 ` Adam Ford
2024-02-20 11:55 ` Erico Nunes
2024-02-20 12:04 ` Adam Ford
2024-03-05 11:58 ` Frank Binns [this message]
2024-03-05 13:47 ` Adam Ford
2024-03-05 16:42 ` Frank Binns
2024-03-05 16:55 ` Biju Das
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=76065296ad514898e2b8c29cd921c104b3692ae0.camel@imgtec.com \
--to=frank.binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=Sarah.Walker@imgtec.com \
--cc=aford173@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marek.vasut@mailbox.org \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®