From owner-acpi-jp@jp.FreeBSD.org Thu Oct  3 05:12:55 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g92KCte59182;
	Thu, 3 Oct 2002 05:12:55 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g92KCs359149
	for <acpi-jp@jp.FreeBSD.org>; Thu, 3 Oct 2002 05:12:54 +0900 (JST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 15613 invoked from network); 2 Oct 2002 20:12:53 -0000
Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63])
          (envelope-sender <jhb@FreeBSD.org>)
          by mail14.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP
          for <iwasaki@jp.FreeBSD.org>; 2 Oct 2002 20:12:53 -0000
Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1])
	by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g92KCoBv014952;
	Wed, 2 Oct 2002 16:12:51 -0400 (EDT)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.20021002161253.jhb@FreeBSD.org>
X-Mailer: XFMail 1.5.2 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <AAC65624-D631-11D6-B0AE-0050E4660701@freebsd.org>
From: John Baldwin <jhb@freebsd.org>
To: acpi-jp@jp.FreeBSD.org
Cc: obrien@freebsd.org, Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 02 Oct 2002 16:12:53 -0400
X-Sequence: acpi-jp 1867
Subject: [acpi-jp 1867] 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: jhb@FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+020902


On 02-Oct-2002 Michael Smith wrote:
> 
> On Tuesday, October 1, 2002, at 09:48 AM, John Baldwin wrote:
> 
>> On 01-Oct-2002 Mitsuru IWASAKI wrote:
>>>> Scope(\_SB_) {
>>> [snip]
>>>>     Device(PCI0) {
>>> [snip]
>>>>         Device(FDC0) {
>>>>             Name(_HID, 0x0007d041)
>>>>             Method(_STA) {
>>>
>>> This means that the fdc is connected to pci directly (path is
>>> _SB_.PCI0.FDC0), but I think our fdc(4) doesn't have PCI attachment as
>>> you know.
>>> If fdc is connected to isa actually, normally there should be a
>>> PCI-ISA bridge definition between PCI0 and FDC0.
>>> pciconf -lv output will be helpful.
>>
>> Eek, that _is_ weird.  Still, it should attach off of 'acpi' due to
>> the somewhat bogus way that we flatten all ACPI devices and hang them
>> off acpi0.
> 
> Er, no, it shouldn't.

Hmm, in his dmesg fdc0 is attaching to acpi0 and not pci0.
 
> The only devices that are "flattened" are 'special' ACPI devices, and 
> even then, only because it makes no sense to attach them anywhere else.

Eh?  In acpi_probe_children() we attach all devices, processors, thermal
zones, and power resources as direct children of acpi0.

> If anything, the fact that we insist that devices be enumerated under a 
> PCI-ISA bridge in ACPI land is 'bogus' in the eyes of the rest of the 
> world.

Well, we don't do that right now (hang ACPI-enumerated ISA devices off
of isa0).  I did notice futzing around in the 'System' app in Windows
control panel that Windows attaches ISA devices directly to ACPI but
does let PCI devices be attached to the host-PCI bridges hung off
acpi0 similar to what we do now.

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
