public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Lost Garden <yuanzhiqiang13@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI Interrupt Problems Since Kernel-2.6.19
Date: Mon, 21 Jan 2008 17:49:15 -0600	[thread overview]
Message-ID: <47952F7B.7080506@shaw.ca> (raw)
In-Reply-To: <fa.ymyLoSJzoVBOIvut+kIrLt7x/M4@ifi.uio.no>

Lost Garden wrote:
>     I'm writing a driver for DVB-C PCI receiving cards these days and
> I found a tricky problem of interrupts. Since kernel-2.6.19 the
> interrupt handlers get rid of "struct pt_regs*" argument  and I think
> it will be easy for me to modify the driver to fit for the recent
> kernel.
>    I simply delete the "struct pt_regs *" argument of my interrupt
> handler and compile the driver again. But then I met a rather tricky
> problem. I cann't get the PCI intterrupt now! I found that the chip on
> the card actually had generate an interrupt and it should not be the
> hardware problem.
>   I'm get seriously confused. My driver works well under kernel-2.6.18
> but not generates a single interrupt signal when works above
> kernel-2.6.19.
>  Does anybody meet similar problems?
>  Sincerely
>  Yours, Lost Graden.
> 1,21. 2008

Need more details, like dmesg output. The source code of your driver 
would also be useful. One common problem is not calling 
pci_enable_device before requesting the interrupt..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2008-01-21 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ymyLoSJzoVBOIvut+kIrLt7x/M4@ifi.uio.no>
2008-01-21 23:49 ` Robert Hancock [this message]
2008-01-21  2:34 PCI Interrupt Problems Since Kernel-2.6.19 Lost Garden

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=47952F7B.7080506@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuanzhiqiang13@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