Re: [2.6.0-test1] yenta_socket.c:yenta_get_status returns bad value compared to 2.4

[Russell King <rmk@arm.linux.org.uk>]

On Sun, Aug 03, 2003 at 12:07:41PM +0100, Stefan Jones wrote:
> Linux Kernel Card Services 3.1.22
>   options:  [pci] [cardbus] [pm]
> Yenta IRQ list 0038, PCI irq11
> Socket status: 30000417

No card inserted.

> parse_events: socket d080002c thread ce4db3c0 events 00000080
> yenta_get_status: status=30000417
> socket d080002c status 00000041
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x2c8-0x2cf 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> yenta_get_status: status=30000417
> 
> **** INSERT card first time nothing gets printed
> 
> **** REINSERT card and I get this;
> 
> 
> parse_events: socket d080002c thread ce4db3c0 events 00000080
> yenta_get_status: status=30000417
> socket d080002c status 00000041

This is a removal event.

> parse_events: socket d080002c thread ce4db3c0 events 00000080
> yenta_get_status: status=30000411
> socket d080002c status 000000c1

This is an insert event.

Hmm, so it looks like the hardware didn't report an insert event.  Can you
add a couple of printk()'s to yenta_events() to display the values of
cb_event and csc please?

Thanks.
-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html