> On Friday 10 of April 2009 15:49:43 Leahy, Chris M. (Xetron) wrote:
> > Having the ftdi_usb_open_dev() after ftdi_usb_get_strings() makes
more
> > sense.
> > The usb_dev should be open after Context::open finishes in that
case.
> > Do you need to call ftdi_usb_get_strings() in Context::open?
> >
> > Chris
>
> Hi Chris,
>
> just to let you know, I have finally made some free time and
> sent two patches for review. Example test passes, so it seems
> figured out, thanks!
>
> I have proposed ftdipp as a bit higher-level API, so
> populating description strings automatically at no
> significant cost seems fine to me, do you have any specific use case?
>
> Marek
>
I'm currently using Hal to find ftdi devices using vid/pid and then
using
the ftdi device in MPSSE mode. So I populating description strings makes
no
difference to me.
The patch looks good.
Chris
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
