From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: de2104x: interrupts before interrupt handler is registered
Date: Mon, 06 Mar 2006 18:02:34 -0600 [thread overview]
Message-ID: <440CCD9A.3070907@shaw.ca> (raw)
In-Reply-To: <5NnDE-44v-11@gated-at.bofh.it>
linux-os (Dick Johnson) wrote:
> This started to happen in a lot of PCI drivers once it became
> necessary to call pci_enable_device() in order to make the
> returned IRQ values valid. This has been reported numerious
> times and has not been fixed. Basically, in order to get
> the correct value, one needs to disable the board in some
> unspecified way so it is not possible for it to generate
> an interrupt before enabling the board. With some devices
> this may not be possible!
What kind of board behaves that way? pci_enable_device just enables the
device BARs and wakes it up if it was suspended, I should think that any
device that starts generating interrupts from that must be quite broken..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-03-07 1:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5N5Ql-30C-11@gated-at.bofh.it>
[not found] ` <5NnDE-44v-11@gated-at.bofh.it>
2006-03-07 0:02 ` Robert Hancock [this message]
2006-03-07 12:07 ` de2104x: interrupts before interrupt handler is registered linux-os (Dick Johnson)
2006-03-07 13:58 ` Robert Hancock
2006-03-07 14:21 ` linux-os (Dick Johnson)
2006-03-07 17:51 ` Bjorn Helgaas
2006-03-07 18:17 ` linux-os (Dick Johnson)
2006-03-08 0:05 ` Robert Hancock
2006-03-08 8:18 ` Jesse Brandeburg
2006-03-08 16:05 ` Bjorn Helgaas
2006-03-08 19:34 ` Martin Michlmayr
2006-03-08 0:00 ` Robert Hancock
2006-03-08 12:03 ` linux-os (Dick Johnson)
2006-03-08 23:34 ` Robert Hancock
2006-03-09 12:42 ` linux-os (Dick Johnson)
[not found] <5Nz1Y-4hZ-25@gated-at.bofh.it>
[not found] ` <5NKTG-4F7-21@gated-at.bofh.it>
[not found] ` <5NLmp-5sk-5@gated-at.bofh.it>
[not found] ` <5NODG-1RH-3@gated-at.bofh.it>
[not found] ` <5O23T-59S-15@gated-at.bofh.it>
2006-03-09 0:02 ` Robert Hancock
2006-03-05 18:07 Martin Michlmayr
2006-03-05 18:59 ` Francois Romieu
2006-03-06 14:35 ` Martin Michlmayr
2006-03-06 19:17 ` Martin Michlmayr
2006-03-06 19:48 ` Francois Romieu
2006-03-06 19:59 ` Martin Michlmayr
2006-03-06 20:23 ` Francois Romieu
2006-03-06 20:29 ` Martin Michlmayr
2006-03-06 20:54 ` Francois Romieu
2006-03-07 5:16 ` Martin Michlmayr
2006-03-06 21:17 ` Francois Romieu
2006-03-07 5:11 ` Martin Michlmayr
2006-03-07 14:57 ` Martin Michlmayr
2006-03-08 0:15 ` Francois Romieu
2006-03-08 3:22 ` Martin Michlmayr
2006-03-07 15:16 ` Martin Michlmayr
2006-03-06 13:02 ` linux-os (Dick Johnson)
2006-03-06 13:02 ` linux-os (Dick Johnson)
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=440CCD9A.3070907@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.