From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Albert Cranford <ac9410@bellsouth.net>, linux-kernel@vger.kernel.org
Subject: Re: Related VIA PCI crazyness?
Date: 08 Jan 2001 23:06:08 -0700 [thread overview]
Message-ID: <m13deti7jj.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10101071915400.28661-100000@penguin.transmeta.com>
In-Reply-To: Linus Torvalds's message of "Sun, 7 Jan 2001 19:18:17 -0800 (PST)"
Linus Torvalds <torvalds@transmeta.com> writes:
> On Sun, 7 Jan 2001, Albert Cranford wrote:
> > > Could anybody with a VIA chip who has the energy please do something for
> > > me:
> > > - enable DEBUG in arch/i386/kernel/pci-i386.h
> > > - do a "/sbin/lspci -xxvvv" on the interrupt routing chip (it's the
> > > "ISA bridge" chip - the VIA numbers are 82c586, 82c596, the PCI
> > > numbers for them are 1106:0586 and 1106:0596, I think)
> > > - do a cat /proc/pci
> > >
> >
> > Does this help.
>
> Ahh, no.
>
> A SMP kernel (or one with UP IO-APIC) is not going to be helpful for this,
> actually. SMP will take the irq data from the MP block, not the pirq table
> (that can be considered something of a misfeature right now, but getting
> the mixture of PCI irq redirection from the MP tables and the pirq irq
> routing information right together is probably not worth it - especially
> as I don't think any MS OS has ever done that either, so the BIOS writers
> have never experienced that combination - so it's almost guaranteed to
> result in strange results).
pirq is specific to they legacy i8259 interrupt handler.
MP is specific to some kind of IO-APIC.
Right now when we enable the IO-APIC we disable the legacy i8259
controller. And I'm not even certain you can have them both enabled
at the same time.
So except for not having an option to disable use of the IO-APIC
I don't see what we could do better.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 12:28 Related VIA PCI crazyness? Philip Armstrong
2001-01-07 14:33 ` Adrian Bunk
2001-01-07 23:52 ` Linus Torvalds
2001-01-07 21:02 ` Albert Cranford
2001-01-08 3:18 ` Linus Torvalds
2001-01-09 6:06 ` Eric W. Biederman [this message]
2001-01-08 2:31 ` Adrian Bunk
2001-01-09 0:53 ` Evan Thompson
2001-01-09 17:19 ` Pete Toscano
[not found] ` <200101072352.PAA28348@penguin.transmeta.com>
2001-01-08 1:44 ` Evan Thompson
2001-01-08 9:08 ` Philip Armstrong
2001-01-10 21:55 ` Philip Armstrong
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=m13deti7jj.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=ac9410@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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