From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60659] Backlight control interface with nouveau driver for nVidia Quadro 1000m not works
Date: Wed, 31 Jul 2013 16:40:39 +0000 [thread overview]
Message-ID: <bug-60659-2300-dm68SNDzFl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60659-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60659
--- Comment #5 from Ilia Mirkin <imirkin@alum.mit.edu> ---
I think we're not understanding each other... you filed this bug because
nouveau wasn't registering a backlight interface. I pointed out why this was
and told you how to make it register one (acpi_backlight=vendor).
Then you go on to mention that booting without that, acpi_video0/brightness
doesn't control the backlight... but I thought this bug was about using nouveau
to control the backlight, not acpi_video...
What happens when you boot with that option (but not acpi_osi=Linux/etc unless
you normally boot with that)? Does the /sys/class/backlight/.../brightness
registered by nouveau let you control the backlight or not? [Note, the
Fn+whatever keys are entirely secondary to backlight control working.]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-07-31 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 6:34 [Bug 60659] New: Backlight control interface with nouveau driver for nVidia Quadro 1000m not works bugzilla-daemon
2013-07-31 7:04 ` [Bug 60659] " bugzilla-daemon
2013-07-31 15:54 ` bugzilla-daemon
2013-07-31 16:01 ` bugzilla-daemon
2013-07-31 16:13 ` bugzilla-daemon
2013-07-31 16:40 ` bugzilla-daemon [this message]
2013-07-31 20:56 ` bugzilla-daemon
2013-07-31 21:00 ` bugzilla-daemon
2013-08-06 8:41 ` bugzilla-daemon
2013-10-29 8:49 ` 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-60659-2300-dm68SNDzFl@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 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.