Re: Registering Interfaces
From: Alexander Grigoriev (alegr_at_earthlink.net)
Date: 07/21/04
- Next message: Dennis Burns: "Compile Errors when using usbioctl.h"
- Previous message: Alexander Grigoriev: "Re: Erratum in Walter Oney's book "Programming the MS Windows Driver Model" 2nd Ed."
- In reply to: Ben Geib: "Re: Registering Interfaces"
- Next in thread: Ben Geib: "RE: Registering Interfaces"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 21 Jul 2004 08:52:11 -0700
Register the interface without the reference string, but have the
application to append additional string to the interface name. This way the
appended string will still be passed to the driver, but now the application
makes the choice.
"Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
news:C20B325B-438A-4786-9A87-116AC0214D30@microsoft.com...
> Using different ReferenceStrings allows me to differentiate among channels
in the driver, but I want the application writer to have an easy way to
access a particular channel. Right now I'm calling
SetupDiEnumDeviceInterfaces in a loop and getting the deviceName from the
detail structure. However, I don't see an easy way the application writer
can open a handle and access a particular channel. Thank you for your time.
>
> "Alexander Grigoriev" wrote:
>
> > Use different ReferenceString arguments in IoRegisterDeviceInterface,
with
> > the same GUID.
> >
> > This argument will be passed to IRP_MJ_CREATE handler (in FILE_OBJECT as
> > file name), to distinguish one channel from another.
> >
> > "Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
> > news:A5A12D05-4E9A-4EFF-A546-C2BE4A16E2E3@microsoft.com...
> > > I am developing a driver for a PCI device that has multiple
communication
> > channels. In an attempt to have each channel opened and used
individually I
> > have tried registering an interface for each channel in the AddDevice
> > routine; that way a different handle may be used for each channel.
However,
> > enumeration of the interfaces in an application does not locate all of
those
> > registered in the driver. Should I even be using multiple interfaces or
> > should I name my device object and subdivide its namespace for each
channel?
> > Thank you for your time.
> >
> >
> >
- Next message: Dennis Burns: "Compile Errors when using usbioctl.h"
- Previous message: Alexander Grigoriev: "Re: Erratum in Walter Oney's book "Programming the MS Windows Driver Model" 2nd Ed."
- In reply to: Ben Geib: "Re: Registering Interfaces"
- Next in thread: Ben Geib: "RE: Registering Interfaces"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|