>I'm just trying to find out how the PCMCIA "API" works.
>I mean the API that calls out, if a device
>attaches/detaches from PCMCIA.
Attach to PCMCIA$, register as an client. This installs an event hook.
>I found out currently that detection is just
>done by "AttachDD" to "PCMCIA$".
Yes.
>Also the own IDC gets called to
>show what device attached/detached.
No, the event procedure.
>But there is no real documentation and I couldnt find out how the
>actual interaction works.
Sample code pc95smpl, pcmcia.sys source code,
Documentation from pcmcia organisation costs money,
Linux pcmcia docs looks similar to that spec,
And you can have a look how MFT (QEMM) DOS apps do it..
>I want to get called on any device attach/detachment. I think that I will do that
>connecting on INITCOMPLETE, because that's the point where USB comes accessible as
>well.
Should work at that time, but for me it works even earlier.
>Also are there Cardbus-drivers available using the same API?
pc95smpl, tdkenab, cbenable ...
But current pcmcia.sys will not work unpatched.
The problem would be: how do you know, if/how many/which IO windows,
IRQ, memory windows, a card and its application needs.
Example: Realtek 8139 CardBus. One IRQ would be nice,
current driver can not use memory mapped IO, only direct IO,
256 addresses.
Veit Kannegieser
-----------
To unsubscribe yourself from this list, send the following message
to [EMAIL PROTECTED]
unsubscribe acpi-os2
end
