John Sigler wrote:
Alexey Starikovskiy wrote:
Could you please open bug at bugzilla.kernel.org and put all these
files there?
http://bugzilla.kernel.org/show_bug.cgi?id=9148
Writing 15361 (i.e. 0x3C01) to ACPI_REGISTER_PM1A_CONTROL appears to
hang my system in acpi_os_write_port(). What
On Tue, 16 Oct 2007, John Sigler wrote:
John Sigler wrote:
Alexey Starikovskiy wrote:
Could you please open bug at bugzilla.kernel.org and put all these
files there?
http://bugzilla.kernel.org/show_bug.cgi?id=9148
Writing 15361 (i.e. 0x3C01) to ACPI_REGISTER_PM1A_CONTROL appears to
Hi,
after upgrading to Fedora 8 which brought kernel 2.6.23 with it I can no longer
use the brightness buttons (Fn+F6/F7) on my above mentioned laptop. Pressing
them generates F6 and F7 key events instead of ACPI events. This used to work
fine in Fedora 7's 2.6.22.9 kernel.
Is there anything I
On 10/16/2007 08:49 AM, Danny Baumann wrote:
Hi,
after upgrading to Fedora 8 which brought kernel 2.6.23 with it I can no
longer
use the brightness buttons (Fn+F6/F7) on my above mentioned laptop. Pressing
them generates F6 and F7 key events instead of ACPI events. This used to work
fine
On Mon, 2007-10-15 at 17:48 +0100, Matthew Garrett wrote:
Why not just call acpi_get_pyhsical_device() on the appropriate handle
and look at the struct device you get back? Remember to put_device() it
once you're done.
Yep, works great. I should have asked earlier for such a thing...
Len
On Tue, 2007-10-16 at 16:39 +0200, Thomas Renninger wrote:
On Mon, 2007-10-15 at 17:48 +0100, Matthew Garrett wrote:
Why not just call acpi_get_pyhsical_device() on the appropriate handle
and look at the struct device you get back?
Remember to put_device() it once you're done.
First read,
On Tue, Oct 16, 2007 at 04:39:01PM +0200, Thomas Renninger wrote:
+ /*
+ * Check whether we have really a graphics device physically
+ * in the slot and registered at the system.
+ */
+ dev = acpi_get_physical_device(device-handle);
+ if (!dev) {
+
Hi,
after upgrading to Fedora 8 which brought kernel 2.6.23 with it I can no
longer
use the brightness buttons (Fn+F6/F7) on my above mentioned laptop. Pressing
them generates F6 and F7 key events instead of ACPI events. This used to
work
fine in Fedora 7's 2.6.22.9 kernel.
Is
Hi,
Len, this should be a rather safe and obvious one. Can you apply it,
pls.
Without this one, one should get NULL pointer when cap.BQC is not set as
device-brightness should not be allocated then.
Christian: This should fix up the wrong initial 0 entry for the current
brightness you saw.
John Sigler wrote:
+===+
| Soft-Off by PWR-BTTN |
|---|
| Instant-Off . [v]|
| Delay 4 Sec. . [ ]|
|
Hello!
I've got a new notebook and kernel 2.6.23 complains, I should send the
DSDT to the developers. It would be nice to see an eMail-address there
- I hope this mail gets to the right persons...
The notebook is a ASUS S37E barebone with a Santa Rosa-chipset.
You can download the DSDT and
On Tue, Oct 16, 2007 at 05:41:58PM +0200, Thomas Renninger wrote:
Len, this should be a rather safe and obvious one. Can you apply it,
pls.
Without this one, one should get NULL pointer when cap.BQC is not set as
device-brightness should not be allocated then.
Christian: This should fix
On Mon, Oct 15, 2007 at 06:33:15PM +0200, Thomas Renninger wrote:
Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it
I think it's ok. dmesg says:
ACPI: Video device VID not physically connected, ignoring
input: Video Bus as /devices/virtual/input/input11
ACPI: Video
Hi,
Christian Birchinger [EMAIL PROTECTED] wrote:
On Mon, Oct 15, 2007 at 06:33:15PM +0200, Thomas Renninger wrote:
Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore
it
I think it's ok. dmesg says:
ACPI: Video device VID not physically connected, ignoring
acpi_leave_sleep_state() should have correct list of wake and
runtime GPEs, which is available only after disable_wakeup_device()
is called.
Signed-off-by: Alexey Starikovskiy [EMAIL PROTECTED]
---
drivers/acpi/sleep/main.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff
On Tuesday, 16 October 2007 20:55, Alexey Starikovskiy wrote:
acpi_leave_sleep_state() should have correct list of wake and
runtime GPEs, which is available only after disable_wakeup_device()
is called.
Signed-off-by: Alexey Starikovskiy [EMAIL PROTECTED]
---
Ackedy-by: Rafael J. Wysocki
On Mon, Oct 15, 2007 at 10:40:02PM +0200, Rafael J. Wysocki wrote:
On Monday, 15 October 2007 18:09, Mark Gross wrote:
On Fri, Oct 12, 2007 at 11:32:40PM +0200, Rafael J. Wysocki wrote:
On Friday, 12 October 2007 06:31, Andrew Morton wrote:
On Tuesday, 16 October 2007 21:58, Mark Gross wrote:
On Mon, Oct 15, 2007 at 10:40:02PM +0200, Rafael J. Wysocki wrote:
On Monday, 15 October 2007 18:09, Mark Gross wrote:
On Fri, Oct 12, 2007 at 11:32:40PM +0200, Rafael J. Wysocki wrote:
On Friday, 12 October 2007 06:31, Andrew Morton
On 10/15/2007 12:32 PM, Andi Kleen wrote:
On Monday 15 October 2007 18:30:13 Chuck Ebbert wrote:
On 10/12/2007 03:04 AM, Zhao Yakui wrote:
Hi, All
The BIOS of some systems using NVIDIA chipset gives the uncorrect
timer override connection, which will cause that I/O APIC and timer
can't
On Tuesday 16 October 2007 23:07:29 Chuck Ebbert wrote:
Do I need something more than early-quirks-unification and nvidia-timer-quirk?
Because those two don't fix anything; I have to manually force
acpi_use_timer_override to get things to work right. The RFC patch seems to
be doing the right
On 10/16/2007 05:51 PM, Andi Kleen wrote:
On Tuesday 16 October 2007 23:07:29 Chuck Ebbert wrote:
Do I need something more than early-quirks-unification and
nvidia-timer-quirk?
Because those two don't fix anything; I have to manually force
acpi_use_timer_override to get things to work
On Tuesday 16 October 2007 23:57:25 Chuck Ebbert wrote:
On 10/16/2007 05:51 PM, Andi Kleen wrote:
On Tuesday 16 October 2007 23:07:29 Chuck Ebbert wrote:
Do I need something more than early-quirks-unification and
nvidia-timer-quirk?
Because those two don't fix anything; I have to
On Tue, Oct 16, 2007 at 10:28:13PM +0200, Rafael J. Wysocki wrote:
On Tuesday, 16 October 2007 21:58, Mark Gross wrote:
On Mon, Oct 15, 2007 at 10:40:02PM +0200, Rafael J. Wysocki wrote:
On Monday, 15 October 2007 18:09, Mark Gross wrote:
On Fri, Oct 12, 2007 at 11:32:40PM +0200, Rafael
On 14/05/2007, Stefan Seyfried [EMAIL PROTECTED] wrote:
On Fri, May 11, 2007 at 03:51:38PM -0700, Linus Torvalds wrote:
On Fri, 11 May 2007, Rafael J. Wysocki wrote:
Just to clarify, the change in question isn't new. It was introduced by
the
commit
On 12/05/2007, Linus Torvalds [EMAIL PROTECTED] wrote:
On Fri, 11 May 2007, Rafael J. Wysocki wrote:
We're working on fixing the breakage, but currently it's difficult, because
none of my testboxes has problems with the 'platform' hibernation and I
cannot reproduce the reported issues.
On Wed, 17 Oct 2007, Qi Yong wrote:
The key point is fall back to shutdown _only_ if !ops, otherwise
don't touch hibernation_mode. And that solves my problem.
Please, when resurrecting a five-month-old discussion, give more of the
old context.
I don't know about anybody else, but I get
On Wed, 17 Oct 2007 04:39:30 +0200 Maxim Levitsky [EMAIL PROTECTED] wrote:
A while ago I asked on LKML about the problem of loosing all wake device
capabilities, after a suspend to disk
(eg: I can't wake the system from keyboard if I suspend to disk and then to
ram)
I was provided with
On Wed, Oct 17, 2007 at 10:46:12AM +0800, Qi Yong wrote:
On 12/05/2007, Linus Torvalds [EMAIL PROTECTED] wrote:
On Fri, 11 May 2007, Rafael J. Wysocki wrote:
We're working on fixing the breakage, but currently it's difficult,
because
none of my testboxes has problems with the
On Wednesday 17 October 2007 05:48:02 Andrew Morton wrote:
On Wed, 17 Oct 2007 04:39:30 +0200 Maxim Levitsky [EMAIL PROTECTED] wrote:
A while ago I asked on LKML about the problem of loosing all wake device
capabilities, after a suspend to disk
(eg: I can't wake the system from keyboard
29 matches
Mail list logo
