From owner-acpi-jp@jp.FreeBSD.org Fri Oct  4 15:00:21 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g9460LI83831;
	Fri, 4 Oct 2002 15:00:21 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g9460K383824
	for <acpi-jp@jp.freebsd.org>; Fri, 4 Oct 2002 15:00:20 +0900 (JST)
	(envelope-from msmith@freebsd.org)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g9460Is09623
	for <acpi-jp@jp.freebsd.org>; Thu, 3 Oct 2002 23:00:18 -0700 (PDT)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5db8e5abf0118164e13cc@mailgate2.apple.com> for <acpi-jp@jp.freebsd.org>;
 Thu, 3 Oct 2002 23:00:18 -0700
Received: from freebsd.org (vpn-scv-x0-135.apple.com [17.219.192.135])
	by scv2.apple.com (8.11.3/8.11.3) with ESMTP id g9460HV03453
	for <acpi-jp@jp.FreeBSD.org>; Thu, 3 Oct 2002 23:00:17 -0700 (PDT)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
From: Michael Smith <msmith@freebsd.org>
To: acpi-jp@jp.FreeBSD.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <200210040248.LAA09907@axe-inc.co.jp>
Message-Id: <8F557906-D75E-11D6-9DDF-0050E4660701@freebsd.org>
X-Mailer: Apple Mail (2.546)
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Thu, 3 Oct 2002 23:00:18 -0700
X-Sequence: acpi-jp 1873
Subject: [acpi-jp 1873] Re: (FWD) 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+020902


On Thursday, October 3, 2002, at 07:57 PM, User Takawata wrote:

> In message <8714F224-D713-11D6-9DDF-0050E4660701@freebsd.org>, Michael 
> Smith wr
> ote:
>>
>> That's to be expected; ACPI is not used to enumerate PCI devices,
>> they're found by walking the PCI bus.
>
> But it is required to handle special method to power management for PCI
> devices, to route PCI-PCI bus interrupt, to use ATA bus timing setting
> informations, to handle ACPI PCI hotplug device, and etc.

Yes, however we attach things (and under ACPI it is still more or less
expected that you attach things) to the bus that enumerates them.

PCI bridges enumerate PCI devices, so PCI devices go under PCI bridges.

Stuff that's enumerated by ACPI ends up under ACPI.

The cross-connection between PCI devices and their nodes in ACPI space
*typically* results in a shadow of the PCI-to-device relationship
courtesy of the layout of the ACPI namespace, but there's no guarantee
that this is the case and we confuse things by separating the PCI bridge
and the notional bus(ses) that it instantiates.

>> As for hanging devices enumerated by ACPI off acpi0 - I can't see any
>> real reason not to do it, as long as we think we can trust their
>> resource claims (probably safe).
>
> There are such cases that both the device driver required to know
> ACPI information and parent bus other than ISA.

Yes, but in these cases the parent bus is the enumerator.  The only
odd one out here are devices that used to be enumerated by the PnP
BIOS and which are now enumerated by ACPI.  They're notionally ISA
devices, so the dispute is simply whether we should "know" this and
push them over to an ISA bus, or just hang them off ACPI and make
the ACPI device behave like an ISA bus.

  = Mike

