> > 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: <PCCOM Serial port> 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 -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
