linux-kernel - Re: [PATCH] parport: Use the PCI IRQ if offered

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200903311531.56965.kgabor@bolyai.elte.hu>
Date:	Tue, 31 Mar 2009 15:31:56 -0400
From:	Gabor Kovacs <kgabor@...yai.elte.hu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] parport: Use the PCI IRQ if offered

Hi Alan,

just to confirm, IRQ detection works fine on my Lava parallel card. 

The instrument driver module that registers an irq handler via 
parport_register_device gets false events when parport irq is shared e.g. with 
an ethernet controller. Should irq sharing awareness go to our handler 
function or parport_irq_handler/parport_generic_irq still needs some 
additional patch? (Or have I just missed this second patch?)

Thanks

Gabor Kovacs


On Thursday 26 March 2009 18:40:42 Jeff Garzik wrote:
> Alan Cox wrote:
> > Signed-off-by: Alan Cox <alan@...rguk.ukuu.org.uk>
>
> Reviewed-by: Jeff Garzik <jgarzik@...hat.com>
>
> A long, long time ago I poked at introducing some PCI-ish probing to
> parport_pc, reading the port mode, I/O port, and possibly irq from
> motherboard-specific magic locations.
>
> This is a helpful extension of that [years-old] work... good stuff.
>
> 	Jeff
>
>
>


--
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/