Unfortunately there is no easy fix; the API is broken 

Forum: PCMCIA driver development
Re: Change in kernel (2.3.99-pre3) causing problem with cardmgr. (Brian Mays)
Date: 2000, Apr 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

This is a "feature" of the new hot plug API. There is no workaround at this time, because there is no mechanism in the new API to pass the correct device name to cardmgr. -- Dave

Messages Inline: Outline:

Re: Unfortunately there is no easy fix; the API is broken Re: Unfortunately there is no easy fix; the API is broken (David Hinds) Date: 2000, Apr 20 From: Steven A. DuChene <sad@valinux.com>

Hmm, so does that mean that unless things change drastically one way or the other, laptop users with PCMCIA cards will not be able to migrate to 2.4 when it is released? This reasoning sounds remarkably similar to the bad feelings surrounding the network driver changes in the late 2.3 kernels and the Donald Becker crafted generic network drivers (like the eepro100 for instance). I hope this does not degenerate into a similar situation. Isn't there some sort of compromise that could be reached?

1. I don't think the problem is as bad as all that by David Hinds, 2000, Apr 20

to: "Unfortunately there is no easy fix; the API is broken"