public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: Linux-acpi@vger.kernel.org
Subject: Re: new Linux/ACPI home page
Date: Thu, 25 Oct 2007 16:29:18 -0400	[thread overview]
Message-ID: <200710251629.19006.lenb@kernel.org> (raw)
In-Reply-To: <4720ED77.6090109@gmail.com>

On Thursday 25 October 2007 15:24, Alexey Starikovskiy wrote:
> Len Brown wrote:

> > and going away), and the DSDT databse -- which I believe
> > is also somewhat of a historical artifact.

> DSDT database or better acpidump.out database might be very useful,
> if could be searched for particular feature -- absence of EC, use of SBS, etc.

True.

I don't like the original DSDT database -- it was from an era
when people thought that it was a good idea to hack a DSDT
to workaround Linux failures and share the hacked DSDT
with others.  That was a bad strategy and it should be abandoned.
DSDT hacking is for Linux debugging only -- Linux should
always be made to work with an un-modified DSDT.

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.

thanks,
-Len

  reply	other threads:[~2007-10-25 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 19:07 new Linux/ACPI home page Len Brown
2007-10-25 19:24 ` Alexey Starikovskiy
2007-10-25 20:29   ` Len Brown [this message]
2007-10-25 19:49     ` Peter Clifton
2007-10-25 21:23     ` Rafael J. Wysocki
2007-10-28 11:17       ` Pavel Machek

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=200710251629.19006.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=Linux-acpi@vger.kernel.org \
    --cc=aystarik@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox