LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
tony.luck@intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, "Accardi,
Kristen" <kristen.c.accardi@intel.com>
Subject: Re: [GIT PATCH] ACPI patches for 2.6.21
Date: Fri, 9 Feb 2007 23:27:03 -0500 [thread overview]
Message-ID: <200702092327.04237.lenb@kernel.org> (raw)
In-Reply-To: <20070209230928.GD3949@ucw.cz>
On Friday 09 February 2007 18:09, Pavel Machek wrote:
> Hi!
>
> > Per your request, and the request of the distros, we've changed
> > how ACPICA Core releases are integrated into Linux so that each
> > upstream (CVS) check-in appears as a single git commit.
> > While this process is not yet perfect, it should be vastly better
> > than previous "code drops" in allowing git bisect to work,
> > and allowing distros to cherry-pick individual fixes.
> >
> > The "bay" driver is new (and marked EXPERIMENTAL) -- adding initial
> > hot-plug support for ACPI controlled drive bays such as the
> > IBM ultrabay or the Dell Module Bay.
>
> Could you describe userland interface it uses? /proc? Will it be
> usable for bays on notebooks not using acpi?
No, Not until somebody finds one and writes code to support it.
> > The "asus-laptop" driver is also new. Consistent with msi-laptop,
> > it uses ACPI in platform-specific ways, but strives to avoid
> > exposing ACPI-specific implementation details to the user.
> > asus-laptop is mutually exclusive with asus_acpi, which it will
> > replace over time.
>
> Not including another /proc/acpi/ibm -like nightmare, is it?
No. See discussion on linux-acpi.
I've prohibited new files under /proc/acpi/ for quite some time now.
> > the old /proc/acpi/ interfaces with cleaner interfaces in sysfs --
> > non-ACPI-specific generic ones whenever possible. This effort
> > is not complete, but it has been in -mm for a long time and
> > I believe that it is time to push it upstream to benefit
> > from broader exposure and testing.
>
> Does it still include completely broken alarm interface? Can't find it
> in changelogs, so hopefully not.
No. See discussion on linux-acpi.
David Brownell's RTC driver will provide the new RTC interface in sysfs.
/proc/acpi/alarm will go away when the rest of /proc/acpi goes away.
thanks,
-Len
next prev parent reply other threads:[~2007-02-10 4:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 19:18 Len Brown
2007-02-09 23:09 ` Pavel Machek
2007-02-10 1:24 ` Kristen Carlson Accardi
2007-02-10 3:34 ` Matthew Garrett
2007-02-10 1:58 ` Henrique de Moraes Holschuh
2007-02-11 19:35 ` Pavel Machek
2007-02-11 19:48 ` Henrique de Moraes Holschuh
2007-02-14 12:58 ` Pavel Machek
2007-02-10 4:27 ` Len Brown [this message]
2007-02-22 15:53 ` Pavel Machek
2007-02-26 9:25 ` Zhang Rui
2007-02-10 8:27 ` Ismail Dönmez
2007-02-10 12:07 ` Holger Macht
2007-02-10 15:52 ` Ismail Dönmez
2007-02-10 16:39 ` Henrique de Moraes Holschuh
2007-02-10 17:02 ` Ismail Dönmez
2007-02-10 16:59 ` Ismail Dönmez
2007-02-07 21:55 Al Boldi
2007-02-08 3:51 ` Len Brown
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=200702092327.04237.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@osdl.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
--subject='Re: [GIT PATCH] ACPI patches for 2.6.21' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).