From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 75985] [NVC1] HDMI audio device only visible after rescan Date: Sat, 14 Oct 2017 19:36:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1534085672==" 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 --===============1534085672== Content-Type: multipart/alternative; boundary="15080097851.143B.17034"; charset="UTF-8" --15080097851.143B.17034 Date: Sat, 14 Oct 2017 19:36:25 +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=3D75985 --- Comment #17 from Maik Freudenberg --- (In reply to Ilia Mirkin from comment #16) > So an interesting thought here is that GRUB also supports the setpci > command Really smart thinking but users trying it had no success. Register always returning value 0xFFFFFFFF. Which would normally(?) mean, no device there. Which led me to dig a bit into setpci and it seems to me that without the kernel and its mmio, setpci is only able to work on the standard 256 pci registers but not the extended config space. So out of luck there? --=20 You are receiving this mail because: You are the assignee for the bug.= --15080097851.143B.17034 Date: Sat, 14 Oct 2017 19:36:25 +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 # 17 on bug 75985<= /a> from = Maik Freudenberg 
(In reply to Ilia Mirkin from comment #16)
> So an interesting thought here is that GRUB also=
 supports the setpci
> command
Really smart thinking but users trying it had no success. Register always
returning value 0xFFFFFFFF. Which would normally(?) mean, no device there.
Which led me to dig a bit into setpci and it seems to me that without the
kernel and its mmio, setpci is only able to work on the standard 256 pci
registers but not the extended config space. So out of luck there?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15080097851.143B.17034-- --===============1534085672== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============1534085672==--