dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105051] Radeon sets max_brightness to -1, breaking GNOME backlight control on Macbook Pro mid-2015 11,5
Date: Mon, 28 Sep 2015 15:53:46 +0000	[thread overview]
Message-ID: <bug-105051-2300-y18fR4MooT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-105051-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=105051

Robert Abraham <robert.abraham86@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robert.abraham86@googlemail
                   |                            |.com

--- Comment #2 from Robert Abraham <robert.abraham86@googlemail.com> ---
I have a similar problem. gmux_backlight/max_brightness is set to -1.
But i also have a radeon_bl entry in /sys/class/backlight which has the correct
values.
But no matter which value i echo into /sys/class/backlight/radeon_bl/brightness
i am on max brightness, except i echo 0. in this case the backlight turns off.

so i can only choose between backlight off or on max brightness.
it works perfectly fine on 4.0.x kernel though.

i will happily provide any information you need.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-09-28 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26 21:01 [Bug 105051] New: Radeon sets max_brightness to -1, breaking GNOME backlight control on Macbook Pro mid-2015 11,5 bugzilla-daemon
2015-09-28 15:07 ` [Bug 105051] " bugzilla-daemon
2015-09-28 15:53 ` bugzilla-daemon [this message]
2015-09-28 22:32 ` bugzilla-daemon
2015-09-29  1:15 ` bugzilla-daemon
2015-09-29  1:17 ` bugzilla-daemon
2015-09-29 10:42 ` bugzilla-daemon
2015-09-29 15:52 ` bugzilla-daemon
2015-09-30  2:57 ` bugzilla-daemon
2015-09-30 19:56 ` bugzilla-daemon
2015-10-01  7:42 ` bugzilla-daemon
2015-10-01 21:04 ` bugzilla-daemon
2015-10-01 21:13 ` bugzilla-daemon
2015-10-08 14:46 ` bugzilla-daemon
2015-10-08 15:14 ` bugzilla-daemon
2015-10-15  4:47 ` bugzilla-daemon
2015-10-22  9:37 ` bugzilla-daemon
2015-10-22  9:39 ` bugzilla-daemon

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-105051-2300-y18fR4MooT@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox