libftdi Archives

Subject: Re: Provide API access to decoded EEPROM structure

From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Fri, 15 Oct 2010 10:16:44 +0200
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
> ftdi_context

Same vote here:

I guess we did everything right (or are on the way to do it right ;))


libftdi - see for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread