Hi, I have checked the driver framework in urjtag, and has made necessary change to Versaloon. The driver to Versaloon will be implemented soon. Question below will not affect how I implement the driver but will affect how I arrange the codes.
Should I put everything in one file named maybe "vsllink.c"? Or can I add a directory for generic Versaloon drivers? I ask this question because in the coming OpenOCD 0.5.0, support to SWD, SPI and so on will be added. So I put different driver in different files(and if implemented in urjtag, no change is needed for these files): versaloon.c ---- generic driver layer for versaloon usbtoxxx\usbtoxxx.c ---- dirver layer for USB_TO_XXX protocol usbtoxxx\usbtogpio.c ---- gpio driver, for SRST and TRST control usbtoxxx\usbtojtagraw.c ---- jtag driver ..... And there is a vsllink.c in OpenOCD driver directory, it simply calls the generic dirver layer for different operations through a generic driver struct. Acutally USB_TO_XXX protocol implemented in Versaloon is a generic dongle protocol supporting many interfaces including JTAG, SWD, SPI, IIC, GPIO, DelayControl, PowerOutputControl, SWIM(for STM8) and so on. 2010/8/15 Mike Frysinger <[email protected]> > On Sat, Aug 14, 2010 at 5:30 AM, simon qian wrote: > > Does UrJTAG accept drivers for 3-rd party tools? > > of course > > > Can I provide the driver in diff patch format? > > unified diff to the mailing list > -mike > -- Best Regards, SimonQian http://www.SimonQian.com
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
