From owner-freebsd-hackers Wed Mar 20 21:59:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 117D437B419 for ; Wed, 20 Mar 2002 21:59:20 -0800 (PST) Received: from localhost (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.2/8.12.2) with ESMTP id g2L5x0ru092564; Thu, 21 Mar 2002 16:29:10 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Decision PCCOM Serial Card From: "Daniel O'Connor" To: John Hay Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <200203200858.g2K8wt140174@zibbi.icomtek.csir.co.za> References: <200203200858.g2K8wt140174@zibbi.icomtek.csir.co.za> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 21 Mar 2002 17:29:00 +1130 Message-Id: <1016690352.383.48.camel@chowder.gsoft.com.au> Mime-Version: 1.0 X-Spam-Status: No, hits=-5 required=5 X-Spam-Level: (-5) X-Scanned-By: MIMEDefang 2.6 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-03-20 at 20:28, John Hay wrote: > You might have more luck getting the puc driver to work with this card. > It is more flexable and meant for these kind of cards. > You will still need to figure out how the serial ports are organised on > the card though. Things like, does each serial port have its own BAR, or > are both inside one BAR and what the offset is where the ports start. > You might be able to figure that out from the linux patch though. > Once you figure those things out, you just add it to pucdata.c, build > a kernel with the puc device and off you go. :-) Hmm.. well I get this far -> puc0: port 0xc400-0xc4ff,0xc000-0xc07f mem 0xd8002000-0xd800207f irq 9 at device 11.0 on pci0 puc: name: PCCOM Serial port could not get resource Probably just guessed the BAR address wrong I suppose. I made the PUC driver a module, but once I load it and it tried to attach and errored out I now get.. mdtest# kldunload puc kldunload: can't unload file: Device not configured Sigh :) --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message