Hi Larry
On Thu, Feb 03, 2011 at 10:16:18PM -0600, Larry Finger wrote:
> >> +static int _usbctrl_vendorreq_async_write(struct usb_device *udev, u8 request,
> >> + u16 value, u16 index, void *pdata,
> >> + u16 len, u8 requesttype)
> >> +{
> >> + int rc;
> >> + unsigned int pipe;
> >> + u8 reqtype;
> >> + struct usb_ctrlrequest *dr;
> >> + struct urb *urb;
> >> + struct rtl819x_async_write_data {
> >> + u8 data[REALTEK_USB_VENQT_MAX_BUF_SIZE];
> >> + struct usb_ctrlrequest dr;
> >> + } *buf;
> >> +
> >> + if (requesttype == VENDOR_READ) {
> >> + pipe = usb_rcvctrlpipe(udev, 0); /* read_in */
> >> + reqtype = REALTEK_USB_VENQT_READ;
> > This is not needed, or function should be named differently not _async_write.
>
> This one I do not understand. The function does do an asynchronous write. Please
> explain.
If function do "write", then requesttype argument should be removed, and
dr->bRequestType = REALTEK_USB_VENQT_WRITE should be hardcoded.
> >> + wvalue = (u16)(addr&0x0000ffff);
> >> + _usbctrl_vendorreq_sync(udev, request, wvalue, index, data, len,
> >> + requesttype);
> >> + ret = (le32_to_cpu(*data) & (0xffffffff >> ((4 - len) * 8)));
> > Ok, BYTEMASK can be used, but what mean this magic?
>
> As the output of this routine is always cast with (u8) when len is 1 and (u16)
> when len is 2, I think the magic can just disappear and ret can simply be
>
> ret = le32_to_cpu(*data);
Good.
> I will test and have contacted the original author. There is similar magic in
> _usb_write_async() that can also disappear.
>
> >> +
> >> + /* IBSS */
> >> + mac->beacon_interval = 100;
> >> +
> >> + /* AMPDU */
> >> + mac->min_space_cfg = 0;
> >> + mac->max_mss_density = 0;
> > Spaces.
>
> Please explain what you mean by "spaces".
I guess I should wrote "indention". On that lines, there in one space
after tab :-)
Thanks for working on my remarks.
Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
