On Dec 30, 2007 12:29 PM, mgross <[EMAIL PROTECTED]> wrote: > The device ID's are different 0x000C in ldusb.c vrs 0x000b in the > driver I just posted.
I know that. 000b is for the demo application. 000c is for the bootloader application. I am not a progammer myself but I think the USB communication part of both the two libusb based application are fine. I have no comments about the other part of fsusb coce. http://forum.microchip.com/tm.aspx?m=106426 > > Please do not add it to the kernel. There are libusb based application > > for both the bootloader and the demo application and both are working > > fine under Linux (along with Windows and I am trying to get FreeBSD > > working). > > The libusb based FW loader http://www.internetking.org/fsusb/ program > is nasty and didn't work on one of my systems, so I refactored it into > a kernel driver and python program. > If it does not work, read my patches and see if it will work. If you do not like the existing fsusb application, you can rewrite it in python with pyusb (which is based on libusb) but you do not need a kernel driver. pyusb: http://pyusb.berlios.de/ Hex file parsing in pyk by Mark Rages. He is using the Bitpim libusb wrapper which IMHO is not as good as pyusb. http://groups.google.com/group/pickit-devel/msg/35e850832256e890 Xiaofan - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
