by Bret » Sun Oct 04, 2009 10:17 am
USBUHCIL won't care what chip is involved. It will enumerate the Device, and let you "see" it and control it through the API.
However, the TD232R is a USB-to-UART (serial port) converter, so the way you request the data and the way it gets sent to you will be in a COMPLETELY different format than U-HID. I haven't written a driver for a USB-to-Serial converter yet, but it's on the list of things I want to do after I get the OHCI host driver done. What you learn will probably help me when I get around to doing that.
One problem with USB-to-Serial converters is that there is no USB standard for how they're supposed to work, so you will need to depend on the manufacturer to provide that information to you. That may be better than the boat you're in now, where there is a standard but the manufacturer doesn't seem to follow it.
A lot of the problems you've had in the past have been related to DPMI, memory locations, real-mode vs. protected mode, etc., and you seem to have all of that figured out now. It's just the device-specific stuff you need to work through. Hopefully the manufacturer will provide you enough information that you can figure it all out.