From: Ilia Mirkin <imirkin@alum.mit.edu>
To: Raymond Wong <raymondwong3690@gmail.com>
Cc: nouveau@lists.freedesktop.org
Subject: Re: Nouveau on a RISC-V SBC with Tesla K80? Supposed to not work or yes?
Date: Fri, 19 Apr 2024 11:25:03 -0400 [thread overview]
Message-ID: <CAKb7UvgRV-kq_LUfd-wiyQPZhZJnr7_qxzpR6WGmz2E5J65=Hg@mail.gmail.com> (raw)
In-Reply-To: <CACnaySK2RJV-1k7EsS1fGgsnBA1HE-PrzuPUdFw2JPaEGHEgMA@mail.gmail.com>
I don't think anyone was ever able to get their hands on a K80 to
confirm. It's a different ID than the GK110 (0xf0) / GK110B (0xf1). I
believe it's referred to as a GK210, but not sure if that's just a
marketing thing or if it's actually different.
You can try copying the 0xf1 entry in devinit and seeing what happens.
https://cgit.freedesktop.org/drm/drm/tree/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c#n3284
i.e. just add "case 0xf2: device->chip = &nvf1_chipset; break;"
However it does seem somewhat likely there would be additional
differences, so I wouldn't be extremely surprised if it didn't come up
without at least some extracted firmware (which we've never done for
that chipset).
Cheers,
-ilia
On Fri, Apr 19, 2024 at 11:14 AM Raymond Wong <raymondwong3690@gmail.com> wrote:
>
> NOUVEAU MESSAGE : {
> [ 47.314360] nouveau 0001:03:00.0: enabling device (0000 -> 0002)
>
> [ 47.314452] nouveau 0001:03:00.0: unknown chipset (0f22d0a1) [ 47.323897]
>
> pci 0001:02:10.0: enabling device (0000 -> 0002) [ 47.323938] nouveau 0001:04:00.0: enabling device (0000 -> 0002)
>
> [ 47.324095] nouveau 0001:04:00.0: unknown chipset (0f22d0a1)
> }
>
> CONTEXT : {
> This thing belongs to someone else, but I'm playing with it. It is a VisionFive 2 (a third one). It would seem like the PCIe implementation in there is missing something that Navi 2s and 3s want. Therefore some Polaris cards and Kepler cards are probably the best GPUs this SBC can run.
> Of course, it is two GPUs on a single PCIe 2.0 x1 lane using a riser. I see that the Tesla K80 has it's own suspiciously incomplete line in the CodeNames section. But nouveau reports unknown chipset when attempting to load drivers onto the GPUs. Maybe it doesn't have the configuration for a Tesla K80 after all?
> However, given Fishwaldo's 5.15.131 kernel is running on the SBC, I wonder if Tesla K80 support has been added somewhere, But my roommates (myself included) are combined all just too noob at googling to find it.
> }
>
> SYSTEM : {
> Board : VisionFive 2
> Kernel : 5.15.131 Fishwaldo using pine64-star64_defconfig
> Nouveau enabled using scripts/config -m CONFIG_DRM_NOUVEAU
> GPU : Tesla K80 dual GPU wanting to use nouveau drivers. One PCIe 2.0 x1 link connects both GPUs.
> OS : Slackware ARM RISC-V (Full system, 16GB installed)
> Notes : It would appear that a GTX 750 Ti worked on another VisionFive 2, as did a RX 550 on my Star64.
> }
prev parent reply other threads:[~2024-04-19 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 19:10 Nouveau on a RISC-V SBC with Tesla K80? Supposed to not work or yes? Raymond Wong
2024-04-19 15:25 ` Ilia Mirkin [this message]
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='CAKb7UvgRV-kq_LUfd-wiyQPZhZJnr7_qxzpR6WGmz2E5J65=Hg@mail.gmail.com' \
--to=imirkin@alum.mit.edu \
--cc=nouveau@lists.freedesktop.org \
--cc=raymondwong3690@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).