Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Sep 2006 16:37:27 +0100
From:      Anton Shterenlikht <mexas@bristol.ac.uk>
To:        Dan Nelson <dnelson@allantgroup.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: what happened to /dev/cuaa0
Message-ID:  <20060921153727.GA20997@mech-aslap33.men.bris.ac.uk>
In-Reply-To: <20060921150005.GA73717@dan.emsphone.com>
References:  <6.2.5.6.1.20060921193135.0308c080@singnet.com.sg> <20060921150005.GA73717@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060921153727.GA20997>