From: Carlos Alberto Lopez Perez <clopez@igalia.com>
To: Corentin Chary <corentincj@iksaif.net>
Cc: AceLan Kao <acelan.kao@canonical.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: asus-wmi.ko should be loaded before video.ko
Date: Wed, 08 Aug 2012 22:17:33 +0200 [thread overview]
Message-ID: <5022C95D.6090200@igalia.com> (raw)
In-Reply-To: <CAHR064i0VUp5djWdoKLpk9H32w81ULwQFeM3hrzTsehF6ou20A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On 08/08/12 11:34, Corentin Chary wrote:
>> The problem is that the /sys/class/backlight/acpi_video0 directory still exists
>> > and the gnome-settings-daemon will choose acpi_video0 for the
>> > brightness functions
> Are you sure acpi_video_unregister() was called in this case ? can you
> add some traces to video.c to see what happened and why
> backlight_device_unregister() wasn't called ?
>
>> > But, if asus-wmi is loaded before video, then video won't call
>> > backlight_device_register(),
>> > since the flag is already be set.
> Honestly, I don't know if there is a way to do that, and asus-wmi
> should be loadable and working at any time, not only on boot.
What about writing an udev rule to force using acpi_video0 for asus-wmi?
Use udevadm to get the attributes for building the rule
udevadm info --attribute-walk --path=/sys/class/backlight/acpi_video0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2012-08-08 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 9:26 asus-wmi.ko should be loaded before video.ko AceLan Kao
2012-08-07 9:32 ` Corentin Chary
2012-08-08 8:13 ` AceLan Kao
2012-08-08 9:34 ` Corentin Chary
2012-08-08 20:17 ` Carlos Alberto Lopez Perez [this message]
2012-08-09 3:29 ` AceLan Kao
2012-08-09 7:15 ` Corentin Chary
2012-08-09 7:39 ` AceLan Kao
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=5022C95D.6090200@igalia.com \
--to=clopez@igalia.com \
--cc=acelan.kao@canonical.com \
--cc=corentincj@iksaif.net \
--cc=platform-driver-x86@vger.kernel.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.