From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: jbarnes@sgi.com (Jesse Barnes)
Cc: andrew.grover@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deal with lack of acpi prt entries gracefully
Date: Thu, 11 Sep 2003 23:00:30 +0100 [thread overview]
Message-ID: <200309112300.30882.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030911212059.GA27063@sgi.com>
On Thursday 11 Sep 2003 10:20 pm, Jesse Barnes wrote:
> On Thu, Sep 11, 2003 at 10:13:13PM +0100, Andrew de Quincey wrote:
> > > That might work, though I'll be using the ACPI namespace to drive PCI
> > > discovery soon (hacking the PROM now). Maybe I should add some MADT
> > > and _PRT entries while I'm at it? The problem is that we don't support
> > > IOAPIC or IOSAPIC interrupt models/hw registers.
> >
> > Which base architecture do you use? x86 and x86_64 ACPI now both support
> > PIC based interrupt models.. as thats the only other option AFAIK (It
> > tries IOAPIC first, then if that fails, it drops back to trying PIC
> > mode).
>
> None of the above. We have our own NUMAlink based interrupt protocol
> model.
Oooer! Hmm, the existing code would probably NOT like having _PRT entries for
a model it doesn't know about.... you could add support for it fairly easily
though I suppose...
next prev parent reply other threads:[~2003-09-11 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 20:13 Jesse Barnes
2003-09-09 20:43 ` Andrew de Quincey
2003-09-09 21:17 ` Jesse Barnes
2003-09-09 21:38 ` Andrew de Quincey
2003-09-09 22:01 ` Jesse Barnes
2003-09-10 21:30 ` Andrew de Quincey
2003-09-10 21:38 ` Jesse Barnes
2003-09-11 20:40 ` Andrew de Quincey
2003-09-11 20:53 ` Jesse Barnes
2003-09-11 21:13 ` Andrew de Quincey
2003-09-11 21:20 ` Jesse Barnes
2003-09-11 22:00 ` Andrew de Quincey [this message]
2003-09-11 22:04 ` Jesse Barnes
2003-10-01 1:22 Brown, Len
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=200309112300.30882.adq_dvb@lidskialf.net \
--to=adq_dvb@lidskialf.net \
--cc=andrew.grover@intel.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@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
Powered by JetHome