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: Wed, 10 Sep 2003 22:30:29 +0100 [thread overview]
Message-ID: <200309102230.29794.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030909220142.GA7668@sgi.com>
On Tuesday 09 Sep 2003 11:01 pm, Jesse Barnes wrote:
> On Tue, Sep 09, 2003 at 10:38:26PM +0100, Andrew de Quincey wrote:
> > On Tuesday 09 September 2003 22:17, Jesse Barnes wrote:
> > > On Tue, Sep 09, 2003 at 09:43:58PM +0100, Andrew de Quincey wrote:
> > > > On Tuesday 09 September 2003 21:13, Jesse Barnes wrote:
> > > > > Instead of going into an infinite loop because the list isn't setup
> > > > > yet, just return NULL if there are no prt entries.
> > > >
> > > > Ah, this is a patch against the vanilla kernel.. This is
> > > > unfortunately incompatible with my recent ACPI patches.
> > >
> > > Maybe you could include it in your patch then? I noticed that your
> > > patch changes some of the IRQ routing code...
> >
> > I'm not sure it is still needed or not. The patch makes a lot of changes
> > as to how the acpi_prt list is generated. What triggers the problem
> > exactly, so I can test?
>
> An SGI Altix system that only supports part of the ACPI spec :). Our
> PROM currently doesn't generate any MADT entries other than CPUs (I'm
> not even sure how we could add them since we use our own interrupt
> controller, not an IOAPIC or IOSAPIC) and lacks an ACPI namespace, so
> we're missing all sorts of stuff.
So, exactly as your patch did, you just want it to drop back if there were no
PCI routing entries found by ACPI... sounds sensible enough.
Can you confirm I have this right?
next prev parent reply other threads:[~2003-09-10 21:32 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 [this message]
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
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=200309102230.29794.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
all inboxes | Powered by JetHome®