vincent wang wrote:
>
>> Another thing I noticed was that the cfgadm -l command didn't notice a
>> card if I inserted one after booting. I sort of assumed this was an
>> error in either interrupt or status checking code, but I've not tested
>> it recently. I'll try 0.3 first and see what happens.
>>
>>
>>
> cfgadm currently only recognizes 32bit PC Cards. 16bit PC Cards are not
> recignozed at present. The cardbus driver handles 16bit vs 32bit cards
> very
> differently. If the device shows up in prtconf but not in cfgadm, then
> it's this
> problem. It may be necessary to make it also recognize 16bit PC Cards.
I was definitely using a 32-bit card. I didn't expect cfgadm to notice
a 16-bit card. Under older releases, 16-bit card removal/insertion are
"transparent" (similar to USB), which works well because the controllers
can detect removal/insertion and the pcmcia framework was designed with
this in mind (unlike the cardbus framework which mostly follows hot plug
PCI.)
I didn't get around to testing your patch today, but I will definitely
do so first thing tomorrow morning.
>
> Snv_44 does not support surprise removal of 32bit cards well, you may
> occasionally encounter panics. This is fixed in snv_46. I'll send you
> the latest
> bits and source so you can help try them out.
Wow. Well, we (Tadpole) have never supported surprise removal of
Cardbus 32 devices. Heck, I'd expect bad things to happen in drivers,
since a lot of cardbus cards want to do DMA, etc. where surprise removal
could leave things like descriptor rings in an inconsistent state.
I'd strongly recommend that users working with cardbus be educated to
use cfgadm to manage insertion and removal.
-- Garrett
>
> Vincent.
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
