Bus+Functional driver in the single driver

NTDEV
1

Hi Gurus,

We usally make a bus driver for the multifunction device and then use a
functional driver for each of the child PDO.

I am looking for a design of a multifunction device that may not be an
usual prctice. First, I make the usual bus driver and create the child
devices. Then I want to make the bus driver to act as a Functional driver
for each of the child devices it has created. To do this I mention the
same driver for the child device in its inf to load. I found that it goes
to the AddDevice routine where I can do those stuff for this new
PhysicalDeviceObject, I have made a global counter and list so that right
things will be done for multifunction and its child devices. Once I’m here
I’m routing all the PnP IRP’s to the related routine that handles PNP IRP
for the child’s functional DOs. Now, I have three sets of PnP IRP handler
routines, that is, one for the multifunction device, one for each child
PDO and lastly one for each child FDO. I do the ExternalNaming for the
child FDO by IRP_MN_START_DEVICE of the last PnP IRP handler routine that
I mentioned. I found my child devices are visible to Win32 and I can do
things like read/write etc.

I have got succes upto this point. Now, I’m asking Gurus whether I’m on
the right track. Is there any possibility that any DO’s pointer become
stale? Or, am I missing any concept?

Thanks in advance.
Hakim

2

I have no substantial experience in writing a bus driver (for w2k+ - I
assume you aren’t interested in writing a NT4 driver) but I think the
toaster example from DDK deals with your problem and could be a help for
you.

Regards
Volker

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@connecttech.com
Sent: Tuesday, March 19, 2002 6:57 PM
To: NT Developers Interest List
Subject: [ntdev] Bus+Functional driver in the single driver

Hi Gurus,

We usally make a bus driver for the multifunction device and then use a
functional driver for each of the child PDO.

I am looking for a design of a multifunction device that may not be an
usual prctice. First, I make the usual bus driver and create the child
devices. Then I want to make the bus driver to act as a Functional driver
for each of the child devices it has created. To do this I mention the
same driver for the child device in its inf to load. I found that it goes
to the AddDevice routine where I can do those stuff for this new
PhysicalDeviceObject, I have made a global counter and list so that right
things will be done for multifunction and its child devices. Once I’m here
I’m routing all the PnP IRP’s to the related routine that handles PNP IRP
for the child’s functional DOs. Now, I have three sets of PnP IRP handler
routines, that is, one for the multifunction device, one for each child
PDO and lastly one for each child FDO. I do the ExternalNaming for the
child FDO by IRP_MN_START_DEVICE of the last PnP IRP handler routine that
I mentioned. I found my child devices are visible to Win32 and I can do
things like read/write etc.

I have got succes upto this point. Now, I’m asking Gurus whether I’m on
the right track. Is there any possibility that any DO’s pointer become
stale? Or, am I missing any concept?

Thanks in advance.
Hakim

You are currently subscribed to ntdev as: xxxxx@epost.de
To unsubscribe send a blank email to %%email.unsub%%

3

I’m developing it for Windows2000 WDM driver.

rgds,
\H

I have no substantial experience in writing a bus driver (for w2k+ - I
assume you aren’t interested in writing a NT4 driver) but I think the
toaster example from DDK deals with your problem and could be a help for
you.

Regards
Volker

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of
> xxxxx@connecttech.com
> Sent: Tuesday, March 19, 2002 6:57 PM
> To: NT Developers Interest List
> Subject: [ntdev] Bus+Functional driver in the single driver
>
>
> Hi Gurus,
>
> We usally make a bus driver for the multifunction device and then use a
> functional driver for each of the child PDO.
>
> I am looking for a design of a multifunction device that may not be an
> usual prctice. First, I make the usual bus driver and create the child
> devices. Then I want to make the bus driver to act as a Functional driver
> for each of the child devices it has created. To do this I mention the
> same driver for the child device in its inf to load. I found that it goes
> to the AddDevice routine where I can do those stuff for this new
> PhysicalDeviceObject, I have made a global counter and list so that right
> things will be done for multifunction and its child devices. Once I’m here
> I’m routing all the PnP IRP’s to the related routine that handles PNP IRP
> for the child’s functional DOs. Now, I have three sets of PnP IRP handler
> routines, that is, one for the multifunction device, one for each child
> PDO and lastly one for each child FDO. I do the ExternalNaming for the
> child FDO by IRP_MN_START_DEVICE of the last PnP IRP handler routine that
> I mentioned. I found my child devices are visible to Win32 and I can do
> things like read/write etc.
>
> I have got succes upto this point. Now, I’m asking Gurus whether I’m on
> the right track. Is there any possibility that any DO’s pointer become
> stale? Or, am I missing any concept?
>
> Thanks in advance.
> Hakim
>
> —
> You are currently subscribed to ntdev as: xxxxx@epost.de
> To unsubscribe send a blank email to %%email.unsub%%

4

Yes. Then the toaster example from W2k or XP DDK
(%DDKPATH%\src\general\toaster) should be right for you. As far as I can
remember there was a whitepaper explaining this example but unfortunately I
can’t find it on microsofts web sites today.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@connecttech.com
Sent: Wednesday, March 20, 2002 12:19 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bus+Functional driver in the single driver

I’m developing it for Windows2000 WDM driver.

rgds,
\H

> I have no substantial experience in writing a bus driver (for w2k+ - I
> assume you aren’t interested in writing a NT4 driver) but I think the
> toaster example from DDK deals with your problem and could be a help for
> you.
>
> Regards
> Volker
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > xxxxx@connecttech.com
> > Sent: Tuesday, March 19, 2002 6:57 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Bus+Functional driver in the single driver
> >
> >
> > Hi Gurus,
> >
> > We usally make a bus driver for the multifunction device and
then use a
> > functional driver for each of the child PDO.
> >
> > I am looking for a design of a multifunction device that may not be an
> > usual prctice. First, I make the usual bus driver and create the child
> > devices. Then I want to make the bus driver to act as a
Functional driver
> > for each of the child devices it has created. To do this I mention the
> > same driver for the child device in its inf to load. I found
that it goes
> > to the AddDevice routine where I can do those stuff for this new
> > PhysicalDeviceObject, I have made a global counter and list
so that right
> > things will be done for multifunction and its child devices.
Once I’m here
> > I’m routing all the PnP IRP’s to the related routine that
handles PNP IRP
> > for the child’s functional DOs. Now, I have three sets of PnP
IRP handler
> > routines, that is, one for the multifunction device, one for
each child
> > PDO and lastly one for each child FDO. I do the ExternalNaming for the
> > child FDO by IRP_MN_START_DEVICE of the last PnP IRP handler
routine that
> > I mentioned. I found my child devices are visible to Win32
and I can do
> > things like read/write etc.
> >
> > I have got succes upto this point. Now, I’m asking Gurus
whether I’m on
> > the right track. Is there any possibility that any DO’s pointer become
> > stale? Or, am I missing any concept?
> >
> > Thanks in advance.
> > Hakim
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@epost.de
> > To unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to ntdev as: xxxxx@epost.de
To unsubscribe send a blank email to %%email.unsub%%

5

> Yes. Then the toaster example from W2k or XP DDK

(%DDKPATH%\src\general\toaster) should be right for you.

I read it and but it did not help me since it is doing the usual way of
creating bus and function driver separately.

As far as I can
remember there was a whitepaper explaining this example but unfortunately I
can’t find it on microsofts web sites today.

If anybody has that article or link please let me know.

Thanks,
H

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of
> xxxxx@connecttech.com
> Sent: Wednesday, March 20, 2002 12:19 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Bus+Functional driver in the single driver
>
>
> I’m developing it for Windows2000 WDM driver.
>
> rgds,
> \H
>
> > I have no substantial experience in writing a bus driver (for w2k+ - I
> > assume you aren’t interested in writing a NT4 driver) but I think the
> > toaster example from DDK deals with your problem and could be a help for
> > you.
> >
> > Regards
> > Volker
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > xxxxx@connecttech.com
> > > Sent: Tuesday, March 19, 2002 6:57 PM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Bus+Functional driver in the single driver
> > >
> > >
> > > Hi Gurus,
> > >
> > > We usally make a bus driver for the multifunction device and
> then use a
> > > functional driver for each of the child PDO.
> > >
> > > I am looking for a design of a multifunction device that may not be an
> > > usual prctice. First, I make the usual bus driver and create the child
> > > devices. Then I want to make the bus driver to act as a
> Functional driver
> > > for each of the child devices it has created. To do this I mention the
> > > same driver for the child device in its inf to load. I found
> that it goes
> > > to the AddDevice routine where I can do those stuff for this new
> > > PhysicalDeviceObject, I have made a global counter and list
> so that right
> > > things will be done for multifunction and its child devices.
> Once I’m here
> > > I’m routing all the PnP IRP’s to the related routine that
> handles PNP IRP
> > > for the child’s functional DOs. Now, I have three sets of PnP
> IRP handler
> > > routines, that is, one for the multifunction device, one for
> each child
> > > PDO and lastly one for each child FDO. I do the ExternalNaming for the
> > > child FDO by IRP_MN_START_DEVICE of the last PnP IRP handler
> routine that
> > > I mentioned. I found my child devices are visible to Win32
> and I can do
> > > things like read/write etc.
> > >
> > > I have got succes upto this point. Now, I’m asking Gurus
> whether I’m on
> > > the right track. Is there any possibility that any DO’s pointer become
> > > stale? Or, am I missing any concept?
> > >
> > > Thanks in advance.
> > > Hakim
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@epost.de
> > > To unsubscribe send a blank email to %%email.unsub%%
>
> —
> You are currently subscribed to ntdev as: xxxxx@epost.de
> To unsubscribe send a blank email to %%email.unsub%%

6

You can combine bus and function driver, but I suggest not doing so.
The complexity of managing ‘three hats’ in one combined bus/function
driver argues against such an implementation. If the concern is the
communication overhead of the separate function driver/bus driver, then
I think the solution is using a private (function call) interface.

On the other hand, having implemented such a driver, it certainly can be
done. You might have whql problems.

=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@connecttech.com
Sent: Tuesday, March 19, 2002 7:04 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bus+Functional driver in the single driver

> Yes. Then the toaster example from W2k or XP DDK
> (%DDKPATH%\src\general\toaster) should be right for you.

I read it and but it did not help me since it is doing the
usual way of creating bus and function driver separately.

> As far as I can
> remember there was a whitepaper explaining this example but
> unfortunately I can’t find it on microsofts web sites today.

If anybody has that article or link please let me know.

Thanks,
H

> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > xxxxx@connecttech.com
> > Sent: Wednesday, March 20, 2002 12:19 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: Bus+Functional driver in the single driver
> >
> >
> > I’m developing it for Windows2000 WDM driver.
> >
> > rgds,
> > \H
> >
> > > I have no substantial experience in writing a bus
driver (for w2k+
> > > - I assume you aren’t interested in writing a NT4 driver) but I
> > > think the toaster example from DDK deals with your problem and
> > > could be a help for you.
> > >
> > > Regards
> > > Volker
> > >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > > xxxxx@connecttech.com
> > > > Sent: Tuesday, March 19, 2002 6:57 PM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Bus+Functional driver in the single driver
> > > >
> > > >
> > > > Hi Gurus,
> > > >
> > > > We usally make a bus driver for the multifunction device and
> > then use a
> > > > functional driver for each of the child PDO.
> > > >
> > > > I am looking for a design of a multifunction device
that may not
> > > > be an usual prctice. First, I make the usual bus driver and
> > > > create the child devices. Then I want to make the bus
driver to
> > > > act as a
> > Functional driver
> > > > for each of the child devices it has created. To do this I
> > > > mention the same driver for the child device in its
inf to load.
> > > > I found
> > that it goes
> > > > to the AddDevice routine where I can do those stuff
for this new
> > > > PhysicalDeviceObject, I have made a global counter and list
> > so that right
> > > > things will be done for multifunction and its child devices.
> > Once I’m here
> > > > I’m routing all the PnP IRP’s to the related routine that
> > handles PNP IRP
> > > > for the child’s functional DOs. Now, I have three sets of PnP
> > IRP handler
> > > > routines, that is, one for the multifunction device, one for
> > each child
> > > > PDO and lastly one for each child FDO. I do the
ExternalNaming
> > > > for the child FDO by IRP_MN_START_DEVICE of the last PnP IRP
> > > > handler
> > routine that
> > > > I mentioned. I found my child devices are visible to Win32
> > and I can do
> > > > things like read/write etc.
> > > >
> > > > I have got succes upto this point. Now, I’m asking Gurus
> > whether I’m on
> > > > the right track. Is there any possibility that any
DO’s pointer
> > > > become stale? Or, am I missing any concept?
> > > >
> > > > Thanks in advance.
> > > > Hakim
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > > > xxxxx@epost.de To unsubscribe send a blank email to
> > > > %%email.unsub%%
> >
> > —
> > You are currently subscribed to ntdev as:
xxxxx@epost.de To
> > unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%

7

Thanks for your suggestion. My concern is that I’ll have 128 devices
created by the bus driver. Could you please give me some reference where I
can get info from DDK or books about this private (function call)
interface. Do you mean it to be callback objects? I’m in this field for
less than one year.

Thanks.
Hakim

You can combine bus and function driver, but I suggest not doing so.
The complexity of managing ‘three hats’ in one combined bus/function
driver argues against such an implementation. If the concern is the
communication overhead of the separate function driver/bus driver, then
I think the solution is using a private (function call) interface.

On the other hand, having implemented such a driver, it certainly can be
done. You might have whql problems.

=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@connecttech.com
> Sent: Tuesday, March 19, 2002 7:04 PM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Bus+Functional driver in the single driver
>
>
>
> > Yes. Then the toaster example from W2k or XP DDK
> > (%DDKPATH%\src\general\toaster) should be right for you.
>
> I read it and but it did not help me since it is doing the
> usual way of creating bus and function driver separately.
>
> > As far as I can
> > remember there was a whitepaper explaining this example but
> > unfortunately I can’t find it on microsofts web sites today.
>
> If anybody has that article or link please let me know.
>
> Thanks,
> H
>
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > xxxxx@connecttech.com
> > > Sent: Wednesday, March 20, 2002 12:19 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] RE: Bus+Functional driver in the single driver
> > >
> > >
> > > I’m developing it for Windows2000 WDM driver.
> > >
> > > rgds,
> > > \H
> > >
> > > > I have no substantial experience in writing a bus
> driver (for w2k+
> > > > - I assume you aren’t interested in writing a NT4 driver) but I
> > > > think the toaster example from DDK deals with your problem and
> > > > could be a help for you.
> > > >
> > > > Regards
> > > > Volker
> > > >
> > > > > -----Original Message-----
> > > > > From: xxxxx@lists.osr.com
> > > > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > > > xxxxx@connecttech.com
> > > > > Sent: Tuesday, March 19, 2002 6:57 PM
> > > > > To: NT Developers Interest List
> > > > > Subject: [ntdev] Bus+Functional driver in the single driver
> > > > >
> > > > >
> > > > > Hi Gurus,
> > > > >
> > > > > We usally make a bus driver for the multifunction device and
> > > then use a
> > > > > functional driver for each of the child PDO.
> > > > >
> > > > > I am looking for a design of a multifunction device
> that may not
> > > > > be an usual prctice. First, I make the usual bus driver and
> > > > > create the child devices. Then I want to make the bus
> driver to
> > > > > act as a
> > > Functional driver
> > > > > for each of the child devices it has created. To do this I
> > > > > mention the same driver for the child device in its
> inf to load.
> > > > > I found
> > > that it goes
> > > > > to the AddDevice routine where I can do those stuff
> for this new
> > > > > PhysicalDeviceObject, I have made a global counter and list
> > > so that right
> > > > > things will be done for multifunction and its child devices.
> > > Once I’m here
> > > > > I’m routing all the PnP IRP’s to the related routine that
> > > handles PNP IRP
> > > > > for the child’s functional DOs. Now, I have three sets of PnP
> > > IRP handler
> > > > > routines, that is, one for the multifunction device, one for
> > > each child
> > > > > PDO and lastly one for each child FDO. I do the
> ExternalNaming
> > > > > for the child FDO by IRP_MN_START_DEVICE of the last PnP IRP
> > > > > handler
> > > routine that
> > > > > I mentioned. I found my child devices are visible to Win32
> > > and I can do
> > > > > things like read/write etc.
> > > > >
> > > > > I have got succes upto this point. Now, I’m asking Gurus
> > > whether I’m on
> > > > > the right track. Is there any possibility that any
> DO’s pointer
> > > > > become stale? Or, am I missing any concept?
> > > > >
> > > > > Thanks in advance.
> > > > > Hakim
> > > > >
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > > > > xxxxx@epost.de To unsubscribe send a blank email to
> > > > > %%email.unsub%%
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> xxxxx@epost.de To
> > > unsubscribe send a blank email to %%email.unsub%%
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> %%email.unsub%%
>
>
>

8

See IRP_MN_QUERY_INTERFACE.

=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@connecttech.com
Sent: Thursday, March 21, 2002 6:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bus+Functional driver in the single driver

Thanks for your suggestion. My concern is that I’ll have 128
devices created by the bus driver. Could you please give me
some reference where I can get info from DDK or books about
this private (function call) interface. Do you mean it to be
callback objects? I’m in this field for less than one year.

Thanks.
Hakim

> You can combine bus and function driver, but I suggest not
doing so.
> The complexity of managing ‘three hats’ in one combined
bus/function
> driver argues against such an implementation. If the concern is the
> communication overhead of the separate function driver/bus driver,
> then I think the solution is using a private (function call)
> interface.
>
> On the other hand, having implemented such a driver, it
certainly can
> be done. You might have whql problems.
>
> =====================
> Mark Roddy
> Windows XP/2000/NT Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com
> xxxxx@hollistech.com
> For Windows Device Driver Training: see www.azius.com
>
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of
> > xxxxx@connecttech.com
> > Sent: Tuesday, March 19, 2002 7:04 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] RE: Bus+Functional driver in the single driver
> >
> >
> >
> > > Yes. Then the toaster example from W2k or XP DDK
> > > (%DDKPATH%\src\general\toaster) should be right for you.
> >
> > I read it and but it did not help me since it is doing the
> > usual way of creating bus and function driver separately.
> >
> > > As far as I can
> > > remember there was a whitepaper explaining this example but
> > > unfortunately I can’t find it on microsofts web sites today.
> >
> > If anybody has that article or link please let me know.
> >
> > Thanks,
> > H
> >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > > xxxxx@connecttech.com
> > > > Sent: Wednesday, March 20, 2002 12:19 AM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] RE: Bus+Functional driver in the
single driver
> > > >
> > > >
> > > > I’m developing it for Windows2000 WDM driver.
> > > >
> > > > rgds,
> > > > \H
> > > >
> > > > > I have no substantial experience in writing a bus
> > driver (for w2k+
> > > > > - I assume you aren’t interested in writing a NT4
driver) but
> > > > > I think the toaster example from DDK deals with
your problem
> > > > > and could be a help for you.
> > > > >
> > > > > Regards
> > > > > Volker
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: xxxxx@lists.osr.com
> > > > > > [mailto:xxxxx@lists.osr.com]On Behalf Of
> > > > > > xxxxx@connecttech.com
> > > > > > Sent: Tuesday, March 19, 2002 6:57 PM
> > > > > > To: NT Developers Interest List
> > > > > > Subject: [ntdev] Bus+Functional driver in the
single driver
> > > > > >
> > > > > >
> > > > > > Hi Gurus,
> > > > > >
> > > > > > We usally make a bus driver for the multifunction
device and
> > > > then use a
> > > > > > functional driver for each of the child PDO.
> > > > > >
> > > > > > I am looking for a design of a multifunction device
> > that may not
> > > > > > be an usual prctice. First, I make the usual bus
driver and
> > > > > > create the child devices. Then I want to make the bus
> > driver to
> > > > > > act as a
> > > > Functional driver
> > > > > > for each of the child devices it has created. To do this I
> > > > > > mention the same driver for the child device in its
> > inf to load.
> > > > > > I found
> > > > that it goes
> > > > > > to the AddDevice routine where I can do those stuff
> > for this new
> > > > > > PhysicalDeviceObject, I have made a global
counter and list
> > > > so that right
> > > > > > things will be done for multifunction and its
child devices.
> > > > Once I’m here
> > > > > > I’m routing all the PnP IRP’s to the related routine that
> > > > handles PNP IRP
> > > > > > for the child’s functional DOs. Now, I have three sets of
> > > > > > PnP
> > > > IRP handler
> > > > > > routines, that is, one for the multifunction
device, one for
> > > > each child
> > > > > > PDO and lastly one for each child FDO. I do the
> > ExternalNaming
> > > > > > for the child FDO by IRP_MN_START_DEVICE of the
last PnP IRP
> > > > > > handler
> > > > routine that
> > > > > > I mentioned. I found my child devices are visible to Win32
> > > > and I can do
> > > > > > things like read/write etc.
> > > > > >
> > > > > > I have got succes upto this point. Now, I’m asking Gurus
> > > > whether I’m on
> > > > > > the right track. Is there any possibility that any
> > DO’s pointer
> > > > > > become stale? Or, am I missing any concept?
> > > > > >
> > > > > > Thanks in advance.
> > > > > > Hakim
> > > > > >
> > > > > > —
> > > > > > You are currently subscribed to ntdev as:
> > > > > > xxxxx@epost.de To unsubscribe send a
blank email to
> > > > > > %%email.unsub%%
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > xxxxx@epost.de To
> > > > unsubscribe send a blank email to %%email.unsub%%
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@hollistech.com To unsubscribe send a blank email to
> > %%email.unsub%%
> >
> >
> >

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%