Re: kern/38298

["Scott Telford" <stelford%mail.com@localhost>]

>   The 0x00004000 needs a symbolic name (CB_SOCKET_FORCE_*, and maybe
>   CB_SOCKET_STAT_*).

I agree. I'm not sure what this bit is called in the official documentation,
but Linux defines it thus:

#define    CB_CVSTEST           0x00004000      /* Card VS test */

> 
>   So what happens is that the slot is in badvcc state and won't power down?
>   Wouldn't it be better to detect and handle that inside pccbb_power()?

Possibly. 

While perusing the PR database, I found PR/36652, which seems to describe
a similar problem. I've tried merging the pccbb.c rev 1.145 change suggested
in this PR, which does write to CB_SOCKET_FORCE in pccbb_power(), but this
doesn't fully fix the problem - the kernel doesn't seem to hang, but I still
get the "disabling socket" message and the CardBus device isn't probed.
Maybe if I added the 0x00004000 bit to the write, this might work, but I haven't
tried that yet.

Regards,
Scott.


-- 
Want an e-mail address like mine?
Get a free e-mail account today at www.mail.com!