mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Cc: rth@twiddle.net, torvalds@transmeta.com
Subject: Re: /proc/pci deprecation?
Date: Mon, 9 Dec 2002 01:15:24 -0800	[thread overview]
Message-ID: <200212090915.BAA10952@adam.yggdrasil.com> (raw)

Linus Torvalds wrote:
> - we should _never_ update the PCI_INTERRUPT_LINE register, because it
>   destroys boot loader information (the same way we need to not overwrite
>   BIOS extended areas and ACPI areas etc in order to be able to reboot
>   cleanly)

	I don't think the kernel presently does this, but if it
were to actually do the chipset-specific programming change the IRQ
routing of a device, it should update PCI_INTERRUPT_LINE precisely
so that the information will be passed on across a soft reboot.

	This comes up for me because I have daone motherobard with a
BIOS that never programs the USB controller's interrupt line, so I
have to do the chipset-specific bit twiddling (which, in this case
happens to be simply writing the desired irq into the device's
PCI_INTERRUPT_LINE register anyhow).  By the way, I also had to change
arch/i386/kernel/pci.c to get it to reread PCI_INTERRUPT_LINE if it
thought the interrupt was not routed, although all that I would really
need is some way for a user level program to persuade the kernel to
believe that a particular PCI device's interrupt line A has changed to
irq n.

	This exception is probably not relevant to what Linus and
Richard are discussing, but I thought should mention it, lest that
"_never_" be interpreted too absolutely.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-12-09  9:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09  9:15 Adam J. Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:00 Nicolas Mailhot
2002-12-06 23:18 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-09 13:35             ` 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
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
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=200212090915.BAA10952@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rth@twiddle.net \
    --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

Powered by JetHome