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?
> 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?
> 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.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
