In message <[EMAIL PROTECTED]>, John Marshall wri
tes:
>
>1. `Selectorised' systraps such as the new serial manager routines don't
> work in prc-tools 0.5.0 without fairly major hacking to the header
> files. (On the other hand, the *old* serial manager routines are in
> a shared library, which prc-tools 0.5.0 supports fine. Perhaps that
> is what you were thinking of?)
I have an application that's been using the serial port for communications,
and I'd like to switch it to use IrComm now. That's my definite goal. If
there's a way to make this work with prc-tools 0.5.0 and the new SDK, please
let me know!
If possible, I'd like to make it so the application can be easily switched
back to (or back and forth between) the serial port (and IrComm). But my
first priority is getting IrComm. If that means no serial port, so be it.
>4. The alpha version of the 3.5 SDK now at the Provider Pavilion works fine
> with __callseq__, and in particular, GCC 2.95.2-kgpd with this SDK
> compiles Srm* functions just fine (I just tested it).
>
>So the answer is: download the SDK again.
>
> John "it's pre-alpha software, Jason, and so for some reason it
> gets a date not a version number. Oh, and don't shoot the
> messenger! :-) :-)"
Great, I'll try this again. It'd be even better if it could be made to work
with the old prc-tools, as that's what's currently in the OpenBSD ports, but
I can deal.
Cheers!
-Angelos
