libftdi Archives

Subject: Re: Provide API access to decoded EEPROM structure

From: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Cc: Mike Frysinger <vapier@xxxxxxxxxx>
Date: Mon, 4 Oct 2010 18:11:18 +0200
>>>>> "Thomas" == Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> writes:

    Thomas> On Saturday, 2. October 2010 17:32:15 Uwe Bonnes wrote:
    >> Hello,
    >> to ease API/ABI stability with future extensions, appended patch
    >> provides ftdi_get|set_eeprom_value and ftdi_get_eeprom_buf to get a
    >> copy of the
    ftdi-> eeprom->buf content.
    >>  Is this the way to go with access to struct ftdi members too?

    Thomas> Reviewed, spell checked and applied :)

    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

Uwe Bonnes                bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

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

Current Thread