GitHub PushEvent at 2014-06-25 04:36:57
Repository: libdivecomputer
Actor: venkateshshukla
Payload: {"shas":[["429647ab54701d1e6240bea55690aefe7a27aef6","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Corrected include statement for ftdi.h\n\nUse libusb.h instead of libusb-1.0/libusb.h\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["3d71f38fe09084491d1bdb39ce16a11d346c0024","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Corrections in serial_open and serial_set_timeout\n\nftdi_context->timeout is the timeout used while libusb_bulk_transfer.\nOn the other hand, libdivecomputer context is used internally by\nlibdivecomputer. So inappropriate to set both here. By default libftdi\nsets a timeout of 5000 ms on both read and write.\n\nUsage of struct ftdi_context was wrong. Fixed it.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["034a07cf8c4300cfbcda850fdfbbbfc0e172c459","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Finally a working version. Try again on no data.\n\nftdi_read_data returns 0 if no data is received from\nthe device. The existing code understood it as timeout errror.\nRemoving this check might end up in an infinite loop. But it works\nin OSTC3. This should be checked further.\nCross compilation of libdivecomputer on android and running it\ngives the results same as the ones on pc.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["d50df99c5db9f9233d61fbaae3a78184ffb355dc","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Check multiple pids while opening device\n\nlibftdi returns -3 when it could not find any device corresponding to\nthe pid and vid given. (Different from -3 of libusb which means you do\nnot have permissions to access the device)\nUsing this value, check among a list of accepted pids. VID is that of\nftdi ( file is called serial_ftdi :)\nThere is a problem when multiple devices are connected. It uses the\nfirst one it can find in the list. This might not be correct always.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["0905ce0641ad58709452532f2fb65708d711c58d","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Added custom pids of divecomputers\n\nSome divecomputer manufacturers use custom pid for their ftdi chips.\nSome of them are Cressi (Leonardo), Suunto and Oceanic.\nThese are added to accepted_pids.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["87c298efc1aa13920335ed094b238c099b31bee8","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","Again changed to pass usb file descriptor\n\nAs experiments continue, I visit this technique again.\nBut instead of using the file descriptor as tty device,\nnow using it to make a libusb_device. This could help us\nin talking with the usb device after appropriate permissions\nare taken. Crossed fingers.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true],["949197e6dbc3be8b8eb614462099161152d60e00","8349e50bec2939976da648e286d7e261bcd17fa3@iitbhu.ac.in","libftdi1 in pkg-config when building for android\n\nIf you are building for android, you would need libftdi package.\nHence add this in Required.private so that it may be included\nautomatically while cross compilation.\n\nSigned-off-by: Venkatesh Shukla <venkatesh.shukla.eee11@iitbhu.ac.in>","Venkatesh Shukla",true]],"size":7,"ref":"refs/heads/android-experiments","head":"949197e6dbc3be8b8eb614462099161152d60e00"}