database for DSDTs @ acpi.sf.net

database for DSDTs @ acpi.sf.net

[Sebastian Henschel]

[-- 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 --]

Re: database for DSDTs @ acpi.sf.net

[Sebastian Henschel]

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

hi there...

Received at 2003-02-26 / 09:32 by Russo, Richard:
> In addition to those, it may be useful to have a configuration 
> field... for some machines, the dsdt varies with how much ram and 
> stuff is plugged in.

sorry, i forgot to mention a field which is currently called "features"
where you can put all the features which are not embraced by the list below.
did you mean something like that with "configuration"?

another thing to mention is perhaps the "supersede"-relation between two
DSDTs which you can also define with that application.

> On 25 Feb 2003 at 9:56, Sebastian Henschel wrote:
> 
> > 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?

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

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