Re: kern/38298

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

The following reply was made to PR kern/38298; it has been noted by GNATS.

From: "Scott Telford" <stelford%mail.com@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
stelford%mail.com@localhost
Cc: 
Subject: Re: kern/38298
Date: Tue, 15 Apr 2008 23:24:22 +0000

 >   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 */
 
 >=20
 >   So what happens is that the slot is in badvcc state and won't power dow=
 n?
 >   Wouldn't it be better to detect and handle that inside pccbb_power()?
 
 Possibly.=20
 
 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 ha=
 ven't
 tried that yet.
 
 Regards,
 Scott.
 
 
 --=20
 Want an e-mail address like mine?
 Get a free e-mail account today at www.mail.com!