public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>,
	akpm@osdl.org, Wilco Beekhuizen <wilcobeekhuizen@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA IRQ quirk missing PCI ids since 2.6.16.17
Date: Wed, 08 Nov 2006 18:05:30 +0000	[thread overview]
Message-ID: <1163009130.23956.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20061108202218.8f542fbf.vsu@altlinux.ru>

Ar Mer, 2006-11-08 am 20:22 +0300, ysgrifennodd Sergey Vlasov:
> Hmm, the old comment mentions 686A/B explicitly - seems that these old
> chips also use PCI_INTERRUPT_LINE to control interrupt routing.  Is it
> correct to ignore them here?  Yes, that chips used PCI and not VLink,
> but they also had an internal PIC (and even internal IO-APIC).
> 
> Unfortunately, I no longer have such hardware available.

I have enough docs to extend this approach to those chips if neccessary.
Anyone got an old 686 board to check.

> > +	/* May not be needed for the 8237 */
> > +	{ PCI_VDEVICE(VIA, PCI_DEVICE_ID_VIA_8237), 15 },
> > +	{ PCI_VDEVICE(VIA, PCI_DEVICE_ID_VIA_8237A), 15 },
> 
> 8237 definitely uses PCI_INTERRUPT_LINE to control interrupt routing in
> PIC mode - tested with the audio part by writing bogus values with
> setpci and checking whether interrupts are delivered.

Ok

> If there is no VIA ISA bridge in the system, this won't cache anything.

I no, thats noted in the comments when I posted the diff. If it works
I'll cache ->driver_data instead.

> > -int pci_dev_present(const struct pci_device_id *ids)
> > +struct pci_device_id *pci_find_present(const struct pci_device_id *ids)
> 
> New API without proper refcounting?  Ewww.

pci_device_id objects are not refcounted and don't vanish underneath us.
Devices may but we aren't dealing in devices. The function operates
under the list lock internally so should be safe.

Alan


  reply	other threads:[~2006-11-08 18:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 11:38 VIA IRQ quirk missing PCI ids since 2.6.16.17 Wilco Beekhuizen
2006-11-06 12:47 ` Sergio Monteiro Basto
2006-11-06 21:13   ` Alan Cox
2006-11-07  1:25     ` Dave Jones
2006-11-07  1:34       ` Alan Cox
2006-11-08  8:54         ` Wilco Beekhuizen
2006-11-08 12:43           ` Sergio Monteiro Basto
2006-11-08 14:55             ` Wilco Beekhuizen
2006-11-08 15:19           ` Alan Cox
2006-11-07  4:07       ` Greg KH
2006-11-07  8:31       ` Jeff Garzik
2006-11-08 17:22     ` Sergey Vlasov
2006-11-08 18:05       ` Alan Cox [this message]
2006-11-08 20:33         ` Sergey Vlasov
2006-11-06 13:30 ` Alan Cox

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=1163009130.23956.57.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio@sergiomb.no-ip.org \
    --cc=vsu@altlinux.ru \
    --cc=wilcobeekhuizen@gmail.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