From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: new Linux/ACPI home page Date: Sun, 28 Oct 2007 12:17:16 +0100 Message-ID: <20071028111716.GF14485@elf.ucw.cz> References: <200710251507.56335.lenb@kernel.org> <4720ED77.6090109@gmail.com> <200710251629.19006.lenb@kernel.org> <200710252323.45234.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:38135 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751390AbXJ1LRH (ORCPT ); Sun, 28 Oct 2007 07:17:07 -0400 Content-Disposition: inline In-Reply-To: <200710252323.45234.rjw@sisk.pl> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Len Brown , Alexey Starikovskiy , Linux-acpi@vger.kernel.org Hi! > > yes, acpidump would be more useful than just the DSDT -- > > as we get all kinds of issues with all the tables. > > > > One problem is that shipping around BIOS images, particularly > > modified ones, is sort of a touchy area. This is the code > > of the manufacturer, who may or may not be happy that the > > community is hacking their code. If any of those manufactureres > > got mad at Intel for mucking with their BIOS code, > > that would be a bad day for we Intel employees. > > > > lesswatts.org is hosted by Intel. So we'd need to > > sort though this issue before adding an acpidump database. > > Well, we have suspend.sf.net and the acpidump database can safely be put in > there, I think. ;-) Agreed. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html