NetBSD Problem Report #14235

Received: (qmail 14426 invoked from network); 13 Oct 2001 08:51:23 -0000
Message-Id: <200110130846.f9D8kjN00306@osprey.buzzard.freeserve.co.uk>
Date: Sat, 13 Oct 2001 09:46:45 +0100 (BST)
From: Richard Earnshaw <rearnsha@buzzard.freeserve.co.uk>
Reply-To: rearnsha@buzzard.freeserve.co.uk
To: gnats-bugs@gnats.netbsd.org
Subject: fcom console doesn't set HW flow control correctly at boot
X-Send-Pr-Version: 3.95

>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:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 13 08:52:01 +0000 2001
>Closed-Date:    Wed May 05 19:37:39 +0000 2004
>Last-Modified:  Wed May 05 19:37:39 +0000 2004
>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:
State-Changed-From-To: open->feedback 
State-Changed-By: nathanw 
State-Changed-When: Wed Aug 28 15:21:32 PDT 2002 
State-Changed-Why:  
According to my reading of the 21285 (footbridge) data sheet, the serial 
port on the 21285 doesn't have any flow control pins, just RX and TX. So 
there's not much to do but make the other end of the connection ignore 
flow control. 

State-Changed-From-To: feedback->open 
State-Changed-By: rearnsha 
State-Changed-When: Wed Nov 6 16:19:53 PST 2002 
State-Changed-Why:  
To: nathanw@netbsd.org 
Cc: rearnsha@buzzard.freeserve.co.uk, port-cats-maintainer@netbsd.org 
Subject: Re: port-cats/14235 
Date: Fri, 30 Aug 2002 00:09:17 +0100 
From: Richard Earnshaw <rearnsha@buzzard.freeserve.co.uk> 

> According to my reading of the 21285 (footbridge) data sheet, the serial 
> port on the 21285 doesn't have any flow control pins, just RX and TX. So 
> there's not much to do but make the other end of the connection ignore 
> flow control. 

Hmm, true.  So what does getty do to the port to make things work once it  
has started (because it does)? 

R. 

State-Changed-From-To: open->feedback 
State-Changed-By: chris 
State-Changed-When: Mon Mar 31 11:46:55 PST 2003 
State-Changed-Why:  
I've not see this bug, I've had issues with speed over the serial
line, but then you'd expect that without hardware flow control.


From: "Erik E. Fair" <fair@NetBSD.org>
To: chris@NetBSD.org
Cc: NetBSD GNATS Bug Tracking System <gnats-bugs@NetBSD.org>
Subject: Re: port-cats/14235
Date: Wed, 28 May 2003 22:37:57 -0700

 Chris,
 	You put this problem report into feedback state, but I don't 
 see what you want to get back from Richard. What sort of feedback are 
 you looking for?

 	a curious GNATS DB admin,

 	Erik <fair@netbsd.org>

From: Chris Gilbert <chris@dokein.co.uk>
To: gnats-bugs@NetBSD.org
Cc: fair@NetBSD.org
Subject: Re: port-cats/14235
Date: Wed, 5 Nov 2003 09:50:34 +0000

 Hi Eric,

 You're right the reply didn't ask for anything.  What I was looking for
 was to find out is if richard has a mis-configuration of the console
 speed, I believe that the cats firmware runs the serial line at 38400
 bps, and getty defaults to 9600, hence the issues seen.  Perhaps the
 right fix is to make the cats ttys file default to 38400 as the speed?  

 Chris
State-Changed-From-To: feedback->closed 
State-Changed-By: rearnsha 
State-Changed-When: Wed May 5 19:35:32 UTC 2004 
State-Changed-Why:  
I don't know what the problem was here, but it seems to have gone away 
(at least for now). 
For the record, of course my serial line was set correctly, or I wouldn't 
have been able to specify the kernel name, or respond to the question about 
the shell. 
>Unformatted:

Home	PR Database Search