On Monday 03 April 2006 5:32 am, Ethan Du wrote: > > > > The only difference is ECM extended a data class > > > interface. EEM doesn't. Is this the benefit of EEM? And is it more > > > efficient using less interfaces? > > > >If you look at EEM, it's clearly a bit less demanding than ECM in terms of > >hardware; it can work without altsettings. (The interrupt/status endpoint > >is optional for ECM.) Which means there's more choice for peripheral > >hardware. > > > > Do you mean EEM is saving endpoints?
No; as I said, it's less demanding because it doesn't need altsettings. > Or could you explain the relationship > between altsettings and hardware. There's no need for such a relationship, but some controllers try to move such software policies into the hardware. Examples include the pxa25x and pxa27x controllers from Intel, both of which make it quite painful (or impossible) to use altsettings. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
