I've just tried to use cuaU2 and cuaU1 to have both ucom1 and ucom2
ports connected instead of ucom0 cuaU0 for command/voice interface of
the modem. All works fine from now.
Thanks for comprehensive answer.
Cheers
On 07.09.2014 3:45, Zé Loff wrote:
On Sat, Sep 06, 2014 at 10:04:28PM +0400, Denis Lapshin wrote:
Having trouble accessing both Data (ucom0) and Voice (ucom1) in one
composite device: '/dev/cuaU0' - USB 3G modem.
/dev/cuaU0 is not a composite device, is the terminal interface for one
of the two serial ports on your modem (and I'm pretty sure none of them
are for 'voice', but without a dmesg one can only wonder). The other
serial interface (ucom1) can be accessed on /dev/cuaU1.
Is it possible to use the same /dev/cuaU* device for accessing both
ucom0, ucom1, ucom* to have voice and data functions available in the
modem simultaneously?
You need to be a lot clearer in explaining what exactly are you trying
to do, and what you mean by simultaneous. My 3G modem also has two
serial interfaces and I can send AT commands on both of them (e.g. use
one for connect/disconnect chat and the other to periodically get
connection stats without fear of collisions/races).
Needed functionality seems to be integrated into FreeBSD by using 'u3g'
kernel mode driver which provides access to a modem 'ucom*' ports by
accessing to: /dev/cuaU0.1 and /dev/cuaU0.2
How to the same functionality can be performed in OpenBSD?
I don't know a thing about FreeBSD device numbering, but my guess is
that /dev/cuaU0.1 and /dev/cuaU0.2 are /dev/cuaU0 and /dev/cuaU1.
Some ideas will be helpful.
Read man 4 ucom, look at your dmesg carefully and please append it to
your message next time.
Cheers
Zé
