All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Grant Grundler <grundler@parisc-linux.org>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
	gregkh <greg@kroah.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, ak@suse.de
Subject: Re: [PATCH] MSI interrupts: disallow when no LAPIC/IOAPIC support
Date: Wed, 28 Sep 2005 21:34:26 -0600	[thread overview]
Message-ID: <20050929033426.GA3892@colo.lackof.org> (raw)
In-Reply-To: <1127860670.10674.32.camel@localhost.localdomain>

On Tue, Sep 27, 2005 at 11:37:50PM +0100, Alan Cox wrote:
> On Maw, 2005-09-27 at 17:26 -0400, Jeff Garzik wrote:
> > Grant Grundler wrote:
> > > I've no clue why folks thought it was better to ignore
> > > the IO APIC on UP kernels.
> > 
> > Hysterical raisins:  the -majority- of the early uniprocessor systems 
> > that claimed IOAPIC support were broken.
> 
> Not really broken in most cases, but since nobody was using the APIC
> board makers didn't bother wiring for it.

ok. Any clue how PCI IRQs got routed/handled on those boxes?
Did UP boards have an 8259 PIC and an IRQ line to the CPU?
Could an 8529 PIC even co-exist with an IO APIC?

Or was it something more silly like BIOS mfgs had no version
of Windows that could grok a IRQ routing table and thus no
incentive to enable that feature?

thanks,
grant

  reply	other threads:[~2005-09-29  3:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  3:11 [PATCH] MSI interrupts: disallow when no LAPIC/IOAPIC support Randy.Dunlap
2005-09-27  4:48 ` Grant Grundler
2005-09-27  4:52   ` Randy.Dunlap
2005-09-27  5:21     ` Grant Grundler
2005-09-27  9:14       ` Mikael Pettersson
2005-09-27 15:51         ` Grant Grundler
2005-09-27  9:11     ` Mikael Pettersson
2005-09-27 21:26   ` Jeff Garzik
2005-09-27 22:37     ` Alan Cox
2005-09-29  3:34       ` Grant Grundler [this message]
2005-09-29 20:09         ` Eric W. Biederman

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=20050929033426.GA3892@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=rdunlap@xenotime.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.