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 31122] Cannot control backlight intensity on Powerbook
Date: Fri, 05 Aug 2016 16:37:34 +0000	[thread overview]
Message-ID: <bug-31122-8800-YNthPCKXEd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-31122-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #11 from A. Chaud <nvbugz-ZdXa/xnzD07wXD0AkxfrAg@public.gmane.org> ---
nvagetbios wasn't able to extract the bios.  From what I gathered after
searching, openfirmware handles vbios differently (ie: no checksums, smaller
vbios, etc).  I found a nv34 openfirmware bios someone else dumped and nvbios
is unable to decode the GPIO section.

However, if the aim is ensuring the device has a backlight, I believe it's
already done.  In nouveau_backlight_init, it first checks to ensure there's a
display on either LVDS or eDP.  Can we not reasonably assume that if the gpu
has a LVDS or eDP panel attached that it also has a backlight?  My init
function is a slightly altered version of the existing nv40_backlight_init
function which doesn't have a backlight check either.

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

[-- Attachment #1.2: Type: text/html, Size: 1671 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:[~2016-08-05 16:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  3:07 [Bug 31122] New: Cannot control backlight intensity on Powerbook bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-31122-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-08-30  0:23   ` [Bug 31122] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31 19:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-11-25  2:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 19:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31  2:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-25 19:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05  2:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05  2:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05  2:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05  8:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05 16:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-08-05 16:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-05 18:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 10:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 14:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 17:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 19:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 19:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-09 19:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-16 14:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 11:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:24   ` 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-31122-8800-YNthPCKXEd@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.