From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: andrej.gelenberg@udo.edu
Cc: Corentin Chary <corentin.chary@gmail.com>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: eeepc-laptop: bugreport
Date: Sun, 15 Nov 2009 17:43:54 +0000 [thread overview]
Message-ID: <4B003DDA.5020508@tuffmail.co.uk> (raw)
In-Reply-To: <cone.1258306366.446137.1656.1000@eeekiste>
andrej.gelenberg@udo.edu wrote:
> Hi,
>
> Corentin Chary writes:
>
>> Could you try to boot with acpi_osi="Linux" ?
>> This might be fixed by
>> http://git.iksaif.net/?p=acpi4asus.git;a=commitdiff;h=a57818b9177b521d418e25bf549a609d0e79cd4a;hp=cbf69cbf597b31201038ecd7630c90183543c488
>>
>
> this patch solved the problem.
>
> Regards,
> Andrej
Ok. Be aware that there may be more turmoil in future. The preferred
solution for linux ACPI is to do whatever the More Popular OS does. See
the recent rejection of a similar patch by thinkpad-acpi developers.
There may be a shiny new ACPI interface we need to write a driver for.
Looking on the bright side, a new driver can easily use different pci
hotplug code (or perhaps no hotplug code).
Regards
Alan
next prev parent reply other threads:[~2009-11-15 17:43 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 [this message]
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
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=4B003DDA.5020508@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=andrej.gelenberg@udo.edu \
--cc=corentin.chary@gmail.com \
--cc=linux-acpi@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.