From: andrej.gelenberg-KJIyc1CJxjQ@public.gmane.org
To: Corentin Chary <corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux acpi <linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Alan Jenkins
<alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>,
Matthew Garrett <mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: eeepc-laptop: bugreport
Date: Thu, 26 Nov 2009 17:45:25 +0100 [thread overview]
Message-ID: <cone.1259253925.112628.13921.1000@eeekiste> (raw)
In-Reply-To: 71cd59b00911260703r284b5bfdn3144de4db74b7c3a@mail.gmail.com
Hi,
i know, what it is not a proper solution, but it work
for me at the moment. Pleas tell me, if i can help.
I think it is better not to let switch the rfkill
on button in the driver itself.
It is more flexible when button send only event and
userspace-tool handle it. Userspace-tool can
choose the right rfkill (or may be multiple rfkills)
(it can be runned, after wlan-driver was loaded).
As i can see, other platform-drivers provide
only rfkill device and do not bind it to
keys.
Regards,
Andrej
Corentin Chary writes:
> Hi,
> Making hotplug optional won't fix the problem,
> because this mean you need to ship a specific module for each Eeepc.
>
> We need a more generic solution, and we need to implement a driver for
> the new wmi interface.
> I'll start to work on that as soon as I can get the hardware...
> Thanks,
>
>
> --
> Corentin Chary
> http://xf.iksaif.net
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-11-26 16:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cone.1258203372.445001.1633.1000@eeekiste>
[not found] ` <71cd59b00911140641i1502e95bt81d87db848feaf0@mail.gmail.com>
[not found] ` <cone.1258211472.464906.1633.1000@eeekiste>
2009-11-15 9:39 ` eeepc-laptop: bugreport Corentin Chary
2009-11-15 11:53 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 12:37 ` Alan Jenkins
2009-11-15 16:06 ` andrej.gelenberg-KJIyc1CJxjQ
[not found] ` <4B002951.4080704@tuffmail.co.uk>
[not found] ` <cone.1258304218.643429.1671.1000@eeekiste>
2009-11-15 17:07 ` Alan Jenkins
2009-11-15 17:17 ` Corentin Chary
2009-11-15 17:32 ` andrej.gelenberg
2009-11-15 17:43 ` Alan Jenkins
2009-11-15 18:05 ` andrej.gelenberg
2009-11-15 18:31 ` Corentin Chary
2009-11-15 18:56 ` Matthew Garrett
2009-11-15 18:06 ` Matthew Garrett
2009-11-15 18:11 ` andrej.gelenberg
2009-11-15 18:15 ` Matthew Garrett
2009-11-15 18:39 ` andrej.gelenberg
2009-11-15 12:44 ` Alan Jenkins
2009-11-15 15:05 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 15:54 ` Alan Jenkins
2009-11-15 16:02 ` Matthew Garrett
2009-11-15 16:11 ` Alan Jenkins
2009-11-15 16:14 ` Matthew Garrett
2009-11-15 18:16 ` Matthew Garrett
2009-11-15 18:22 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-15 18:27 ` Matthew Garrett
2009-11-15 15:56 ` Matthew Garrett
2009-11-15 15:59 ` Alan Jenkins
2009-11-15 15:52 ` Matthew Garrett
2009-11-15 19:19 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-26 15:03 ` Corentin Chary
2009-11-26 16:45 ` andrej.gelenberg-KJIyc1CJxjQ [this message]
2009-11-26 16:48 ` Matthew Garrett
2009-11-27 11:21 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 11:27 ` Alan Jenkins
2009-11-27 12:27 ` andrej.gelenberg
2009-11-27 17:25 ` Matthew Garrett
2009-11-27 20:26 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 20:43 ` Corentin Chary
2009-11-27 20:55 ` andrej.gelenberg-KJIyc1CJxjQ
2009-11-27 21:58 ` Matthew Garrett
2009-12-07 21:23 ` Corentin Chary
2009-12-07 21:28 ` Matthew Garrett
2009-12-13 21:16 ` [PATCH] eeepc-laptop: disable pci hotplug code when all notifiers fail to load Corentin Chary
2009-12-16 10:58 ` Corentin Chary
2009-11-27 17:19 ` eeepc-laptop: bugreport Matthew Garrett
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=cone.1259253925.112628.13921.1000@eeekiste \
--to=andrej.gelenberg-kjiyc1cjxjq@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alan-jenkins-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org \
--cc=corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mjg-H+wXaHxf7aLQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox