From owner-freebsd-hackers Wed Mar 20 22:39:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 3523F37B41A for ; Wed, 20 Mar 2002 22:39:46 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g2L6dSv79049; Thu, 21 Mar 2002 08:39:28 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200203210639.g2L6dSv79049@zibbi.icomtek.csir.co.za> Subject: Re: Decision PCCOM Serial Card In-Reply-To: <1016690352.383.48.camel@chowder.gsoft.com.au> from "Daniel O'Connor" at "Mar 21, 2002 05:29:00 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Thu, 21 Mar 2002 08:39:28 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > 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 Hmmm. The puc driver won't work with a mem mapped BAR. The sio driver won't like it, so I never tried to make the puc driver able to do mem mapped devices. Hopefully, one of the other BARs (the IO ones) will contain the serial ports. > > Probably just guessed the BAR address wrong I suppose. Can't you get the BAR info from the linux driver? > 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 I never tried to make it into a module because I weren't sure what the interaction with the sio driver would be. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message