Follow-up Comment #12, bug #30559 (project avrdude):
Just for the record.
I don't think that merging them should be done "just because they use similar
chips".
If merging is done I think the reason should be: "Because they share a lot of
code".
For example, suppose the rasbperry pi board has an SPI port (it does), then
AVRDude might be able to program AVRs through that SPI port.
But suppose that the board also has general purpose IO pins (it does), then
AVRDude may be able to program AVRs through those GPIO pins. In fact, the SPI
pins can be configured and used as GPIO pins as well. So it can be said that
the same chip/board can switch between the hardware SPI and software
bitbanging on the same pins.
I think that conceptually they are different drivers and should not be merged
into one sourcefile.
A very similar thing is happening here: The mpsse module in the modern FTDI
chips can be used (one driver) or a different "module" of the chip (syncbb)
can be used (the other driver).
And just like the example of the raspberry pi board, the MPSSE mode cannot
allow pin assigments to be "random", while the bitbanging modes allow
(almost?) every combination of assignments of pins to functions.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?30559>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
avrdude-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
