All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 104156] NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) issue finding GPIO
Date: Tue, 12 Dec 2017 21:56:33 +0000	[thread overview]
Message-ID: <bug-104156-8800-ujAewjbUoW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104156-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 584 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104156

--- Comment #7 from Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Jonathan from comment #6)
> (In reply to Ilia Mirkin from comment #3)
> > IIRC I had the same issue with my G96. Should be in the vbios repo.
> 
> File has been attached. (twice by mistake)

Yeah, as far as I can tell from that, we're not doing anything wrong here. 
Your VBIOS' connector table points to a GPIO table entry that doesn't exist.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1494 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-12-12 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  8:28 [Bug 104156] New: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) issue finding GPIO bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-104156-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-12-07  8:29   ` [Bug 104156] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-07 19:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-07 19:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-11 16:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-11 16:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-12 12:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-12 21:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-12-14  6:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-104156-8800-ujAewjbUoW@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.