Hi Clive,
On Friday, 7. November 2014 17:25:31 Clive Stubbings wrote:
> 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.
please don't top post :)
I'd prefer to skip the patch for this release since I'm not 100% sure
about the implications it will have. So let's have a "safe" release
first and then we'll look for a solution to your problem in the next release.
IMHO that's what you also suggested.
Cheers,
Thomas
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|