From: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Aaron Sowry <aaron+nv-+1tCnOwpXBmzQB+pC5nmwQ@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: nouveau exposes backlight controls in presence of ACPI
Date: Tue, 02 Nov 2010 13:58:35 +1000 [thread overview]
Message-ID: <1288670315.6477.2.camel@nisroch> (raw)
In-Reply-To: <20101029154934.GA2076-+1tCnOwpXBmzQB+pC5nmwQ@public.gmane.org>
On Fri, 2010-10-29 at 17:49 +0200, Aaron Sowry wrote:
> It seems to be de facto standard to only expose kernel-level backlight controls in the absence of ACPI, however nouveau does this regardless of whether ACPI equivalents are available or not. This will confuse userspace in some situations. Does this need patching or is there some reason for this behaviour?
Yes, it appears that you're correct here. I took a look into what is
supposed to happen, and it looks fairly trivial to implement and stop
nouveau providing nv_backlight if video.ko is already providing it.
However. There's also the platform-specific modules (thinkpad etc) that
will provide their own backlight methods if the standard ACPI mechanism
isn't available. I didn't see any immediately obvious way of knowing
whether or not they were being provided.
I'm not too certain the best way to deal with this, any ideas? :)
Ben.
>
> /Aaron
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2010-11-02 3:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 15:49 nouveau exposes backlight controls in presence of ACPI Aaron Sowry
[not found] ` <20101029154934.GA2076-+1tCnOwpXBmzQB+pC5nmwQ@public.gmane.org>
2010-11-02 3:58 ` Ben Skeggs [this message]
2010-11-02 14:51 ` Aaron Sowry
[not found] ` <20101102145153.GA4075-+1tCnOwpXBmzQB+pC5nmwQ@public.gmane.org>
2010-11-02 22:37 ` Ben Skeggs
2010-11-02 16:37 ` Calvin Walton
2010-11-02 19:28 ` Aaron Sowry
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=1288670315.6477.2.camel@nisroch \
--to=skeggsb-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aaron+nv-+1tCnOwpXBmzQB+pC5nmwQ@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.