-----BEGIN PGP SIGNED MESSAGE-----
The actual selection of the VPI:VCI used is done by the
connection-oriented client driver, such as LANE or IPATM. The client
will make a call to "create" a VC, which will in turn cause your
miniport's MiniportCoCreateVc function to be called. In that call you
return a structure that will represent a VC. NDIS will return this
structure to you whenever it wants to operate on the VC.
Next the client "activates" the VC, which causes your miniport's
MiniportCoActivateVc to be called. One of the parameters to the
MiniportCoActivateVc is a pointer to a CO_CALL_PARAMETERS structure.
Among other things, this structure contains the VPI:VCI that the
client wants to use.
CallParameters->MediaParameters.MediaSpecific.Parameters should be a
pointer to a ATM_MEDIA_PARAMETERS structure that contains the VPI and
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]
]On Behalf Of encarta
> Sent: Monday, April 17, 2000 10:23 PM
> To: NT Developers Interest List
> Subject: [ntdev] Where to get VPI/VCI in CO-miniport driver
> Hi, all
> I'm writing an NDIS5.0 ATM Adapter driver.
> Now I hanve a question : in my miniport driver , where can I
> get the VPI/VCI value
> of the ATM connection.
> It seems that I can set the VPI/VCI in the miniport.But I'm not
> Does anyone know where can these values from?
> Thanks a lot.
> Xiaohua Cai
> Institute of Modern Communications, SJTU
> Free Email/SMTP/POP, http://www.bn3.com
, Hosting[email protected]
> You are currently subscribed to ntdev as: [email protected]
> To unsubscribe send a blank email to $subst('Email.Unsub')
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2
-----END PGP SIGNATURE-----