buster
March 29th, 2006, 17:55
Hi,

Just wondered if anyone has had any luck getting one of these to work. I've got a 4 port VScom 400H.

Dmesg reports:

puc0 at pci0 dev 15 function 0 "Oxford VScom 400H/800H" rev 0x00: com,com, com, com

pccom3 at puc0 port 0 irq 0: st16650, 32 byte fifo
... port 1 irq 0: st16650, 32 byte fifo
... port 2 irq 0: st16650, 32 byte fifo
... port 3 irq 0: st16650, 32 byte fifo

I was hoping I could just plug in the card and then start using it (say cu -l /dev/cua02). Anyway it doesn't seem to have any device node for the ports.

I've done some seraching around and the issue seems to resolve around them sharing an IRQ?

Linux has a setserial command but I've found no equivalent on OpenBSD.

There is a DOS program VSSHOW that will give output like (example only):

VS PCI 400H found at bus 0, device nr. 19 func 0
IRQ = 9
Speed: HIGH
Com port 1: 0x6200
Com port 2: 0x6208
Com port 3: 0x6210
Com port 4: 0x6218

And this remains constant providing hardware is left alone.

Any ideas where I can go from here???

Any help would be much appreciated (and save me having to hunt down a Cisco 2509!)

Cheers

Strog
March 29th, 2006, 18:52
I see OpenBSD was patched back in '01 for that card so I would think the driver is matured by now. The puc (http://www.openbsd.org/cgi-bin/man.cgi?query=puc) device is compiled into the GENERIC kernel (http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/conf/GENERIC) which is evident by your dmesg. Are you saying that you don't have a /dev/cua02, etc.?

buster
March 30th, 2006, 05:24
The normal deives cua00 cua01 etc are present. In fact I tested my Cisco console cable through the two inbuilt COM ports on my motherboard (cu -l /dev/cua01 etc)

I had another look at dmesg, and I missed a bit:

puc0 at pci0 dev 15 function 0 "Oxford VScom 400H/800H" rev 0x00: com,com, com, com
pccom3 at puc0 port 0 irq 0: st16650, 32 byte fifo
pccom4 at puc0 port 1 irq 0: st16650, 32 byte fifo
pccom5 at puc0 port 2 irq 0: st16650, 32 byte fifo
pccom6 at puc0 port 3 irq 0: st16650, 32 byte fifo
vendor "VScom", unknow product 0xffff (class communications subclass miscellaneous rev 0x00) at pci0 dev 15 function 1 not configured.
...
...
pccom0 at isa0 port 0x3f8/8 irq4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x3f8/8 irq3: ns16550a, 16 byte fifo


Also from a DOS disk I ran supplied VSshow.com to get:

VS PCI 400H found at bus0, device nr. 15 func 0
IRQ = 7
Speed: x8 (HIGH)
Com port 1: 0xA800
Com port 2: 0xA808
Com port 3: 0xA810
Com port 4: 0xA818

I guess these mappings stay the same as long as I leave hardware and bios alone.

The reason for finding the port addresses was after reading the following for FreeBSD system: http://www.visionsystems.de/faq/faq/VSFreeBSD_e.html


I wonder if I need to do something similar with OpenBSD? In the FreeBSD guide it looks like the devices are created in the last step after everything has been mapped?

I'm not really sure though so would appreciate any thoughts/guidance. I've never had need to create devices so am a little unsure of myself here.

Thanks

buster
March 30th, 2006, 12:18
Cracked it! :icon_smil

No idea what I was doing but I tried:

/dev/MAKEDEV tty03
/dev/MAKEDEV tty04
/dev/MAKEDEV tty05
/dev/MAKEDEV tty06

This worked immeadiately e.g cu -s 9600 -l /dev/tty03.
All four ports now available.

So I've reused some old hardware as a console server to my Cisco routers :biggrin:

Thankyou OpenBSD - again! I always buy the CD's but I'll make a donation this time around - we can't let it die :frown:

And thanks to Strog to. Your post put me on the right track. Cheers

Strog
March 30th, 2006, 12:26
I just got a box on the bench to mess with. I had some PCI USR modems that are supposed to use the puc driver too. Oh well.

Congrats on getting it going. :biggrin: