Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 18 Apr 2001 17:48:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 18 Apr 2001 17:48:30 -0400 Received: from fmfdns02.fm.intel.com ([132.233.247.11]:15325 "EHLO thalia.fm.intel.com") by vger.kernel.org with ESMTP id ; Wed, 18 Apr 2001 17:48:12 -0400 Message-ID: <4148FEAAD879D311AC5700A0C969E89006CDDD9D@orsmsx35.jf.intel.com> From: "Grover, Andrew" To: "'John Fremlin'" Cc: "'Simon Richter'" , "Acpi-PM (E-mail)" , "'Pavel Machek'" , Andreas Ferber , linux-kernel@vger.kernel.org Subject: RE: Let init know user wants to shutdown Date: Wed, 18 Apr 2001 14:46:16 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > From: John Fremlin [mailto:chief@bandits.org] > [...] > > > Fair enough. I don't think I would be out of line to say that our > > resources are focused on enabling full ACPI functionality for Linux, > > including a full-featured PM policy daemon. That said, I don't think > > there's anything precluding the use of another daemon (or whatever) > > from using the ACPI driver's interface. > > ACPI != PM. I don't see why ACPI details should be exposed to PM > interface at all. ACPI has by far the richest set of capabilities. It is a superset of APM. Therefore a combined APM/ACPI interface is going to look a lot like an ACPI interface. IMHO an abstracted interface at this point is overengineering. Maybe later it will make sense, though. Regards -- Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/