Date: Sun, 15 Aug 2010 09:51:06 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Paul Thornton <prt@prt.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Problem detecting and reacting to serial break Message-ID: <C1709BF3-5E1F-4E4A-B7AC-9B3D429870A8@gsoft.com.au> In-Reply-To: <4C672FF4.4080208@prt.org> References: <4C66D2CF.9040408@prt.org> <B6614C81-EF88-475E-AA6C-75F5C649819E@gsoft.com.au> <4C672FF4.4080208@prt.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-34-729272746 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 15/08/2010, at 9:38, Paul Thornton wrote: > Part of the problem I'm having is that whenever you try and search for > information/docs about this sort of thing, you're transported back in = a > time warp to the 1980s where people used serial terminals as the norm > for access and everything seems to be written from that standpoint - = not > from a "I'd like to use the serial port for binary data that has = nothing > to do with interactive login please" perspective... Yep, definitely time to blow some dust off various old tomes :) Between 7.x and 8.x the default serial driver changed from sio to uart. You can recompile your kernel and get sio back and see if that has an = effect. Actually I see you used cuaU0 - that is a USB serial dongle so the = driver change would have no effect. That said the stack was rewritten between 7 & 8 too so perhaps that is = related. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --Apple-Mail-34-729272746--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C1709BF3-5E1F-4E4A-B7AC-9B3D429870A8>