Win98banter - View Single Post

**Paul[_6_]** · February 24th 21, 01:43 PM posted to microsoft.public.win98.gen_discussion

wrote:
SNIP
Example of a bus bridge.

Cirrus Logic PCIC compatible PCMCIA controller

Example of a driver file. (See if there is
already one of these in the OS.)

MSPCIC.dll

While the PNP entry for the various hardware bus
controllers would work, there is an ACPI-like
entry too. This implies the chip which bridges from
PCI bus to PCMCIA slot, follows standard register
designations.

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607

Whereas the

Megahertz XJ1144 or XJ2144 PCMCIA Modem

entry, that's going to present PNP information when
it runs on the PCMCIA bus in the slot.

The information in the table, doesn't tell much more than
that. I don't have any indication, who made the bus
bridge. And maybe it doesn't matter, as long as it works :-)

Paul

Hi Paul,

I found "MSPCIC.DLL" in WINDOWS\SYSTEM folder.

Also, in WINDOWS\INF folder, "PCMCIA.INF" file has

%PCI\CC_0607.DeviceDesc%=CARDBUS, PCI\CC_0607
(and other lines)

[Control Flags] (section, same file)

"ExcludeFromSelect=PCI\CC_0607"

I have NO idea what that does.

Again, Thanks, John

It's presumably a Microsoft generic driver for the bridge.

I don't think you can just wire the PCI bus directly to
the Cardbus, and there must be some silicon in there
somewhere to do that.

With that driver in place, then it should be possible to
install the modem driver when the modem card is inserted.

Without the bridge, there's a good chance plugging in
the modem would elicit no response at all. If the system
can see an "event" show up, something to trigger PNP,
then chances are there's a driver in place for the bridge.

Even if the Cardbus was 32 bit (say, muxed address and data),
I think there's a rate difference involved too. That bus
runs a bit slower than PCI bus. The wikipedia on PCMCIA or
cardbus might have more details on the particulars.

I would have expected the silicon to perhaps have more
functions than that, and as a consequence, have a more
visible driver situation. Bridges are relatively low
key items (complex in terms of getting the hardware
details at the gate level right, not so much at
the driver level). And as computer users, we're used
to that one being auto-resolved without us knowing
anything has happened. The OS discovers and probes
past a metric ton of bridges inside, and these
kinds of things hardly ever show up in "trouble"
postings :-)

But getting a modem driver or whatever driver the
card needs, that's a different matter. More trouble
is to be expected in such cases.

Paul