Date: Thu, 06 Sep 2001 15:45:35 -0700 From: Mike Smith <msmith@freebsd.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 Message-ID: <200109062245.f86MjZo03743@mass.dis.org> In-Reply-To: Message from Mitsuru IWASAKI <iwasaki@jp.freebsd.org> of "Fri, 07 Sep 2001 01:01:47 %2B0900." <20010907.010147.104026307.iwasaki@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109062245.f86MjZo03743>