From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 109952] nv106 nv108 confusion
Date: Mon, 11 Mar 2019 11:47:35 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0532682003=="
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Sender: "Nouveau"
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
List-Id: nouveau.vger.kernel.org
--===============0532682003==
Content-Type: multipart/alternative; boundary="15523048550.6ED1e5A.8765"
Content-Transfer-Encoding: 7bit
--15523048550.6ED1e5A.8765
Date: Mon, 11 Mar 2019 11:47:35 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D109952
--- Comment #1 from Ilia Mirkin ---
Marketing names are fungible. If nouveau says it's a NV106, then it's a NV1=
06.
If it's truly not, then the hw maker screwed up -- unlikely. Also GK208B is
something we largely invented -- they're all marketed as GK208, but the "BO=
OT0"
register has a different chip id.
You can reuse the same firmware files as nv108 for nv106 -- can just symlink
them, ought to work.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15523048550.6ED1e5A.8765
Date: Mon, 11 Mar 2019 11:47:35 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Commen=
t # 1
on bug 10995=
2
from Ilia Mirkin
Marketing names are fungible. If nouveau says it's a NV106, th=
en it's a NV106.
If it's truly not, then the hw maker screwed up -- unlikely. Also GK208B is
something we largely invented -- they're all marketed as GK208, but the &qu=
ot;BOOT0"
register has a different chip id.
You can reuse the same firmware files as nv108 for nv106 -- can just symlink
them, ought to work.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15523048550.6ED1e5A.8765--
--===============0532682003==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt
YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m
cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1
--===============0532682003==--