Re: user-defined ioctl handling

Tech-Archive recommends: Speed Up your PC by fixing your registry

hi K. S. Huang,

Very thanks for your reply. I used "ndisuio" but when i use user-defined
ioctls in the application, i am getting error "ioctl not supported". So
please tell me how to make the passthru as a dual interface driver (NDIS and
Stream Interface)? Is there any registry settings to be changed? or any
environment varible has to be set?

regards,
brahma.

"K. S. Huang" wrote:

While ndis passthru is a NDIS driver that will not have a regular stream
interface, and that means there is NO corresponding XXX_IoControl handler
there.
You could make the passthru as a dual interface driver (NDIS and Stream
Interface) so that you could use the Stream Interface for passing your
customer IOCTLs down.
Another apporach might be defined the IOCTL as your private owned OIDs, and
you could still access the passthru driver via NDISUIO with Set/QueeryInfo
handler.

"brahma" <brahma@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8944277A-57C7-4104-B7E4-486C515F0810@xxxxxxxxxxxxxxxx
hi san,

Thanks for your replay. But in wince 5.0 which routine is called in the
passthru driver when the application sends an ioctl(user-defined)? and how
to
register that(ie., ioctl rotine) routine? i think there is no direct
routine
as such. So i'm using "ndisuio". But in this also i'm getting problems
with
user defined ioctls. So Please tell me any solution to this.

thanQ.

"san" wrote:

brahma,

You have to define your own IOCTL constants and using the switch case you
can define the functionality. The same constants is used from the upper
layer
or other compoents to communicate with your driver.

"brahma" wrote:

hi all,

I'm working on NDIS PASSTHRU driver in wince 5.0. Could anyone tell me
how
to handle the user-defined ioctls in the driver?

thanQ,

regards,
brahma.



.

Relevant Pages

  • Re: ioctl number 0xF3
    ... > The interface I intend to use matches the one the X driver has (using ... > the Xv extension as an ioctl replacement) and will be documented. ... > I develope both the SiS kernel framebuffer driver as well as the SiS X ... use as few ioctls as possible so that you can control/verify the changes ...
    (Linux-Kernel)
  • Re: ioctl number 0xF3
    ... I didn't mean that as any sort of insult. ... people telling me "implement a generic interface". ... driver and want the users of this driver to have some sort of comfort. ... intended ioctls already implemented. ...
    (Linux-Kernel)
  • Re: Accessing Ndis miniport from user mode application-one more thing
    ... IOCTLs, so I believe we're in agreement there. ... send control requests to your driver (and I believe one normally has a good ... "Please make sure that UDP port XYZ is available only to privileged users", ...
    (microsoft.public.development.device.drivers)
  • Re: ioctls, etc. (was Re: [PATCH 1/4] sas: add flag for locally attached PHYs)
    ... > ioctls represent the most direct, ... > potentially a few levels down a driver stack. ... sysfs, since its normal ASCII ... This entirely depends on the interface you define. ...
    (Linux-Kernel)
  • Re: CE6.0 Exposing Driver Interfaces to an Application
    ... complicated mechanism is to create a simple stream driver and expose your ... for *kernel* ioctls, not device driver ioctls. ... components can call device driver ioctls though. ...
    (microsoft.public.windowsce.platbuilder)