From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Richard Henderson <rth@twiddle.net>,
Patrick Mochel <mochel@osdl.org>, Willy Tarreau <willy@w.ods.org>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com
Subject: Re: /proc/pci deprecation?
Date: 09 Dec 2002 22:57:26 -0700 [thread overview]
Message-ID: <m13cp6wh4p.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1039458577.10470.49.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Mon, 2002-12-09 at 17:00, Linus Torvalds wrote:
> > On 9 Dec 2002, Alan Cox wrote:
> > > I wonder if this is why we have all these problems with VIA chipset
> > > interrupt handling. According to VIA docs they _do_ use
> > > PCI_INTERRUPT_LINE on integrated devices to select the IRQ routing
> > > between APIC and PCI/ISA etc, as well as 0 meaning "IRQ disabled"
> >
> > Whee.. That sounds like a load of crock in the first place, since the
> > PCI_INTERRUPT_LINE thing should be just a scratch register as far as I
> > know. However, it doesn't really matter - we definitely should never write
> > to it anyway, so the VIA behaviour while strange should still be
> > acceptable.
>
> Tested and verified. If I leave it alone non apic mode works. To use
> APIC mode I have to write the new IRQ value into that register. I've
> shoved that into the driver for now, since its a demented chip specific
> horror.
Think you can put in a reboot notifier/device shutdown method to restore
it to it's old value, so kexec has a chance of working correctly with
this hardware.
Eric
next prev parent reply other threads:[~2002-12-10 5:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 23:18 /proc/pci deprecation? Petr Vandrovec
2002-12-07 7:44 ` Willy Tarreau
2002-12-07 13:20 ` Tomas Szepe
2002-12-07 19:03 ` Linus Torvalds
2002-12-08 2:56 ` Patrick Mochel
2002-12-08 4:21 ` Linus Torvalds
2002-12-08 20:56 ` Richard Henderson
2002-12-09 1:54 ` Linus Torvalds
2002-12-09 3:59 ` Patrick Mochel
2002-12-13 12:36 ` kernel isapnp (2.4.20) h-peter recktenwald
2002-12-09 13:35 ` /proc/pci deprecation? Ivan Kokshaysky
2002-12-09 14:11 ` Alan Cox
2002-12-09 17:00 ` Linus Torvalds
2002-12-09 18:29 ` Alan Cox
2002-12-09 18:11 ` Linus Torvalds
2002-12-09 18:16 ` Jeff Garzik
2002-12-10 0:43 ` Alan Cox
2002-12-10 0:30 ` Linus Torvalds
2002-12-10 5:57 ` Eric W. Biederman [this message]
2002-12-09 23:27 ` Vojtech Pavlik
2002-12-09 14:14 ` Alan Cox
2002-12-10 16:42 ` Martin Mares
2002-12-07 12:35 ` Erik Hensema
2002-12-07 13:15 ` Dr. David Alan Gilbert
2002-12-07 17:46 ` Arnaldo Carvalho de Melo
2002-12-09 19:03 ` Rogier Wolff
2002-12-09 19:08 ` Arnaldo Carvalho de Melo
2002-12-07 13:14 ` Tomas Szepe
2002-12-07 18:52 ` Petr Vandrovec
2002-12-08 12:30 ` Erik Hensema
2002-12-09 10:14 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:00 Nicolas Mailhot
2002-12-09 9:15 Adam J. Richter
2002-12-06 21:13 Patrick Mochel
2002-12-06 22:17 ` Jeff Garzik
2002-12-06 22:13 ` Patrick Mochel
2002-12-07 16:23 ` Krzysztof Halasa
2002-12-07 21:18 ` Kai Henningsen
2002-12-08 20:01 ` Krzysztof Halasa
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=m13cp6wh4p.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rth@twiddle.net \
--cc=torvalds@transmeta.com \
--cc=willy@w.ods.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