From nobody@FreeBSD.ORG  Sat Jun  3 10:54:54 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 70F5B37BCD4; Sat,  3 Jun 2000 10:54:54 -0700 (PDT)
Message-Id: <20000603175454.70F5B37BCD4@hub.freebsd.org>
Date: Sat,  3 Jun 2000 10:54:54 -0700 (PDT)
From: ebd@oau.org
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Problems with Comtrol RocketPort
X-Send-Pr-Version: www-1.0

>Number:         18987
>Category:       misc
>Synopsis:       Problems with Comtrol RocketPort
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 03 11:00:01 PDT 2000
>Closed-Date:    Sun Oct 14 10:58:44 PDT 2001
>Last-Modified:  Sun Oct 14 10:59:56 PDT 2001
>Originator:     Elliot Dierksen
>Release:        3.4-STABLE
>Organization:
>Environment:
FreeBSD alfred.oau.org 3.4-STABLE FreeBSD 3.4-STABLE #17:
Sat Jun  3 11:53:35 EDT 2000
root@alfred.oau.org:/usr/src/sys/compile/NEWALF2  i386

>Description:
The problem involves a Comtrol RocketPort PCI/Octa/DB25. The problem is
that you can not use the port at any baud rate other than 9600 baud. The
problem is two-fold. I have a fix for the first part. There is an
incorrect definition of the static struct speedtab baud_table array. This
should be an array of 2 element structures. As it is currently defined,
it is a single structure will more than 2 elements. I tested this by
breaking up the structure into multiple elements, and that works fine.
I have isolated the second part, but have not yet come up with a
resolution. The setting lock devices are not working properly
(cualR0, ttylR0) with regards to the baud rate. If you set the lock device
to zero baud, it will only let you access the device at zero baud. The
same holds true for 1200, 2400, etc. The initial setting of this device
starts at 9600 baud. I have not been able to locate a value that allows
you to change the baud rate of the regular callout device (cuaR0) when
you access it. I don't know if this problem is in rp.c or tty.c. I will
keep trying to find it, but I would appreciate any assistance.

Thanx,

EBD

>How-To-Repeat:
Correct to the structure definition in rp.c.
recompile and install new kernel.
reboot
stty -a < /dev/cualR0
baud rate will be 9600 baud. any value set on this device locks the
baud rate. I have not found a value that permits the baud rate to vary.

>Fix:
Fix speedtab structure definition.
??? I don't know yet about the rest.


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mjacob 
State-Changed-When: Mon Oct 1 22:34:52 PDT 2001 
State-Changed-Why:  
Is this still a problem for you? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18987 
State-Changed-From-To: feedback->closed 
State-Changed-By: mjacob 
State-Changed-When: Sun Oct 14 10:58:44 PDT 2001 
State-Changed-Why:  
Submitter says that bug is fixed in -current and that it probably 
isn't practical to move the changes to -stable as it. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18987 
>Unformatted:
