From: Mike Smith <msmith@freebsd.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ACPI 2.0 support
Date: Sat, 18 Nov 2000 07:52:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205749@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205743@msgid-missing>
> I'd also like to incorporate using ACPI methods to get resource
> information for programming PCI devices, eventually leading to
> support for hot-plug PCI via ACPI. Anyone have any thoughts or
> interest there? Thanks,
I hope folks don't mind a stranger dropping in on this discussion; I've
been doing similar work for the IA32 and IA64 FreeBSD codebase though and
this is a point I've been looking at for a while.
The key item to bear in mind here is that ACPI stays out of the way of
other enumeration mechanisms; meaning that ACPI itself isn't going to
help you very much when it comes to resource information for
newly-arrived PCI devices, other than routing interrupts for them (and
even then your bridge driver will still have to correctly swizzle for
devices on the other side of the bridge).
I've written (but not verified) code that uses the Intel ACPI CA codebase
to route PCI interrupts for the host-PCI bridge; I'd be happy to furnish
this on request, although in truth the documentation is enough to make
this a largely trivial task.
As for allocating memory ranges and configuring intermediate bridges;
ACPI doesn't play a role here at all (so far as I've seen, at any rate).
Hope this helps.
Mike
--
... 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
next prev parent reply other threads:[~2000-11-18 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 20:12 [Linux-ia64] ACPI 2.0 support Alex Williamson
2000-11-17 20:34 ` Mallick, Asit K
2000-11-18 7:52 ` Mike Smith [this message]
2000-11-20 16:00 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590678205749@msgid-missing \
--to=msmith@freebsd.org \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox