|
NAMEng_tty —
netgraph node type that is also a TTY hook
SYNOPSIS#include <sys/types.h>
#include <sys/ttycom.h>
#include <netgraph/ng_tty.h>
DESCRIPTIONThetty node type is both a netgraph node type and a TTY
hook.
The node has a single hook called Incoming data is delivered directly to ng_tty via the tty bypass hook as a buffer pointer and length, this is converted to a mbuf and passed to the peer. The node supports an optional “hot character”. If
the driver can not deliver data directly to the tty bypass hook then each
character is input one at a time. If set to non-zero and bypass mode is
unavailable, incoming data from the tty device is queued until this
character is seen. This avoids sending lots of mbufs containing a small
number of bytes, but introduces potentially infinite latency. The default
hot character is 0x7e, consistent with HOOKSThis node type supports the following hooks:
CONTROL MESSAGESThis node type supports the generic control messages, plus the following:
SHUTDOWNThis node shuts down when the corresponding device is closed.SEE ALSOioctl(2), netgraph(4), ng_async(4), tty(4), ngctl(8)HISTORYTheng_tty node type was implemented in
FreeBSD 4.0.
AUTHORSArchie Cobbs <archie@FreeBSD.org>Andrew Thompson <thompsa@FreeBSD.org> BUGSThe serial driver code also has a notion of a “hot character”. Unfortunately, this value is statically defined in terms of the line discipline and cannot be changed. Therefore, if a hot character other than 0x7e (the default) is set for theng_tty node, the
node has no way to convey this information to the serial driver, and
sub-optimal performance may result.
Visit the GSP FreeBSD Man Page Interface. |