On Jun 24, 2008, at 11:28 AM, Alexander Wagner wrote: >> I have looked at it briefly since your email and yes, you >> are right, this OS X USB APIs are a different beast >> altogether. I had assumed (stupid) that they would have >> lower level APIs simlilar to BSD but I was quite wrong. >> As near as I can tell, there is only one way to get to USB >> devices on OS X and it involves using IOKit. > > They have. They offer a driver that adds a serial port. The > drama starts as the Mac doesn't know a thing about a serial > port. This driver adds a serial port but that virtual port > is a bit strange as far as we could tell. > I was under the impression that the usb models had a custom driver for windows that needed to be ported. It sounds like you're saying that the board presents itself as a serial device (has its own usb->serial UART) and that a driver for it is provided with the board. Is that right? Do you know which chipset is used for the UART?
If that's true then you're probably right; it might just be a matter of handling the provided serial port properly in dgtnix. This is not nearly as daunting as what I was thinking. I was envisioning writing a custom driver which would have required digging into IOKit, as this is the only way to get to the device. That would be an alternative approach if the serial drive didn't work out. I believe IOKit provides a facility for writing user space usb drivers. That would basically mean that dgtnix would talk to the usb device directly. The only advantage to this (other than learning something new) would be less stuff to install. Probably not worth the extra effort. Hmm... ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users