pjh@mccc.edu (Peter J. Holsberg) (05/25/91)
A colleague asks, "How do I tell UNIX about the internal modem I have that in MSDOS is on COM3 IRQ4 address 03E8?" Thanks, Pete -- Prof. Peter J. Holsberg Mercer County Community College Voice: 609-586-4800 Engineering Technology, Computers and Math FAX: 609-586-6944 1200 Old Trenton Road, Trenton, NJ 08690 Internet: pjh@mccc.edu TCF 92 - April ??-??, 1992
peter@ficc.ferranti.com (Peter da Silva) (05/25/91)
In article <1991May25.004941.26239@mccc.edu> pjh@mccc.edu (Peter J. Holsberg) writes: > A colleague asks, "How do I tell UNIX about the internal modem I have > that in MSDOS is on COM3 IRQ4 address 03E8?" If running a System V.3.2 derivitive, add an appropriate line to /etc/conf/sdevice.d/asy and /etc/conf/cf.d/mdevice, then run /etc/conf/bin/idbuild and reboot. Or, get a copy of the FAS driver and follow the instructions. -- Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180; Sugar Land, TX 77487-5012; `-_-' "Have you hugged your wolf, today?"
wtm@uhura.neoucom.EDU (Bill Mayhew) (05/26/91)
I'm not sure if just changing the address and IRQ of sdevice.d and cf.d entries for the standard asy port driver will work for other than the standard COM1 3f8 and COM2 2f8 addresses and IRQs 4 and 3 respectively. There is also a problem in that COM3 shares IRQ 4 with COM1. You may experience either hardware, software or both conflicts with the interrupts. The problem is that in the standard MSDOS ISA bus architecture interrupts are edge triggered. Almost all cards are stupidly designed so that they hold the IRQ lead low until their hardware is serviced. This means that any subsequent interrupts generated by other boards in the system while the first card is holding the IRQ lead low will not be noticed by the 8259 controller. This is a really p*ss poor design. I know why board designers do that, it allows an IRQ service routine to psuedo poll devices, but really violates the intended way of making things work. The other problem is the &**#@! boards themselves. You could share the interrupt if the boards had open collector outputs, but I've seen quite a few that have regular totempole TTL outputs driving the bus because they were too cheap to use one extra open collector driver part. Anyway, it seems that although the Sys V r 3.2 documentation hints that you can share IRQs, that it doesn't work. The idbuild process will bitch if you have two drivers with the same IRQ. I don't know if that is a "bug" in the idbuild process or if that is a limitation of the asy driver. I'm not an expert at writing drivers. I agree that the FAS 2.06 driver that Peter recommends is a good idea. I've installed it on my system. I also rigged my COM3 port to use IRQ 7 so that I could still have the built-in ports. At least the newer designs fix the quick and dirty design of the original IBM PC. Both the EISA bus and MCA bus have level triggered interrupts. Bill -- Bill Mayhew NEOUCOM Computer Services Department Rootstown, OH 44272-9995 USA phone: 216-325-2511 wtm@uhura.neoucom.edu ....!uunet!aablue!neoucom!wtm via internet: (140.220.001.001)
gemini@geminix.in-berlin.de (Uwe Doering) (05/29/91)
wtm@uhura.neoucom.EDU (Bill Mayhew) writes: >limitation of the asy driver. I'm not an expert at writing >drivers. I agree that the FAS 2.06 driver that Peter recommends is >a good idea. I've installed it on my system. I also rigged my I think a better idea would be to use FAS 2.08. :-) This is the latest FAS release. I has lots of speed improvements compared to FAS 2.06. Uwe -- Uwe Doering | INET : gemini@geminix.in-berlin.de Berlin |---------------------------------------------------------------- Germany | UUCP : ...!unido!fub!geminix.in-berlin.de!gemini
bill@ssbn.WLK.COM (Bill Kennedy) (05/30/91)
:gemini@geminix.in-berlin.de (Uwe Doering) writes: :wtm@uhura.neoucom.EDU (Bill Mayhew) writes: : :>limitation of the asy driver. I'm not an expert at writing :>drivers. I agree that the FAS 2.06 driver that Peter recommends is :>a good idea. I've installed it on my system. I also rigged my : :I think a better idea would be to use FAS 2.08. :-) This is the :latest FAS release. I has lots of speed improvements compared to :FAS 2.06. : : Uwe Sorry to repeat the whole post, but my question doesn't make sense without it. Does FAS 2.08 work on AT&T 3.x? When I tried an earlier version it had a different tty structure and wouldn't bind. I gave up on it and went back to Interactive but maybe I just made some bone headed mistake or 2.08 will work. I was using 2.06 and Vr3.2.2 if memory serves. -- Bill Kennedy internet bill@ssbn.WLK.COM or ssbn!bill@attmail.COM uucp {att,cs.utexas.edu,pyramid!daver}!ssbn.wlk.com!bill