Hi Uwe,
If you had asked that 6months ago I could have been sure, but I think it was
probably an externel prom on a FT2232HL dev board. I've been back through my
notes at the time and was working with a couple of different units.
We are in the process of putting one on a design, so I'm expecting that to come
off the reel blank. But until the board comes back I won't be sure.
If you are uncomfortable with the change, feel free to sit on it and I'll harass
you if/when I see it again. I have a patched version here. However I seem to
remember posting the comment in the expectation it wouldn't be a one-off problem.
I'd also observe there are a number of other ways you could expose this field.
But one way or the other it should be accessible from the library, even if thats
through some extended-function call.
Cheers
Clive
On Fri, 7 Nov 2014, Uwe Bonnes wrote:
"Clive" == Clive Stubbings <clive.stubbings@xxxxxxxxxxxxx> writes:
...
Clive> I'm having a bit of difficulty talking to blank
Clive> eeproms. eeprom->size is not accessible from outside the library
Clive> and there seems to be no way to get the library to set it for
Clive> some devices.
What devices? Devices with external or internal EEPROM?
--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
