On Thursday 17 May 2007, Hans Petter Selasky wrote:
>
> I would like introduce a new USB API call, so that my pre-allocate model will
> work better with your USB API. For example I want something like this:
>
> void
> usb_setup_endpoint(struct usb_device *usb, struct usb_interface *ui, struct
> usb_host_endpoint *uhe, uint32_t bufsize, uint32_t unused0, uint32_t unused1,
> uint32_t unused2);
The usb_device and usb_interface are implied by the usb_host_endpoint,
and "unused" parameters are pointless. Sizes are "size_t", and such
a call could obviously fail because of invalid parameters. So
int usb_setup_endpoint(struct usb_host_endpoint *hep, size_t bufsize);
What would such a call do, though? Who would use it, and why?
> On FreeBSD this function will pre-allocate one or two USB transfers for an
> endpoint using the given "bufsize" argument. Those FreeBSD USB transfers will
> then be used to do all the Linux USB transfers. This function can block and
> must have a context.
So what's the model ... GPL'd Linux drivers will be modified to
incorporate that call, so they'd work better on FreeBSD?
- Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
