mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: kernel@agotnes.com, akpm@osdl.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-usb-users@lists.sourceforge.net,
	linux-usb-devel@lists.sourceforge.net, stern@rowland.harvard.edu,
	cw@f00f.org, vsu@altlinux.ru
Subject: Re: how I know if a interrupt is ioapic_edge_type or  ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]]
Date: Thu, 22 Jun 2006 14:29:02 -0700	[thread overview]
Message-ID: <20060622142902.5c8f8e67.rdunlap@xenotime.net> (raw)
In-Reply-To: <1150977386.2859.34.camel@localhost.localdomain>

On Thu, 22 Jun 2006 12:56:25 +0100 Sergio Monteiro Basto wrote:

> On Wed, 2006-06-21 at 21:08 -0700, Randy.Dunlap wrote:
> > 
> > If you have a specific issue/problem, it would probably be
> > better just to focus on that. 
> 
> on linux-2.6.17/drivers/pci/quirks.c	
> 
>   * we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
>   * interrupts delivered properly.
>   */
> 
>  static void quirk_via_irq(struct pci_dev *dev)
>  {
>  	u8 irq, new_irq;
> 
> I want here put something like:  if ( dev->irq != XT-PIC) return and don't quirk this dev.
>  	else 

I don't think the interrupt device mode is known by this code (AFAICT
with a quick look).  The function is only called for certain VIA chipsets.

Do you want the quirk for any particular hardware device?
You might be able to look at the function's <dev> parameter
to decide on using the quirk or not.


> 	new_irq = dev->irq & 0xf;
>  	pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);


---
~Randy

  reply	other threads:[~2006-06-22 21:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44953B4B.9040108@agotnes.com>
2006-06-20 11:21 ` [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Johny
2006-06-20 11:40   ` Andrew Morton
2006-06-20 13:22     ` Sergio Monteiro Basto
2006-06-21 10:50     ` Johny
2006-06-22  0:36       ` who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Sergio Monteiro Basto
2006-06-22  0:47         ` Randy.Dunlap
2006-06-22  1:04           ` how I " Sergio Monteiro Basto
2006-06-22  4:08             ` Randy.Dunlap
2006-06-22 11:56               ` Sergio Monteiro Basto
2006-06-22 21:29                 ` Randy.Dunlap [this message]
2006-06-22 22:46                   ` Sergio Monteiro Basto
2006-06-22 22:54                     ` Chris Wedgwood
2006-06-23  1:00                       ` Sergio Monteiro Basto
2006-06-23  1:39                         ` Randy.Dunlap
2006-06-23  1:50                           ` Sergio Monteiro Basto
2006-06-23  2:02                             ` Randy.Dunlap
2006-06-28  1:08                         ` [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergio Monteiro Basto
2006-06-23  1:40                       ` how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Johny
2006-06-22 23:25                     ` Randy.Dunlap
2006-06-23  1:30                       ` Sergio Monteiro Basto
2006-06-23 15:31         ` [linux-usb-devel] who I do " David Brownell
2006-06-20 12:09   ` [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergey Vlasov
2006-06-20 13:30     ` Sergio Monteiro Basto
2006-06-20 13:59       ` Sergey Vlasov

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=20060622142902.5c8f8e67.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=cw@f00f.org \
    --cc=kernel@agotnes.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=sergio@sergiomb.no-ip.org \
    --cc=stern@rowland.harvard.edu \
    --cc=vsu@altlinux.ru \
    /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®