From owner-freebsd-current Thu Sep 6 15:39:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 188B337B401 for ; Thu, 6 Sep 2001 15:39:09 -0700 (PDT) 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 Subject: Re: [acpi-jp 1247] Re: ACPI and PS/2 mouse problem In-Reply-To: Message from Mitsuru IWASAKI 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 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: 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( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message