Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!wupost!uunet!mcsun!sun4nl!tuegate.tue.nl!svin09.info.win.tue.nl!wzv.win.tue.nl!gvr.win.tue.nl!guido From: guido@gvr.win.tue.nl (Guido van Rooij) Newsgroups: comp.unix.bsd Subject: Re: XFree86, COM driver, ported programs Message-ID: <1n79u5$lu0@wzv.win.tue.nl> Date: 5 Mar 93 10:27:17 GMT References: <2B931973.9680@news.service.uci.edu> Organization: Eindhoven University of Technology, The Netherlands Lines: 24 NNTP-Posting-Host: gvr.win.tue.nl swallace@pal-r32-a07b.slip.nts.uci.edu (Steven Wallace) writes: >com2 and com3 drivers). I added these to my configuration file and >the appropriate address vectors, but although the system would boot >and recognize those com ports, the com ports would not work at all. >Obviously, since there is a sharing of IRQ lines (i.e. 3 and 4) between >two individual COM ports, the driver has to distinguish which com unit >the interrupt originated from. Has anyone modded this into their com >driver or can give me advice on how to implement this? Change the code in atatch() so that the interrupts on the port sharing irq's are not disabled. Not however that then a real multi comport will not function anymore. Note further that you may blow up your hardware because some comports have their interrupt line directly connected to the bus's irq. It should be connected via an open collector instead. You can also solve it by making com3 use irq5 (second parallel port) if irq5 is free. All you need is a bit of soldering. -Guido -- Guido van Rooij | Internet: guido@gvr.win.tue.nl Bisschopsmolen 16 | Phone: ++31.40.461433 5612 DS Eindhoven | ((12+144+20)+3*sqrt(4))/7 The Netherlands | +(5*11)=9^2+0