From owner-acpi-jp@jp.FreeBSD.org Fri Oct  4 06:03:21 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g93L3Lv76023;
	Fri, 4 Oct 2002 06:03: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 g93L3I376017;
	Fri, 4 Oct 2002 06:03:19 +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 g93L3Fs00011;
	Thu, 3 Oct 2002 14:03:15 -0700 (PDT)
Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5db6f9fe40118164e13cc@mailgate2.apple.com>;
 Thu, 3 Oct 2002 14:03:15 -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 g93L3DV11951;
	Thu, 3 Oct 2002 14:03:13 -0700 (PDT)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: obrien@freebsd.org, Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
To: acpi-jp@jp.FreeBSD.org
From: Michael Smith <msmith@freebsd.org>
In-Reply-To: <XFMail.20021002161253.jhb@FreeBSD.org>
Message-Id: <8714F224-D713-11D6-9DDF-0050E4660701@freebsd.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Thu, 3 Oct 2002 14:03:12 -0700
X-Sequence: acpi-jp 1869
Subject: [acpi-jp 1869] 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 Wednesday, October 2, 2002, at 01:12 PM, John Baldwin wrote:

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

Those are all 'special' ACPI devices.

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

That's to be expected; ACPI is not used to enumerate PCI devices, 
they're
found by walking the PCI bus.

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

  = Mike

