Subject: port-cats/14235: fcom console doesn't set HW flow control correctly at boot
To: None <gnats-bugs@gnats.netbsd.org>
From: Richard Earnshaw <rearnsha@buzzard.freeserve.co.uk>
List: netbsd-bugs
Date: 10/13/2001 09:46:45
>Number:         14235
>Category:       port-cats
>Synopsis:       fcom console doesn't set HW flow control correctly at boot
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-cats-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 13 01:52:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Richard Earnshaw
>Release:        NetBSD-current 13 Oct 2001
>Organization:
self
	
>Environment:
	
System: NetBSD osprey.buzzard.freeserve.co.uk 1.5Y NetBSD 1.5Y (OSPREY) #6: Sat Oct 13 09:23:20 BST 2001 rearnsha@osprey.buzzard.freeserve.co.uk:/usr/src/sys/arch/cats/compile/OSPREY cats


>Description:
	The H/W flow contol lines on the fcom serial port are not set 
	correctly at boot, which means that you can't type anything
	at the fcom port until getty starts to run there.
	
>How-To-Repeat:
	Using a serial connection to fcom0 from a machine that respects
	H/W flow signals (RTS/CTS etc).

	from the firmware, boot with

	boot wd0a:/netbsd -s console=fcom0

	try to press return when asked for a shell, note that nothing is
	received.
	
>Fix:
	The serial driver should set the H/W flow control bits correctly
	during init to enable transmission.
	
>Release-Note:
>Audit-Trail:
>Unformatted: