Re: Device Driver - Direct Access to Endpoint 0
- From: "Ashish Sharma" <ashish.sharma@xxxxxxxxxxxxx>
- Date: Thu, 1 Sep 2005 15:06:55 +0530
Thanks for the reply
It looks like UsbBuildVendorRequest can be used to define
URB_CONTROL_VENDOR_OR_CLASS_REQUEST.
But I have some specific questions about the few attributes that should be
defined in UsbBuildVendorRequest to send requests to Endpoint 0.
VOID UsbBuildVendorRequest( IN USHORT Function, IN USHORT Index,
.... );
1) Function : What should be the value of this function? Will
URB_FUNCTION_VENDOR_DEVICE work?
2) Index : Should this value be equal to 0 for accessing Endpoint 0?
MSDN says:
Specifies the device-defined identifier if the request is for an endpoint,
interface, or device-defined target. Otherwise, Index must be zero.
In the firmware, we have defined End Point 0 for the below extra
functionalities:
1. To receive the LED information. This information comes after SET report
request (=12) from host.
2. To receive the buzzer information. This information comes after SET
report request (=12) from host.
Bye,
Ashish
"Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uleCIHkrFHA.4044@xxxxxxxxxxxxxxxxxxxxxxx
> _URB_CONTROL_VENDOR_OR_CLASS_REQUEST will do waht you want.
>
> d
>
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Ashish Sharma" <ashish.sharma@xxxxxxxxxxxxx> wrote in message
> news:%23bOoN0irFHA.2072@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi All,
> >
> > I have made a USB functional driver and it is stacked on top of "usb bus
> > driver" & "usb host controller driver".
> > It uses the services of the lower driver(s) to access descriptors and
> > activate the selected interface.
> >
> > We plan to use endpoint 0 (control type) for some function specific
WRITE
> > functionality (like beep buzzer, blink error LED)
> >
> > Is it possible for the functional driver to directly access endpoint 0?
I
> > could not find any DDK calls that can allow this access.
> >
> > Thanks
> > Ashish
> >
> >
> >
>
>
.
- References:
- Re: Device Driver - Direct Access to Endpoint 0
- From: Doron Holan [MS]
- Re: Device Driver - Direct Access to Endpoint 0
- Prev by Date: Unable to remove USB-based AVStream Device safely
- Next by Date: debugging the cause of an NMI
- Previous by thread: Re: Device Driver - Direct Access to Endpoint 0
- Next by thread: Re: Asynchronous IRP and ISR
- Index(es):
Relevant Pages
|
