On Sun, 2007-11-04 at 20:55 +0100, Erik Andrén wrote:
> The bad part is that writing to the EC using the ec_write function
> doesn't work at all. Sure it completes the operation, but when probing
> the register afterwards, no change of value is seen.
This sounds the same as my Lenovo 3000 N100. If
On Wed, 2007-08-08 at 14:37 +0800, Zhang Rui wrote:
> On Mon, 2007-07-30 at 12:47 +0100, Richard Hughes wrote:
> > On 30/07/07, Matthew Garrett <[EMAIL PROTECTED]> wrote:
> > > On Sun, Jul 29, 2007 at 12:40:16PM -0400, Luming Yu wrote:
> > > >
On Tue, 2007-07-31 at 12:42 +0200, Thomas Renninger wrote:
> Richard, could you give attached patch a try, pls.
> Also check that platform suspend mode is used. AFAIK this isn't called
> at all in suspend mode.
The attached patch works for me with a git kernel on my X60. I'm not in
the office toda
On Tue, 2007-07-31 at 11:08 +0200, Rafael J. Wysocki wrote:
> On Monday, 30 July 2007 17:33, Richard Hughes wrote:
> > On Mon, 2007-07-30 at 17:21 +0200, Thomas Renninger wrote:
> > > On Tue, 2007-07-17 at 12:15 +0100, Richard Hughes wrote:
> > > > On resume we need t
On Mon, 2007-07-30 at 17:21 +0200, Thomas Renninger wrote:
> On Tue, 2007-07-17 at 12:15 +0100, Richard Hughes wrote:
> > On resume we need to refresh the lid status as we will not get an event if
> > the lid opening was what triggered the suspend.
> > This manifests itself i
On 30/07/07, Matthew Garrett <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 29, 2007 at 12:40:16PM -0400, Luming Yu wrote:
> > switch (event) {
> > case ACPI_VIDEO_NOTIFY_SWITCH: /* User requested a switch,
> >* most likely via hotkey. */
> >
On Sun, 2007-07-29 at 23:36 +0200, Rafael J. Wysocki wrote:
> On Sunday, 29 July 2007 23:18, Adrian Bunk wrote:
> > On Sun, Jul 29, 2007 at 11:17:20PM +0200, Rafael J. Wysocki wrote:
> > > On Sunday, 29 July 2007 22:40, Adrian Bunk wrote:
> > > > On Sun, Jul 29, 2007 at 02:38:05PM +0200, Rafael J.
ed patch has been ignored two or three times now.
I've been getting about 2-3 duplicate bugs a week about this.
Please apply,
Richard.
From: Richard Hughes <[EMAIL PROTECTED]>
Date: Fri, 15 Jun 2007 15:53:11 +0100
Subject: No Subject
Message-Id: <[EMAIL PROTECTED]>
Mime-Version:
On Wed, 2007-07-18 at 17:25 +0100, Matthew Garrett wrote:
> This isn't an either/or situation. If you have a hal keymap then the
> system will still work. The question is what to do in the absence of
> hal. The kernel can either provide sane defaults (that might be wrong
> in a couple of cases) o
On Wed, 2007-07-18 at 12:02 -0400, Dmitry Torokhov wrote:
> What distributions cirrently use the new HAL facilities? I am not
> saying that we want support FC3 but what about FC6, FC7? Ubuntu,
> Debian?
Currently Fedora and RHEL 5.1 but I believe ubuntu has plans for gutsy.
Basically if you use a
On Wed, 2007-07-18 at 11:05 -0400, Dmitry Torokhov wrote:
>
> I think we should continue adding keymaps to kernel until everyone is
> using HAL's facilities to load keymaps and then stop. Does this make
> sense?
I don't think so. The whole idea of hal-info is that we can update a 14k
noarch pack
userspace gets very confused indeed.
Patch inline (and also attached) forces a check of the lid status in the
resume handler.
Signed-off-by: Richard Hughes <[EMAIL PROTECTED]>
---
diff --git a/drivers/acpi/button.c b/drivers/acpi/button.c
index cb4110b..fd3473b 100644
--- a/drivers/acpi/button
On Mon, 2007-07-16 at 19:09 +0100, Matthew Garrett wrote:
>
> That's fine, we have information that lets us distinguish between
> models.
Yes, but the consensus I seemed to get from previous mails was that the
matching quirks should be done in userspace where possible. The current
FDI thing let
On Sun, 2007-07-15 at 22:11 +0100, Matthew Garrett wrote:
> On Mon, Jul 16, 2007 at 02:34:37AM +0900, Mattia Dongili wrote:
> > + /* we emit the scancode so we can always remap the key */
> > + input_event(kp.dev, EV_MSC, MSC_SCAN, event);
>
> As I said to Henrique, I don't thi
On Mon, 2007-07-09 at 09:30 -0700, David Brownell wrote:
> What's this "power manager" component?
At the moment we're using OHM, although it's got a few rough edges, it
seems to do mostly what we need it to right now.
> This policy is easily set through sysfs. It doesn't need a new
> component t
On Thu, 2007-07-12 at 17:46 +0800, Zhang, Rui wrote:
>
> I'm not sure if the button sysfs I/F is already finished.
> We'd better make a double check. :)
We need a button sysfs interface? What's wrong with just using input?
Richard.
-
To unsubscribe from this list: send the line "unsubscribe li
On Thu, 2007-07-12 at 09:32 +0400, Alexey Starikovskiy wrote:
> >> [*] Does someone have an alternative for
> >> /proc/acpi/battery/BAT1/{state,info}?
> I'm working on it. Should have proto by the end of week.
If you are using the power_supply class (i hope you are ;-) then a HAL
from freedesktop
On Sun, 2007-07-08 at 19:44 -0700, David Brownell wrote:
> On Sunday 08 July 2007, Marcelo Tosatti wrote:
> > On Sun, Jul 08, 2007 at 01:15:40PM -0700, David Brownell wrote:
> > > On Sunday 08 July 2007, Richard Hughes wrote:
> > >
> > > That is, we may wa
On Sun, 2007-07-08 at 12:17 -0700, David Brownell wrote:
>
> I think so ... although that's unfortunately another difference
> between the legacy x86-mostly code and the newer RTC framework.
(sorry for hijacking the thread)
Is this the interface should stuff like HAL use to do:
* Suspend for 10
t is the event will
not be sent.
Signed-off-by: Richard Hughes <[EMAIL PROTECTED]>
--- Begin Message ---
On resume we need to refresh the lid status as we will not get an event if
the lid opening was what triggered the suspend.
This manifests itself in users never getting a "lid open
On Tue, 2007-06-26 at 07:03 +0200, Rolf Eike Beer wrote:
> Richard Hughes wrote:
> > On Sat, 2007-06-23 at 16:56 +0200, Rolf Eike Beer wrote:
> > > None of the above keys generated a key event. Neither does
> "Brightness
> > > down", but it still works
On Mon, 2007-06-25 at 22:49 +0200, Bartók Albert wrote:
> GMail On 16/06/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> > On Saturday 16 June 2007 13:11, Richard Hughes wrote:
> > > On Fri, 2007-06-15 at 15:53 +0100, Richard Hughes wrote:
> > > > On Fr
On Sat, 2007-06-23 at 16:56 +0200, Rolf Eike Beer wrote:
> None of the above keys generated a key event. Neither does "Brightness down",
> but it still works. "Brightness up" generates an event and works. Kpowersave
> tells me it can't do brightness switching in software (which works in
> WinXtr
On Fri, 2007-06-15 at 15:53 +0100, Richard Hughes wrote:
> On Fri, 2007-06-15 at 10:29 -0400, Dmitry Torokhov wrote:
> > On 6/15/07, Richard Hughes <[EMAIL PROTECTED]> wrote:
> > > On Fri, 2007-06-15 at 13:29 +0100, Richard Hughes wrote:
> > > > in respons
On Fri, 2007-06-15 at 10:29 -0400, Dmitry Torokhov wrote:
> On 6/15/07, Richard Hughes <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-06-15 at 13:29 +0100, Richard Hughes wrote:
> > > in response to an event, but I'm thinking in a resume hook we should
> > > pr
On Fri, 2007-06-15 at 13:29 +0100, Richard Hughes wrote:
> in response to an event, but I'm thinking in a resume hook we should
> probably do acpi_evaluate_integer(handle, "_LID", NULL, &state) and then
> send an event, just so userspace is aware of what the state
On Thu, 2007-06-14 at 19:56 +, Pavel Machek wrote:
>
> noapic/nolapic will not help with video issue. try s2ram from
> suspend.sf.net.
Also there is (unashamed plug)
http://people.freedesktop.org/~hughsient/quirk/
Richard.
-
To unsubscribe from this list: send the line "unsubscribe linux-a
Guys,
I'm getting a few bugreports where:
* user shuts lid, initiates suspend
{lid is reported down}
* user opens lid, resume completes
But I'm not getting any lid INPUT up event. This works if you don't
initiate suspend when you shut the lid (blank screen for instance) -- so
I know my hardware
On Fri, 2007-06-08 at 10:23 -0400, Dmitry Torokhov wrote:
> On 6/7/07, Richard Hughes <[EMAIL PROTECTED]> wrote:
> > On Sun, 2007-06-03 at 00:48 -0400, Dmitry Torokhov wrote:
> > >
> > >
> > > It looks like KEY_COFFE comes from 0x0c/0x19e - AL Ter
On Sun, 2007-06-03 at 00:48 -0400, Dmitry Torokhov wrote:
>
>
> It looks like KEY_COFFE comes from 0x0c/0x19e - AL Terminal
> Lock/Screensaver
> so your interpretation is indeed correct. I guess I better add an
> alias to
> input.h
What's the status of this patch? Good for merging? Do you want m
d to input.h.
>
> Iam still struggling with the purpose of the key. What would you
> extect to happen when youser presses this key? Screen gets locked?
> KEY_SCREENLOCK? KEY_SCREENSAVER?
Either of these keys would be good to add.
So yes, patch looks good, cheers for the improvements.
S
_acpi.c
+++ b/drivers/acpi/toshiba_acpi.c
@@ -27,13 +27,13 @@
* engineering the Windows drivers
* Yasushi Nagato - changes for linux kernel 2.4 -> 2.5
* Rob Miller - TV out and hotkeys help
- *
+ * Richard Hughes - emit INPUT events for hotkeys
*
* TODO
*
*/
-#define TOSHIBA_ACPI_VERSIO
On Thu, 2007-05-31 at 14:44 +0100, Richard Hughes wrote:
> Nope, impossible AFAICS. The hardware is just broken. Windows XP has an
> toshiba supplied daemon that polls, so I think we have to just bite the
> bullet.
... adding in reply in different thread...
On Thu, 2007-05-31 at 10
On Thu, 2007-05-31 at 13:53 +0100, Bastien Nocera wrote:
> On Thu, 2007-05-31 at 13:36 +0100, Richard Hughes wrote:
> > Attached patch adds a kernel thread to do polling on Toshiba hardware.
> >
> > Toshiba hardware is a little oddball, and does not provide ACPI events
&g
ch involve switching to a workqueue for the
polling, not breaking the spaces in "hotkeys_via_input" and also masking
out the fn key button up.
toshiba_acpi.c | 228 +++--
1 file changed, 206 insertions(+), 22 deletions(-)
Signed-
On Wed, 2007-05-30 at 21:53 -0300, Henrique de Moraes Holschuh wrote:
> Maybe we can add that requirement and driver changes (if any, for all
> I know most drivers might already be generating such events) for
> 2.6.23? I bet Richard would like that one a lot. Richard?
To be honest, I've got lost
inline and attached.
Signed-off-by: Richard Hughes <[EMAIL PROTECTED]>
toshiba_acpi.c | 242 +++--
1 file changed, 220 insertions(+), 22 deletions(-)
--- origin/toshiba_acpi.c 2007-05-18 09:56:03.0 +0100
+++ toshiba_acpi.c
I've bugzilla'd this before (#7860), but with no specific outcome.
I'm now in a position where I have some fairly heavy-duty testing stuff
at my disposal, including stuff like DriverStudio. Does anybody know how
I can "trace" the successful suspend and resume in Windows XP, and then
use this to wo
Sorry for the general question, but I'm pretty stuck for ideas.
My Lenovo 3000 N100 laptop has a really different bios to a IBM
Thinkpad, and the backlight brightness does not get expressed through
standard ACPI controls, nor work with the ibm_acpi EC access. Brightness
keys get (I think) routed s
On 15/03/07, Len Brown <[EMAIL PROTECTED]> wrote:
On Thursday 15 March 2007 09:13, Richard Hughes wrote:
> What about some documentation so that userspace knows what to do with
> this new framework?
What does userspace need to know in addition to what is in
Documentation/cpuidle/
On 10/03/07, Len Brown <[EMAIL PROTECTED]> wrote:
arch/i386/Kconfig |2 +
arch/x86_64/Kconfig|2 +
drivers/Makefile |1 +
drivers/cpuidle/Kconfig| 28 +++
drivers/cpuidle/Makefile |5 +
drivers/cpuidle/cpu
On Fri, 2007-01-19 at 16:06 +0800, Luming Yu wrote:
> if not, you need to sort out the broken drivers. If you need help
> please feel free to enter a bug in ACPI category at
> bugzilla.kernel.org.
Done, thanks.
http://bugzilla.kernel.org/show_bug.cgi?id=7860
Richard.
-
To unsubscribe from thi
ally don't know
where to begin to fix this, advice would be really appreciated.
Thanks,
Richard Hughes.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2007-01-04 at 13:28 -0800, Andrew Morton wrote:
> On Thu, 4 Jan 2007 22:18:30 +0100
> Mattia Dongili <[EMAIL PROTECTED]> wrote:
>
> > > The place to start (please) is the patches in -mm:
> > >
> > > 2.6-sony_acpi4.patch
> > > sony_apci-resume.patch
> > > sony_apci-resume-fix.patch
> > > a
On Wed, 2006-10-11 at 11:30 +, Pavel Machek wrote:
> Looks okay to me. It would be nice to get this in, so that we teach
> people to use generic interface, and so that we can remove crappy
> interfaces in future...
What about needing a module parameter "enable-old-interface" so by
default be o
On Tue, 2006-10-10 at 14:20 -0700, [EMAIL PROTECTED] wrote:
>
> The following patch adds ->resume method to the ACPI battery handler,
> which
> has the only aim - to check whether the battery state has changed
> during
> sleep, and if so, update the ACPI internal data structures, so that
> informa
On Tue, 2006-10-10 at 23:17 +0800, Yu Luming wrote:
> It should be mapped to KEY_BRIGHTNESSDOWN/UP (linux/input.h)
Completely agree. Then userspace (like gnome-power-manager or
powersaved) can change the brightness based on policy and user-lockdown.
Richard.
-
To unsubscribe from this list: sen
On Tue, 2006-10-10 at 22:32 +0800, Yu Luming wrote:
> >From my understanding, a cute userspace App shouldn't have this kind
> of logic:
> if (is DELL )
> invoke libsmbios
> if (is foo)
> invoke libfoo,
> if (is bar)
> invoke
On 04/10/06, Alexey Starikovskiy <[EMAIL PROTECTED]> wrote:
Please open bug at bugzilla.kernel.org against ACPI/battery and attach output
from acpidump to it.
Done: http://bugzilla.kernel.org/show_bug.cgi?id=7263 - thanks for the pointer.
Richard.
-
To unsubscribe from this list: send the lin
e.
As the author of gnome-power-manager this is a bad thing :-)
I've checked out my DSDT with iasl and there are no reported problems.
I'm also running 2.6.18 and using the latest (1.02 bios) I don't know
where or how to start debugging this so I'm asking for advice.
Thanks
On Mon, 2006-09-18 at 11:17 -0400, Dmitry Torokhov wrote:
> On 9/18/06, Richard Hughes <[EMAIL PROTECTED]> wrote:
> > On Wed, 2006-08-30 at 23:07 -0400, Dmitry Torokhov wrote:
> > > On Wednesday 30 August 2006 23:03, Len Brown wrote:
> > > > On Wednesday 30 Augu
On Wed, 2006-08-30 at 23:07 -0400, Dmitry Torokhov wrote:
> On Wednesday 30 August 2006 23:03, Len Brown wrote:
> > On Wednesday 30 August 2006 22:53, Dmitry Torokhov wrote:
> >
> > > So... do you want me to make it work with !CONFIG_INPUT or shoudl I just
> > > add a dependency on INPUT in Kconfi
On Mon, 2006-01-09 at 16:14 -0500, Dmitry Torokhov wrote:
> On 1/9/06, Richard Hughes <[EMAIL PROTECTED]> wrote:
> >
> > * All ACPI keyboard events would come through /proc/acpi/event as hkey's
> > * You could change the brightness on *any* lcdpanel by doing a
On Mon, 2006-01-09 at 02:30 +, Matthew Garrett wrote:
> On Mon, Jan 09, 2006 at 10:19:00AM +0800, Yu Luming wrote:
>
> > Re: dev_acpi:
> > The key point is AML code shouldn't be exposed in userspace. It is too ugly.
>
> It may be ugly, but it /works/. We can't predict what vendors will do in
On Mon, 2006-01-09 at 15:47 +0800, Yu Luming wrote:
> On Monday 09 January 2006 15:14, Karol Kozimor wrote:
> > Thus wrote Yu Luming:
> > > >From practical point of view, the acpi hotkey won't change for a quite
> > >
> > > long period. For example, I cannot find too much changes on acpi hotkey
On Mon, 2006-01-09 at 01:09 -0500, Dmitry Torokhov wrote:
> On Monday 09 January 2006 00:24, Matthew Garrett wrote:
> > On Mon, Jan 09, 2006 at 12:07:43AM -0500, Dmitry Torokhov wrote:
> >
> > > Why don't we create an input handler that would feed certain events
> > > from input layer to acpid via
On Mon, 2006-01-09 at 00:07 -0500, Dmitry Torokhov wrote:
> On Sunday 08 January 2006 20:14, Richard Hughes wrote:
> > On Sun, 2006-01-08 at 14:13 +, Richard Hughes wrote:
> > > On Sun, 2006-01-08 at 13:47 +, Matthew Garrett wrote:
> > > > On Sun, Jan 08, 200
On Mon, 2006-01-09 at 09:10 +0800, Yu Luming wrote:
> > 3. Use the new acpi kernel hotkeys stuff -- not that I really understand
> > the interface, nor how to use it correctly. Plus I'm not sure how much
> > of the vendor kernel modules can use this new interface, or if it's
> > suitable. It al
On Sun, 2006-01-08 at 14:13 +, Richard Hughes wrote:
> On Sun, 2006-01-08 at 13:47 +, Matthew Garrett wrote:
> > On Sun, Jan 08, 2006 at 12:58:44PM +, Richard Hughes wrote:
> >
> > > Can we not go further and define Dock/UnDock,
> > > Brightness
On Sun, 2006-01-08 at 13:47 +, Matthew Garrett wrote:
> On Sun, Jan 08, 2006 at 12:58:44PM +0000, Richard Hughes wrote:
>
> > Can we not go further and define Dock/UnDock,
> > BrightnessUp/BrightnessDown, Hibernate, etc?
>
> BrightnessUp/BrightnessDown have keycode
On Sat, 2006-01-07 at 17:24 +, Matthew Garrett wrote:
> Currently, there are three ways that a sleep hotkey may generate an
> event:
>
> 1) Exposed in DSDT as an ACPI object, generates an ACPI notification
> event (the "normal" way)
>
> 2) Uses hardware-specific ACPI driver, generates an AC
61 matches
Mail list logo
