Skip to contentSkip to conversation

database for DSDTs @ acpi.sf.net

DISCUSSION Sebastian Henschel 1 participant 2 messages Feb 25, 2003 – Feb 26, 2003 2 messages not in the archive ACPI

lore
Share & tools
lore
#0 lore raw

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

Signature · 3 lines
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

A message that is not in the archive (sent off-list or not yet received): 3E5B4718.15266.1E8ED22F@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

hi there...

Received at 2003-02-26 / 09:32 by Russo, Richard:

Quoted 3 lines

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.

Quoted 26 lines · Sebastian Henschel
Quoted 25 lines

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
Quoted 1 line
Quoted 1 line

any more suggestions? or less?

bye,
sebastian

Signature · 3 lines
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import