From owner-acpi-jp@jp.freebsd.org  Sun Nov  4 05:05:31 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id FAA02600;
	Sun, 4 Nov 2001 05:05:31 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id FAA02595
	for <acpi-jp@jp.freebsd.org>; Sun, 4 Nov 2001 05:05:30 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.6/8.11.3) with ESMTP id fA3K68V01427
	for <acpi-jp@jp.freebsd.org>; Sat, 3 Nov 2001 12:06:08 -0800 (PST)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200111032006.fA3K68V01427@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Sat, 03 Nov 2001 14:27:30 +0100."
             <20011103142729.A2617@webcom.it> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 03 Nov 2001 12:06:08 -0800
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1430
Subject: [acpi-jp 1430] Re: DSDT Override 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> > I think DSDT overriding is very important for our further development
> > and debugging and improvement of ACPI CA code.  I really want to
> > support it...
> 
> By the way: do you think it would be a good idea to create a database for
> "hacked" DSDT files for different machines? While I do agree that vendors
> should be fixing bugs, this is not going to happen for discontinued or old
> machines.
> It would be nice to eventually create a port...
> 
> If you agree and nobody else volunteers, I'd be willing to maintain this.

I think that an automated mechanism for patching AML would be good; keep 
a set of diffs against the acpidump output and a small tool that dumps 
the AML, patches it, then compiles it back into a DSDT image.

For each patch, keep an md5 digest of the dump(s) that it can be applied 
to.  Then you can automate the process, like a port, without distributing 
the actual ASL.  I visualise something like this:

# acpi_patcher
Fetching DSDT table... success.
Table matches "IBM ThinkPad 770Z BIOS 1.69a"
Patching table... success.
Compiling table... success.
Install new DSDT table in /boot/acpi_table.dsdt [Yn]? Y
Installing table... success.

# acpi_patcher
Fetching DSDT table... success.
Table does not match any known systems, trying patches...
Possible matches:
  0) None of these.
  1) Dell Inspiron 8000 BIOS A12
  2) Dell Inspiron 8000 BIOS A13
  3) Compal N33 BIOS 1.09
Select: 2
Patching table... success.
Compiling table... FAILED.

etc.

Regards,
Mike

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


