On Wed, Aug 11, 2010 at 11:59 AM, Matthieu CASTET <matthieu.castet@xxxxxxxxxx> wrote: > It is best to solve in usb driver, because for example in Asix case the > driver already do copy (see asix_rx_fixup/asix_tx_fixup). > Yes, however those functions are only called for devices which register them. Looking at the driver_info and product id tables shows that it's only a subset of the devices that asix supports (88772 and 88178 chips) In fact my hardware _is_ included // DLink DUB-E100 H/W Ver B1 Alternate USB_DEVICE (0x2001, 0x3c05), .driver_info = (unsigned long) &ax88772_info, but fixing this in asix_rx_fixup wouldn't solve it for the other supported devices. It seems to me these fixup functions are not intended to solve alignment issues but rather implement device specific framing (such as when the hardware packs multiple ethernet frames into a single urb) > PS : what hcd driver do you use ? imx21_hcd Martin -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
