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:

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?

I don't think the problem is as bad as all that Re: Re: Unfortunately there is no easy fix; the API is broken (Steven A. DuChene) Date: 2000, Apr 20 From: David Hinds <dhinds@pcmcia.sourceforge.org>

No bad feelings are involved, as far as I'm concerned. And there is nothing preventing laptop users from migrating to 2.4 whenever it is released. I still distribute PCMCIA drivers that build correctly on 2.3.99* and work correctly. Linus and others made a choice to not include some of that code in the kernel; I pointed out what the issues were and he made a decision that I disagreed with, but I respect his decision. I think it would be very unfair to criticize me for those choices, and Linus will tell you the same thing. Compared to the situation with Donald Becker, I think there are a few differences. I'm not fighting a "turf war" here, and I'm not blowing off PCMCIA because I didn't get my way. I continue to release timely updates and continue to give feedback and send contributions to Linus and other kernel developers. I said there was no easy fix, because there really is no easy fix, not because I'm holding out on anyone. It is not unsolvable, but it also is not something I can fix on my own (and my solution has already been explicitly rejected). -- Dave

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