From owner-acpi-jp@jp.FreeBSD.org Wed Dec 11 17:33:07 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gBB8X7b07733;
	Wed, 11 Dec 2002 17:33:07 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gBB8X6207700
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Dec 2002 17:33:06 +0900 (JST)
	(envelope-from takawata@axe-inc.co.jp)
Received: from axe-inc.co.jp ([192.47.224.47])
	by axe-inc.co.jp (8.9.3+3.2W/3.7W) with ESMTP id RAA13064;
	Wed, 11 Dec 2002 17:33:03 +0900 (JST)
Message-Id: <200212110833.RAA13064@axe-inc.co.jp>
To: obrien@freebsd.org
Cc: acpi-jp@jp.FreeBSD.org, current@freebsd.org
In-reply-to: Your message of "Tue, 10 Dec 2002 12:08:42 PST."
             <20021210200842.GA94153@dragon.nuxi.com>
From: User Takawata <takawata@axe-inc.co.jp>
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 11 Dec 2002 17:33:20 +0900
X-Sequence: acpi-jp 2036
Subject: [acpi-jp 2036] 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: takawata@axe-inc.co.jp
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021210

In message <20021210200842.GA94153@dragon.nuxi.com>, "David O'Brien" wrote:
>
>I never heard an answer to this:
>
>    Did this test a "bug" fix; or should this maybe be committed into the
>    CVS repository for use by others with the same mobo I have?

This is always needed until the BIOS maker fix it and you replace
with the bug-fixed version.

>A stock 10-DEC-2002 10:00 PST kernel still does not give me a working
>floppy drive.  Should the latest ACPI import have fixed my problem?
>Should a future ACPI code drop fix this problem, or will I forever have
>to use a custom .AML with this motherboard?

 I don't think the problem will fixed in the future, because 
the problem is occured by the strict checking of byte-code validity.

> 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.
