Re: [PATCH 2.6.13-rc3] pcmcia: pcmcia_request_irq for !IRQ_HANDLE_PRESENT

2005-07-24 Thread Dominik Brodowski
On Sun, Jul 24, 2005 at 12:40:40PM +0100, Russell King wrote: > On Sat, Jul 23, 2005 at 10:11:13PM +0200, Dominik Brodowski wrote: > > Thanks for the excellent debugging. Your patch seems to work, however it > > might be better to do just this: > > This can be racy if two drivers are simultaneousl

Re: [PATCH 2.6.13-rc3] pcmcia: pcmcia_request_irq for !IRQ_HANDLE_PRESENT

2005-07-24 Thread Russell King
On Sat, Jul 23, 2005 at 10:11:13PM +0200, Dominik Brodowski wrote: > Thanks for the excellent debugging. Your patch seems to work, however it > might be better to do just this: This can be racy if two drivers are simultaneously trying to request an IRQ. 'data' must be unique to different threads

Re: [PATCH 2.6.13-rc3] pcmcia: pcmcia_request_irq for !IRQ_HANDLE_PRESENT

2005-07-23 Thread Dominik Brodowski
Hi, > When a driver calls pcmcia_request_irq with IRQ_HANDLE_PRESENT unset, it looks > for an open IRQ by request_irq()ing with a dummy handler and NULL dev_info. > free_irq uses dev_info as a key for identifying the handler to free among > those > sharing an IRQ, so request_irq returns -EINVAL i

[PATCH 2.6.13-rc3] pcmcia: pcmcia_request_irq for !IRQ_HANDLE_PRESENT

2005-07-16 Thread Noah Misch
Between 2.6.10 and 2.6.11, the kernel began to print this message when I inserted my IBM Home and Away adapter (pcnet_cs) into an i82365 slot: 1.0: RequestIRQ: Unknown error code 0xffea Initialization of the device then aborted; no `eth0' appeared. Another user recently reported the same p