From owner-acpi-jp@jp.FreeBSD.org Sat Oct  5 04:31:19 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g94JVJh74088;
	Sat, 5 Oct 2002 04:31:19 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from hermes.jf.intel.com (fmr05.intel.com [134.134.136.6])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g94JVG373972
	for <acpi-jp@jp.FreeBSD.org>; Sat, 5 Oct 2002 04:31:16 +0900 (JST)
	(envelope-from robert.moore@intel.com)
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id g94JTJx08504
	for <acpi-jp@jp.FreeBSD.org>; Fri, 4 Oct 2002 19:29:19 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.25 2002/09/23 20:43:13 dmccart Exp $) with SMTP id g94JSQu29636
	for <acpi-jp@jp.FreeBSD.org>; Fri, 4 Oct 2002 19:28:26 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002100412340702048
 for <acpi-jp@jp.FreeBSD.org>; Fri, 04 Oct 2002 12:34:07 -0700
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <4G4FD38S>; Fri, 4 Oct 2002 12:31:09 -0700
Message-ID: <B9ECACBD6885D5119ADC00508B68C1EA0D19B816@orsmsx107.jf.intel.com>
From: "Moore, Robert" <robert.moore@intel.com>
To: "'acpi-jp@jp.FreeBSD.org'" <acpi-jp@jp.FreeBSD.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Fri, 4 Oct 2002 12:31:08 -0700
X-Sequence: acpi-jp 1875
Subject: [acpi-jp 1875] RE: acpi-jp@jp.FreeBSD.org
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: robert.moore@intel.com
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+020902

BTW - this was one of the original reasons ACPI was invented in the first
place -- to fill the missing PnP gaps between the various buses/motherboard
devices.  And that's one of the reasons it's not often pretty.

Bob


-----Original Message-----
From: Takanori Watanabe [mailto:takawata@axe-inc.co.jp] 
Sent: Friday, October 04, 2002 12:09 PM
To: acpi-jp@jp.FreeBSD.org
Subject: [acpi-jp 1874] acpi-jp@jp.FreeBSD.org


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

It is true that ACPI namespace sometimes form odd structure, but
ACPI devices often cannot be identified without 
existing bus enumeration mechanism, especially 
other than ISA-like devices.

So it is meaningful that device tree have nearly same 
layout as ACPI namespace as far as possible.

I don't object some ISA-like devices are direct child of acpi bus.
It is  more better that ISA bus children is automatically 
child of ACPI-bus children.
