[Jun Sun <[email protected]>] > > BTW, from what you were saying, it seems the usb functions are > composite-able. That is interesting.
Yup -- that was the major goal of the function framework -- to be able to combine an arbitary set of functions together (on the fly!). The gadget framework has since provided more support for composite client devices, so we're in the process of migrating our USB work there for post-cupcake development. Brian > On Tue, Jan 20, 2009 at 11:17:27PM -0800, Brian Swetland wrote: > > > > You're going to have to configure the function to be included in the usb > > composite device (look in board-trout.c), and probably will have to > > modify the VID/PID to match one your desktop linux kernel associates > > with the "simple" ethernet profile. > > > > Also, I've found that having other interfaces (like adb) present tends > > to confuse the host driver (which assumes that *all* interfaces are > > ethernet interfaces). > > > > I have successfully used this driver with several different desktop > > linux systems, but things are not rigged up so simply including the > > driver in the build gets it all going. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
