summaryrefslogtreecommitdiffstats
path: root/bin/ls/print.c
diff options
context:
space:
mode:
authordlg <dlg@openbsd.org>2005-01-10 12:05:08 +0000
committerdlg <dlg@openbsd.org>2005-01-10 12:05:08 +0000
commit021bcdb4b2ff4237ae8af51ff5f64babe3d57320 (patch)
treefe9e849d25ca4269316d00290e534ae0292acd3f /bin/ls/print.c
parentfrom freebsd, uplcom.c revision 1.23: (diff)
downloadwireguard-openbsd-021bcdb4b2ff4237ae8af51ff5f64babe3d57320.tar.xz
wireguard-openbsd-021bcdb4b2ff4237ae8af51ff5f64babe3d57320.zip
from netbsd uplcom.c revision 1.37:
Make sure that we call uplcom_set_line_state() to get consistent state between our idea of flow controll settings and the chips one. In uplcom_set_line_state use the same value as the manufacturer suggests, since the previously used (umodem based) values do not seem to work. It is not completely clear what happened here - either the "not calling uplcom_set_line_state" due to luck prevented the non working state to be discovered or there are variants of the chip that need the old values. During testing none such chips have been found - if they ever apear we might have to make this function more intelligent, depending on the chip in use.
Diffstat (limited to 'bin/ls/print.c')
0 files changed, 0 insertions, 0 deletions