lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <3b7d7830801201834o3f03380eu5c9d82912acd0e3c@mail.gmail.com>
Date:	Mon, 21 Jan 2008 10:34:45 +0800
From:	"Lost Garden" <yuanzhiqiang13@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: PCI Interrupt Problems Since Kernel-2.6.19

    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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ