On Sun, Jul 15, 2018 at 10:30:39PM +0200, Loic Poulain wrote:
> Hi Johan,
>
> Thanks for the review.
>
> On 10 July 2018 at 11:19, Johan Hovold wrote:
> > The CBUS configuration is stored in just a couple of words at a known
> > offset and could easily be retrieved without depending on the
Hi Johan,
Thanks for the review.
On 10 July 2018 at 11:19, Johan Hovold wrote:
> Hi,
>
> I finally found some time to dig into the ftdi eeprom handling.
>
> On Tue, Jun 26, 2018 at 02:54:48PM +0200, Loic Poulain wrote:
>> Most of FTDI's devices have an EEPROM which records FTDI devices
>>
Hi,
I finally found some time to dig into the ftdi eeprom handling.
On Tue, Jun 26, 2018 at 02:54:48PM +0200, Loic Poulain wrote:
> Most of FTDI's devices have an EEPROM which records FTDI devices
> configuration setting (e.g. the VID, PID, I/O config...) and user
> data. For example, FT232R and
Hi Johan,
On 29 June 2018 at 21:52, Ajay Gupta wrote:
> Hi Loic.
> Thanks for fixing comments. Looks good to me now.
>
> On 6/26/18, Loic Poulain wrote:
>> Most of FTDI's devices have an EEPROM which records FTDI devices
>> configuration setting (e.g. the VID, PID, I/O config...) and user
>>
Hi Loic.
Thanks for fixing comments. Looks good to me now.
On 6/26/18, Loic Poulain wrote:
> Most of FTDI's devices have an EEPROM which records FTDI devices
> configuration setting (e.g. the VID, PID, I/O config...) and user
> data. For example, FT232R and FTX chips have 128-byte and 2048-byte
Most of FTDI's devices have an EEPROM which records FTDI devices
configuration setting (e.g. the VID, PID, I/O config...) and user
data. For example, FT232R and FTX chips have 128-byte and 2048-byte
internal EEPROM respectively.
This patch adds support for FTDI EEPROM read/write via USB control
