linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Stian Jordet <liste@jordet.nu>
Cc: Olaf Hering <olh@suse.de>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bogus VIA IRQ fixup in drivers/pci/quirks.c
Date: Tue, 27 Sep 2005 15:58:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0509271556211.3308@g5.osdl.org> (raw)
In-Reply-To: <1127857716.4339be34f239f@webmail.jordet.nu>



On Tue, 27 Sep 2005, Stian Jordet wrote:
> 
> I have no idea. But I'll attach dmesg from the same kernel with your patch, so
> you'll see the differences yourself. I also see that initialization of
> everything have changed. Now scsi is almost the last thing in the dmesg, it
> used to be about the first.  Weird.

That's not my patch. Something else has changed.

Anyway, this dmesg you posted still says

	...
	USB Universal Host Controller Interface driver v2.3
	ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
	ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
**	PCI: Via IRQ fixup for 0000:00:11.2, from 9 to 11
	uhci_hcd 0000:00:11.2: UHCI Host Controller
	uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
	uhci_hcd 0000:00:11.2: irq 11, io base 0x00009800
	hub 1-0:1.0: USB hub found
	hub 1-0:1.0: 2 ports detected
	ACPI: PCI Interrupt 0000:00:11.3[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
**	PCI: Via IRQ fixup for 0000:00:11.3, from 9 to 11
	uhci_hcd 0000:00:11.3: UHCI Host Controller
	uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
	uhci_hcd 0000:00:11.3: irq 11, io base 0x00009400
	hub 2-0:1.0: USB hub found
	hub 2-0:1.0: 2 ports detected
	ACPI: PCI Interrupt 0000:00:11.4[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
**	PCI: Via IRQ fixup for 0000:00:11.4, from 9 to 11
	...

so my patch didn't change anything at all for you (which is correct - it 
was designed not to ;)

So if you have trouble with it, it's something else.

		Linus

  reply	other threads:[~2005-09-27 22:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 18:44 bogus VIA IRQ fixup in drivers/pci/quirks.c Olaf Hering
2005-09-26 21:59 ` Linus Torvalds
2005-09-27  6:09   ` Olaf Hering
2005-09-27 12:29   ` Olaf Hering
2005-09-27 14:27   ` Stian Jordet
2005-09-27 14:42     ` Linus Torvalds
2005-09-27 21:19       ` Stian Jordet
2005-09-27 21:36         ` Linus Torvalds
2005-09-27 21:48           ` Stian Jordet
2005-09-27 22:58             ` Linus Torvalds [this message]
2005-09-28  7:28               ` Matthieu CASTET
2005-09-28 15:32                 ` Matthieu CASTET
2005-09-27 21:52           ` Stian Jordet

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=Pine.LNX.4.58.0509271556211.3308@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    --cc=olh@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).