libftdi Archives

Subject: Re: Provide API access to decoded EEPROM structure

From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Cc: Mike Frysinger <vapier@xxxxxxxxxx>
Date: Mon, 4 Oct 2010 18:00:50 +0200
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?

Reviewed, spell checked and applied :)

Now we can decide if we want prohibit direct access to the private parts
(by moving the ftdi_eeprom struct to a separate header file).

Though this will make the transition from libftdi 0.x to 1.x harder
than renaming just some eeprom variables. Opinions?


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

Current Thread