From owner-freebsd-bugs Sat Jun 17 7:25:42 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from mx.oau.org (mx.oau.org [208.46.16.50]) by hub.freebsd.org (Postfix) with ESMTP id 474A837B5D3 for ; Sat, 17 Jun 2000 07:25:38 -0700 (PDT) (envelope-from elliot@alfred.oau.org) Received: (from uucp@localhost) by mx.oau.org (8.9.3/8.9.3) with UUCP id KAA23476; Sat, 17 Jun 2000 10:24:18 -0400 (EDT) Received: (from elliot@localhost) by alfred.oau.org (8.9.3/8.9.3) id KAA48740; Sat, 17 Jun 2000 10:18:13 -0400 (EDT) (envelope-from ebd@alfred.oau.org) From: Elliot Dierksen Message-Id: <200006171418.KAA48740@alfred.oau.org> Subject: Re: RocketPort PCI/Octa/DB25 vs. FreeBSD 3.4-STABLE In-Reply-To: <200006042301.BAA71367@midten.fast.no> from "Tor.Egge@fast.no" at "Jun 5, 2000 01:01:26 am" To: Tor.Egge@fast.no Date: Sat, 17 Jun 2000 10:18:13 -0400 (EDT) Cc: ebd@alfred.oau.org, support@comtrol.com, Tom.Hitchcock@comtrol.com, freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Tor.Egge@fast.no: >> 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. > >MAKEDEV generates incorrect minor device numbers for {cua,tty}{i,l}R0. >Locking of control characters is broken in rp.c. > >I suggest the following steps: > > - apply the enclosed patches > - install the updated MAKEDEV > - recreate the RocketPort device files by running the newly > installed MAKEDEV > - compile a new kernel > - install the new kernel > - reboot the machine > - test > >The standard RocketPort driver in FreeBSD has some additional problems: > > - Only the first PCI RocketPort card works in a machine. > - open() might cause a kernel panic instead of returning ENXIO if > the device doesn't exist. This seems to address most of the problems I was having. I plan to try and move one of my main modems to the RocketPort card this weekend. I did notice that these changes have not made their way into 3.4-STABLE. Any idea what the hold-up is? Thanx for your help! EBD -- Elliot Dierksen "There ain't nothing like regret To remind you you're alive" -- Sheryl Crow - The Difficult Kind Home) ebd@oau.org (407) 850-9760 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message