Subject: Re: Provide API access to decoded EEPROM structure
On Monday, 4. October 2010 18:11:18 Uwe Bonnes wrote:
> Thomas> Now we can decide if we want prohibit direct access to the
> Thomas> private parts (by moving the ftdi_eeprom struct to a separate
> Thomas> header file).
> Thomas> Though this will make the transition from libftdi 0.x to 1.x
> Thomas> harder than renaming just some eeprom variables. Opinions?
> My vote to prohibit direct access to the eeprom and also to struct
Same vote here: http://rusty.ozlabs.org/?p=140
I guess we did everything right (or are on the way to do it right ;))
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx