On 4/19/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Thu, 19 Apr 2007, Wael Adel wrote: > > > Sorry may be i just express what i want in a wrong way so again what i > > want is to load skeleton driver on my host computer side then make it > > communicate with my OMAP kit. > > > > so i think this could be the steps for using skeleton driver: > > 1) i should change the vendor id and product id to be like the id of my > kit. > > 2) mknod /dev/usb/my_dev_node -c 180 0 > > 3)in my user space application i can open (my_dev_node) > > then read or write > > > > is there anything missing or not? > > Nothing is missing on the host side. But you still have to do work on the > device side. Those OMAP kits don't program themselves. :-)
Dont worry man, i managed the gadget side well but i still have another question: suppose that i have 2 different applications on the host and both talks to the OMAP device so i can achieve this by making 2 device nodes with different minor numbers or what? i mean how can i make 2 applications on the host side talk to the same OMAP kit using the same skeleton driver? i can imagine this can be done by assigning different minor numbers or different endpoints for each application. so which choice should i make? thanks in advance. > Alan STern > > ------------------------------------------------------------------------- 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
