Re: what happened to /dev/cuaa0
- From: Anton Shterenlikht <mexas@xxxxxxxxxxxxx>
- Date: Thu, 21 Sep 2006 16:37:27 +0100
Switching to cuad* should have worked. sio(4) was the only driver
where the cua* and tty* devices had different letters, so the cuaa*
devices were renamed in 6.0 to match their ttyd* counterparts. If
you're using an internal modem, if may be a "Winmodem" requiring a
special driver. The comms/ltmdm port may help here. If it's an
external modem, try cuad1.
After reading Section 22.2.2.2.2 of the Handbook my understaning is that
the same serial port can be addressed as either /dev/ttydN or /dev/cuadN.
Is that correct?
I'm confused by the "Call-in" - "Call-out" terminology. I have an
external modem connected to 1st serial port, and I use it as /dev/ttyd0.
Does it mean it becomes a call-in device?
thanks
anton
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: what happened to /dev/cuaa0
- From: Dan Nelson
- Re: what happened to /dev/cuaa0
- References:
- what happened to /dev/cuaa0
- From: KHOO Guan_Chen
- Re: what happened to /dev/cuaa0
- From: Dan Nelson
- what happened to /dev/cuaa0
- Prev by Date: Re: How "real time" is FreeBSD?
- Next by Date: Re: How "real time" is FreeBSD?
- Previous by thread: Re: what happened to /dev/cuaa0
- Next by thread: Re: what happened to /dev/cuaa0
- Index(es):
Relevant Pages
|