From: Robert Siemer <Robert.Siemer@gmx.de>
To: mdiehlcs@compuserve.de, torvalds@transmeta.com
Cc: jgarzik@mandrakesoft.mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: PCI IRQ routing problem in 2.4.0 (updated patch)
Date: Tue, 30 Jan 2001 02:07:46 +0100 [thread overview]
Message-ID: <20010130020746C.siemer@panorama.hadiko.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101291859220.29065-100000@notebook.diehl.home>
In-Reply-To: <Pine.LNX.4.10.10101290928060.9131-100000@penguin.transmeta.com> <Pine.LNX.4.21.0101291859220.29065-100000@notebook.diehl.home>
From: Martin Diehl <mdiehlcs@compuserve.de>
> On Mon, 29 Jan 2001, Linus Torvalds wrote:
> Below is the updated patch. It should handle both (0x01/0x41
> like) mappings. I can (and did) only test the 0x01 case.
> USBIRQ routing (0x62) supported, IDE/ACPI/DAQ untouched.
I don't really understand your note above, but your patch alone does
not fix my problem. - Linus diff over pci-irq.c does.
The kernel still does not think what the bios states; it's like the
vanilla 2.4.0 in this regard. (--> on my box: kernel panic after
"modprobe usb-ohci && modprobe hid")
Bye,
Robert
-
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-30 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0101291801580.29065-400000@notebook.diehl.home>
2001-01-29 17:34 ` PCI IRQ routing problem in 2.4.0 Linus Torvalds
2001-01-29 19:02 ` PCI IRQ routing problem in 2.4.0 (updated patch) Martin Diehl
2001-01-30 1:07 ` Robert Siemer [this message]
2001-01-31 10:18 ` Martin Diehl
2001-01-31 19:11 Dunlap, Randy
[not found] <20010201003032U.siemer@panorama.hadiko.de>
2001-02-01 0:37 ` Martin Diehl
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=20010130020746C.siemer@panorama.hadiko.de \
--to=robert.siemer@gmx.de \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdiehlcs@compuserve.de \
--cc=siemer@panorama.hadiko.de \
--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
all inboxes | Powered by JetHome®