From owner-acpi-jp@jp.freebsd.org  Fri Oct 13 04:54:44 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id EAA60676;
	Fri, 13 Oct 2000 04:54:44 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id EAA60671
	for <acpi-jp@jp.freebsd.org>; Fri, 13 Oct 2000 04:54:43 +0900 (JST)
	(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9CJv1h01012
	for <acpi-jp@jp.freebsd.org>; Thu, 12 Oct 2000 12:57:03 -0700 (PDT)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200010121957.e9CJv1h01012@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Thu, 12 Oct 2000 22:15:14 +0900."
             <200010121315.WAA84890@shidahara1.planet.sci.kobe-u.ac.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Oct 2000 12:57:01 -0700
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 857
Subject: [acpi-jp 857] Re: Latest ACPI megapatch update 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> >I think this is already done correctly.  I haven't checked though.  When 
> >I was writing the ACPI-PnP resource enumerator I realised that we have to 
> >change the way that PnP data is connected to ISA devices (we should save 
> >the raw data and only parse it when the device has a match).  There are 
> >other complications here as well, of course.  I need to do this soon.
> 
> Please show your dmesg of the machine with EC .
> I did not find where is going wrong. I want hint.

I don't get that far; I run across what I think is an interpreter bug 
where something tries to access the EC's space before the driver ever 
gets probed.  I do have a boot log, but it's 170MB...

> I noticed you only calls acpi_parse_resources() for those connected to 
> acpi0 at acpi_get_resource(). But where do you think bus_get_resource();
> is called from?

It should be called from bus_alloc_resource() in acpi_ec_attach().  I may 
not have this entirely right yet though; I'll look at it today now that 
the PCI stuff seems to be working OK.

> And I try to call acpi_parse_resources() directly from acpi_probe_child
> but end up with page fault in resource_list_find();

Hrm.  Thanks for the report.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


