From owner-freebsd-mobile Thu Jan 4 23:19:38 2001 From owner-freebsd-mobile@FreeBSD.ORG Thu Jan 4 23:19:37 2001 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id B9BDD37B400 for ; Thu, 4 Jan 2001 23:19:21 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f057VEt03651; Thu, 4 Jan 2001 23:31:14 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050731.f057VEt03651@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Samuel Tardieu Cc: freebsd-mobile@freebsd.org Subject: Re: FreeBSD and ACPI: what can be done? In-reply-to: Your message of "Thu, 04 Jan 2001 15:38:08 +0100." <2001-01-04-15-38-08+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 23:31:14 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This may be a dumb remark, but I currently fail to see how ACPI can be > used in FreeBSD. Should AML code be uploaded into devices before being used? > Where to find such code? Is there default versions? How do we choose power > options? I would recommend a careful reading of the ACPI spec (and perhaps some of the supporting materials available from various sources) to gain a fundamental understanding of ACPI. The questions you're asking indicate that explaining how ACPI is likely to be used in FreeBSD would involve covering a lot of material that is presented better elsewhere already. Regards, -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message