mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Takashi Iwai" <takashi.iwai@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Jeff Garzik" <jeff@garzik.org>, "Takashi Iwai" <tiwai@suse.de>,
	"Andrew Morton" <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, barkalow@iabervon.org
Subject: Re: [git patch] improve INTx toggle for PCI MSI
Date: Fri, 8 Dec 2006 12:00:31 +0900	[thread overview]
Message-ID: <6dc076840612071900r657e78dag1377312d86042c67@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612071504570.3615@woody.osdl.org>

2006/12/8, Linus Torvalds <torvalds@osdl.org>:
>
>
> On Thu, 7 Dec 2006, Jeff Garzik wrote:
> >
> > "it boots" on ICH7 at least.
>
> Ok. Pulled, pushed out.
>
> There was some noise saying that this may actually fix the problems with
> the NVidia "Intel HDA" sound situation? Can people who saw that issue try
> it out whether this just makes MSI works for them?
>
> Takashi added to the To: field, because he hopefully remembers and has a
> clue about the proper identities in question.. Iirc, you needed to have
> not only a NVidia chipset, but also have the legacy interrupt shared with
> some other device to see the problem.

Well, I'm on vacation now, so cannot answer much, too :)

IIRC, the problem was with HD-audio and network devices on Nvidia.
The explicit call of pci_intx() (currently implemented in hd-audio
driver locally) helped avoiding the orphan irq problem, but doesn't
fix the MSI problem itself.  (Some might have been fixed indeed,
but I don't have reports in hands.)


Takashi

  reply	other threads:[~2006-12-08  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 22:58 Jeff Garzik
2006-12-07 23:08 ` Andrew Morton
2006-12-07 23:09 ` Linus Torvalds
2006-12-08  3:00   ` Takashi Iwai [this message]
2006-12-08 16:44 ` Daniel Barkalow

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=6dc076840612071900r657e78dag1377312d86042c67@mail.gmail.com \
    --to=takashi.iwai@gmail.com \
    --cc=akpm@osdl.org \
    --cc=barkalow@iabervon.org \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®