--/unnNtmY43mpUSKx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I have a usb-irda widget I'm trying to get working.  Instead of
following the class driver spec for uirda, this thing turned out to be
a uplcom(4) glued to an rs232 irda dongle.  So, I must use
irframetty(4) - but that doesn't currently have a control driver for
this dongle.

I've written one by looking at the linux equivalent - but it's not
working.  I can use it fine at 9600bps (the default power on speed),
but at no other speeds.  The major/only purpose of the dongle driver
is to signal the dongle to change speeds to match the serial port data.

No matter what variations I try, it's not changing speed - and its so
simple there's really not much room for it to be wrong, assuming the
linux driver works, which it evidently does.

Each dongle does it a little differently, but it typically depends on
signalling and timing via the DTR and RTS control lines.  I'm starting
to wonder if this part is working.  It's obviously not feasible to put
a serial line analyser in the cable in this case :/

Before I spend much more fruitless time, could anyone confirm please
that ucom, and uplcom in particular, work as expected for RTS and DTR
signalling? It's using TIOCM[GS]ET on the parent tty to effect the
change, with masking so that only TIOCM_DTR and TIOCM_RTS are actually
changed.

The other option is that the timing of signalling changes and data
sending via usb is radically different than via a normal serial port,
and this is confusing the dongle.

--
Dan.
--/unnNtmY43mpUSKx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAfHvZEAVxvV4N66cRAsY5AKDOiYp0zckLtZLq8A27FX7qkaUiYgCeOV47
Rr2paQkr1KjTpw6QDnUJUJQ=
=Vq2+
-----END PGP SIGNATURE-----

--/unnNtmY43mpUSKx--