Garth Corral wrote:
Hi!
>> dgtdrv itself sits on the dgtnix library which is portable between OS,
>> its done in plain POSIX C. dgtdrv itself is also plain C(++). Its
>> known to work on Linux and Windows at the moment afaik also on BSD. We
>> have an open issue on the Mac that actually nobody understands as we
>> just use POSIX IO for serial ports, but the Mac has a bit a strange
>> way to add usbserial by some driver. At this part a Mac programmer
>> should have a look at, then I think the solution would be almost
>> trivial. (But try to fix some hardware dependend thing if you don't
>> have the hardware nor a compiler...) dgtdrv itself compiles out of the
>> box on OSX and also works there as I was able to test with the virtual
>> board. Its just an issue with the serial port on the Mac. We had the
>> feeling that the mac might not like serial IO without _any_ flow
>> control as it is used by DGT. Ie. dgtdrv2 starts up, searches for the
>> board and hangs there right after the first char send to the serial
>> port even in the init routines of dgtnix.
>>
>> BTW: which project do you mean that supports the DGT on OSX at all? Do
>> you think of eBoard? This just uses the same backend, it sits right on
>> dgtnix. I don't think you'll get the DGT to talk here as the open
>> issue mentioned on OSX is still unresolved in dgtnix.
>>
> I was vaguely aware of the existence of dgtnix but had not
> looked at it. I guess I assumed that the scid support was
> based on this in some way.
Sure. I've an older version of the driver that does not need
dgtnix but uses code from crafty. This could probably be
portable but I'm not really sure there and this code is a
pretty hack. Using dgtnix is a lot cleaner.
> Yes, I was referring to eBoard. I wasn't aware of the
> problems on OS X, so that means that there is no support
> on my platform of choice.
I fear not. eBoard is just compiling against dgtnix.
> Now I have a sort of catch 22. I'm willing to work on
> this (time permitting), but with no current support I'm
> not really inclined to incur the expense of the board, but
> without the board I can't really work on it to make things
> better.
I know that problem well. I've no Mac...
> 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.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
-------------------------------------------------------------------------
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
