public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Henschel <shensche-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: database for DSDTs @ acpi.sf.net
Date: Tue, 25 Feb 2003 16:56:35 +0100	[thread overview]
Message-ID: <20030225155635.GA3899@enigma.daemon.sh> (raw)

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

hi folks...

i am currently working on a little tool which lets all of you upload
fixed or for some reason modified DSDTs to acpi.sf.net. so that there
will be a kind of central place to download and compare DSDTs.

the question now is, which information shall be stored to describe a
DSDT. these things were thought of a couple of months (or years?) ago:

manufacturer    -- Mainboard-manufacturer
name            -- Mainboard-name
boardrev        -- Board-Revision
biosrev         -- BIOS-Revision
dual            -- SMP-System: y/n
dsdtvendor      -- "Vendor"-entry DSDT
dsdtproduct     -- "Product"-entry DSDT
dsdtrev         -- "Revision"-entry DSDT
s4bios_p        -- Supports S4BIOS
s2lat           -- S2-Wakeup-Latency
s3lat           -- S3-Wakeup-Latency
dutywidth       -- number of bits Throttling-Reg.
boot_p          -- Has BOOT-Table
apic_p          -- Has APIC-Table
original_p      -- Is original table from manufacturer


any more suggestions? or less?


cheers,
 sebastian
-- 
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-02-25 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 15:56 Sebastian Henschel [this message]
     [not found] ` <3E5B4718.15266.1E8ED22F@localhost>
     [not found]   ` <3E5B4718.15266.1E8ED22F-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2003-02-26  8:38     ` database for DSDTs @ acpi.sf.net Sebastian Henschel

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=20030225155635.GA3899@enigma.daemon.sh \
    --to=shensche-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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