Date: Tue, 03 Feb 2004 13:16:41 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: nate@root.org Cc: arch@freebsd.org Subject: Re: newbus ioport usage Message-ID: <20040203.131641.26968129.imp@bsdimp.com> In-Reply-To: <20040203111312.Q32201@root.org> References: <E4469364-5092-11D8-8DD8-000393C72BD6@freebsd.org> <20040127.032119.28084825.imp@bsdimp.com> <20040203111312.Q32201@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[[ I'll draft a longer reply this evening ]]
In message: <20040203111312.Q32201@root.org>
Nate Lawson <nate@root.org> writes:
: 1. Do I have to do all the bus_set_handle gyrations found in nexus?
I think so. I'd have to look at the code. You may be able to copy
the bus_handle from the BUS_ALLOC_RESOURCE resource.
: I
: thought that they could be dispensed with since nexus should do all those
: when acpi0 allocates resources from it with BUS_ALLOC_RESOURCE.
It all depends on the details (eg, I'd have to look at the code you
are writing).
: I can
: certainly leave out the PC98 ifdefs since I'm relatively certain there are
: no PC98 ACPI machines, right?
There never was or will be a ACPI implementation for pc98.
: In the future, I'll make two passes, first to detect system resource
: objects (PNP0C01 and PNP0C02) and reserve resources and the second to
: actually probe acpi devices. I'd rather wait for newbus to do this
: multi-pass approach than attempt it myself with hacks to try to localize
: it.
Yes. We need a better discovery phase followed by an attach phase. I
don't know if this is a newbus API change yet or not. I can see it
being done with most of the APIs that are in place now, but a few
tweaks might be in order.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040203.131641.26968129.imp>