From owner-acpi-jp@jp.FreeBSD.org Wed Dec 11 18:21:33 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gBB9LXV59490;
	Wed, 11 Dec 2002 18:21:33 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gBB9LW259485
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Dec 2002 18:21:32 +0900 (JST)
	(envelope-from msmith@freebsd.org)
Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225])
	by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id gBB9LUw17220
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Dec 2002 01:21:31 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5f179707e6118064e13f4@mailgate1.apple.com>;
 Wed, 11 Dec 2002 01:21:07 -0800
Received: from freebsd.org (vpn-scv-x4-134.apple.com [17.219.194.134])
	by scv3.apple.com (8.11.3/8.11.3) with ESMTP id gBB9LTf16584;
	Wed, 11 Dec 2002 01:21:29 -0800 (PST)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
Cc: obrien@freebsd.org, current@freebsd.org
To: acpi-jp@jp.FreeBSD.org
From: Michael Smith <msmith@freebsd.org>
In-Reply-To: <200212110833.RAA13064@axe-inc.co.jp>
Message-Id: <EE664CB2-0CE9-11D7-9354-0050E4660701@freebsd.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.548)
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 11 Dec 2002 01:21:29 -0800
X-Sequence: acpi-jp 2037
Subject: [acpi-jp 2037] Re: no floppy drive with acpi.ko loaded
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: msmith@freebsd.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021210


On Wednesday, December 11, 2002, at 12:33 AM, User Takawata wrote:

>> If this mobo will always
>> require a custom .AML file I want to commit the one I have and start a
>> table of mobo/BIOS's and the custom .AML files we offer.
>
> You will need version information of the bytecode.

Wasn't someone already doing this?

At any rate, we are definitely going to need a list of rogue DSDTs and
something in the loader (for the installer case) which can detect them
and take appropriate action.

Booting from CD you have the luxury of having them all in place; the
rogue list and the required replacement AML will have to be copied by
the installer.

Floppy install will probably have to force you to copy the AML to a
new floppy and feed it in as part of the boot process.

  = Mike

