From owner-acpi-jp@jp.freebsd.org  Fri Sep  7 07:39:09 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id HAA48243;
	Fri, 7 Sep 2001 07:39:09 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id HAA48238
	for <acpi-jp@jp.freebsd.org>; Fri, 7 Sep 2001 07:39:07 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.6/8.11.3) with ESMTP id f86MjZo03743;
	Thu, 6 Sep 2001 15:45:35 -0700 (PDT)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200109062245.f86MjZo03743@mass.dis.org>
To: acpi-jp@jp.freebsd.org
cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, current@freebsd.org,
        msmith@mass.dis.org
In-Reply-To: Message from Mitsuru IWASAKI <iwasaki@jp.freebsd.org> 
   of "Fri, 07 Sep 2001 01:01:47 +0900." <20010907.010147.104026307.iwasaki@jp.FreeBSD.org> 
Date: Thu, 06 Sep 2001 15:45:35 -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+010328
X-Sequence: acpi-jp 1248
Subject: [acpi-jp 1248] Re: ACPI and PS/2 mouse problem 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> I personally, don't have enough time to hack the code for now (sorry),
> but I think that newly added `placeholders' code causes the problem
> for my first impression.

Yes; this is something that I'm not happy about.  It looks like these
resources are being badly abused by vendors as "hints" for allocation of
fresh resources, rather than truly reflecting the system configuration.

> 
>     for (i = 0; i < 100; i++) {
>         rid = i;
>         res = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0, ~0, 1, 0);
>         rid = i;
>         res = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0, ~0, 1, 0);
>         rid = i;
>         res = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0, 1, 0);
>     }
> 
> Mike, do you have any idea on this?

I'm not sure exactly what to do here.  These resources contain information
we need to know about where we cannot put PnP devices.  But if we feed the
information into our current resource manager, we end up with conflicts
with existing devices.  

For the moment, I've changed the code to allocate IRQs shared.  The
PS/2 mouse driver should do the same.  I'm still trying to work out
what we can and cannot depend on here. 8(

