On 01/24/2003 05:45 PM Thomas Jarosch wrote: > Dear Wolfgang, > > I'm currently designing a USB <--> VFD display interface > using the Philips PDIUSBD12 USB chip. > > I was very luck to find out that the linux mct_u232 driver > is already talking to this chip, so writing the driver > for the interface won't be too hard (I hope). > > The display got the same control lines for parallel data transfer > as the USB chip, but the BUSY line is missing. The display > sets the BUSY line to high for some short period of time > while it processes received data. > > Maybe you can shed some light on this: > How is the data transfer speed of the parallel interface controlled? > How does other hardware tell the chip to stop sending new data? > > I've seen the BUSY flag is available on the pin D7 if you read > from the other device indicating if it's busy or not. > Does the USB chip automatically wait for this flag? > > I'm stuck with this problem so any help is really appreciated.
It's a long time ago that I made the initial implementation for the MCT U232 device. And just now I realized that Julian Highfield has pointed out that there is a Philips PDIUSBD12 USB chip inside. Well, as I never really cared about the USB transfer, I can not really help. But very likely some USB core developer on the linux-usb-devel list can (see CC). Good luck, Wolfgang. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
