Follow-up Comment #4, patch #4330 (project avrdude):
"Markers" ... just a name for a generic mechanism. We can ensure that some
pattern is found in the input data; so we do so, and use that to flag the
data we might not otherwise be able to find.
Why libusb calls? Because libftbb wasn't sufficient, and since anyway it
relies on libusb to exist. In ftdi_usb_open() the use is just to find the
specified device. In fastcmd() the comment explains the issue: libftbb does
buffer flushes in a bad order, and the direct call is used to minimize the
amount of garbage sitting in the buffer (and maximize the amount of real
data).
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?4330>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
avrdude-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
