public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Scott Thompson <postfail@hushmail.com>,
	linux-pm@lists.linux-foundation.org, linux-acpi@vger.kernel.org
Subject: Re: DSDT from your system / new DSDT archive
Date: Wed, 17 Sep 2008 17:44:33 +0200	[thread overview]
Message-ID: <200809171744.34064.trenn@suse.de> (raw)
In-Reply-To: <20080917024127.GB1187@khazad-dum.debian.net>

On Wednesday 17 September 2008 04:41:27 Henrique de Moraes Holschuh wrote:
> Hi Scott!
>
> On Tue, 16 Sep 2008, Henrique de Moraes Holschuh wrote:
> > On Tue, 16 Sep 2008, Scott Thompson wrote:
> > > Since a current one doesn't seem to exist, I am attempting to put
> > > my own database together up on the
> > > internets (URL coming soon) and am looking for folks to send me the
> > > DSDT from their systems.  Gathering your system DSDT takes
> > > less than about 2 minutes by running the following:
> >
> > You also want the dmidecode output, which BTW you must sanitize to remove
> > UUIDs and serial numbers.  Otherwise, the DSDTs are a lot less useful.
>
> Come to think of it, the DSDTs are useless without the other tables in most
> systems, anyway, so you want to store the entire acpidump :-p
Exactly.
You should take dmidecode and acpidump in a specific format (provide a small
script to (show how to) gather them?).
You should also double check the info you get uploaded. On the sourceforge
list all kind of broken info was flying around (all kind of compressions
used, only aml, only asl and only hex tables, only the diffs, and more...).

Therefore IMO best is not to only provide a small script how you should gather
and upload the data, but also internally do a quick check the other way round 
whether the data sent up is valid (unzip, acpixtract -a acpidump, [ -e 
DSDT.dsl ] or similar).

I'd also only accept acpidumps or whole zips containing the dumps.
You should not provide extracted acpidumps, even worse disassmbled ones as
the code in there is protected by copyrights.
Also a disclaimer that people must only use the info for getting their
machine running for which they bought the copyrights should be stated 
somewhere.

Expect that you get a lot dumps.

You should state somewhere that people should (if they are doing a BIOS update 
anyway):
   - upload the dumps
   - upgrade the BIOS
   - again upload the dumps
Like that you get a nice history of fixups which can reveal interesting 
things...

      Thomas

PS: This work is very much appreciated. Tell me how I can help.

  reply	other threads:[~2008-09-17 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 16:55 DSDT from your system / new DSDT archive Scott Thompson
2008-09-16 22:22 ` Henrique de Moraes Holschuh
2008-09-17  2:41   ` Henrique de Moraes Holschuh
2008-09-17 15:44     ` Thomas Renninger [this message]
2008-09-17 17:29       ` Thomas Renninger
  -- strict thread matches above, loose matches on Subject: below --
2008-09-20  3:09 Scott Thompson

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=200809171744.34064.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=postfail@hushmail.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