Prev: OEMUI and OEMUNI
Next: USBSTOR.SYS
From: Maxim S. Shatskih on 29 Aug 2005 15:11
Oh, I see. So, this is a METHOD_xxx_DIRECT IOCTL.

The allocate a piece of nonpaged memory, then IoAllocateMdl over it and
MmBuildMdlForNonPagedPool. Do not forget to free all this stuff in the
completion routine.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

"Angela Yan" <yanyan9(a)hotmail.com> wrote in message
news:u9WtlGLrFHA.904(a)tk2msftngp13.phx.gbl...
> Hi,
>
> The DDK says
>
> "IOCTL_HID_GET_FEATURE
> Output
> The Irp->MdlAddress member points to the requester-allocated output buffer
> that the HID class driver uses to return the feature report."
>
> So I presume if a upper device filter, such as firefly, were to send
> IOCTL_HID_GET_FEATURE to Hid miniDriver via HidClass, it should allocate the
> Irp->MdlAddress to the output feature report buffer. Am I correct?
>
> Thank you.
>
> Angela
>
>
>
> "Maxim S. Shatskih" <maxim(a)storagecraft.com> wrote in message
> news:ujljqAJrFHA.908(a)tk2msftngp13.phx.gbl...
> >> I want to know how should I allocate the feature report buffer to the
> >> Irp->MdlAddress?
> >> By using IoAllocateMdl()?
> >
> > No, use Irp->AssociatedIrp.SystemBuffer instead.
> >
> > --
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > maxim(a)storagecraft.com
> > http://www.storagecraft.com
> >
> >
>
>


First  |  Prev  | 
Pages: 1 2
Prev: OEMUI and OEMUNI
Next: USBSTOR.SYS