From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Marc Koschewski <marc@osknowledge.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: CONFIG_ACPI_PROC_EVENT disabled -> userspace not working (Was: Re: CONFIG_ACPI_PROCFS_POWER to be removed in 2.6.39)
Date: Fri, 1 Jul 2011 16:54:54 +0800 [thread overview]
Message-ID: <BANLkTimAyhUxcLCyXLKoWuv7wPhUiMh--A@mail.gmail.com> (raw)
In-Reply-To: <20110701061943.GA17184@marc.osknowledge.org>
(Cc linux-acpi@vger.kernel.org...)
On Fri, Jul 1, 2011 at 2:19 PM, Marc Koschewski <marc@osknowledge.org> wrote:
> * Américo Wang <xiyou.wangcong@gmail.com> [2011-07-01 08:55:23 +0800]:
>
> I just disabled the 3 'deprecated' within ACPI and ACPI userspace is not working
> any longer. I'm using Gentoo so I doubt my userspace is too old. acpid doesn't
> somehow listen to events when CONFIG_ACPI_PROC_EVENT is not set:
>
> "Say Y here to retain the old behaviour. Say N if your
> user-space is newer than kernel 2.6.23 (September 2007)."
>
>> On Fri, Jul 1, 2011 at 5:37 AM, Marc Koschewski <marc@osknowledge.org> wrote:
>> > Hey guys,
>> >
>> > CONFIG_ACPI_PROCFS_POWER is still there. Missed it or did you want it
>> > to reside?
>>
>> There was a patch to remove it,
>>
>> https://patchwork.kernel.org/patch/654021/
>>
>> Don't know why it is not merged.
>>
>>
>
> --
> Marc Koschewski
>
next prev parent reply other threads:[~2011-07-01 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:37 CONFIG_ACPI_PROCFS_POWER to be removed in 2.6.39 Marc Koschewski
2011-07-01 0:55 ` Américo Wang
2011-07-01 6:19 ` CONFIG_ACPI_PROC_EVENT disabled -> userspace not working (Was: Re: CONFIG_ACPI_PROCFS_POWER to be removed in 2.6.39) Marc Koschewski
2011-07-01 8:54 ` Américo Wang [this message]
2011-07-05 17:52 ` CONFIG_ACPI_PROCFS_POWER to be removed in 2.6.39 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=BANLkTimAyhUxcLCyXLKoWuv7wPhUiMh--A@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.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
all inboxes | Powered by JetHome®