Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:1459 comp.unix.bsd:11775 Newsgroups: comp.os.386bsd.questions,comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!psgrain!percy!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Subject: Re: patch support for Chris' com drivers ? Message-ID: <C55IGr.1M9@agora.rain.com> Organization: Open Communications Forum References: <1993Apr6.144356.21797@latcs1.lat.oz.au> <C543Lv.Ht9@agora.rain.com> <CGD.93Apr7181957@eden.CS.Berkeley.EDU> Date: Thu, 8 Apr 1993 06:10:02 GMT Lines: 77 cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <C543Lv.Ht9@agora.rain.com> rgrimes@agora.rain.com (Rodney Grimes) writes: >>Support for COM3 and COM4 is availiable even in 0.1, you just need to >>add the lines to your config file. Patchkit 0.2.3 does add the defines >>so that you can use IO_COM3 and IO_COM4 in the config file, also the >>GENERICISA kernel has been updated to include this support. >NO IT IS NOT. Chris, please don't contridict me, you have not even seen my GENERICISA config file. Yes the support for COM3 and COM4 is there, no they do not use shared interrupts. I used the most common alternate IRQ's for them IRQ2 and IRQ5, this has the largest hardware support. I am running a kernel config just that way. I have 2 16550 ports at std com2 and com4, irq5, irq2 respectfully. And 2 16450 ports at std com1 and com3. It works and it has since 0.1. >COM3 and COM4 require interrupt sharing, and the default serial driver >will *NOT* do this. Agreed, and that is NOT what I did, see above. >>I am regreatting haveing to say that Chris' com drivers will probably >>not end up in the patchkit, I have decided to get Bruce Evan's intr >>code in one way or the other and his com driver, I believe that even >>Chris is behind this idea (Chris?). >*I* am certainly not regretting your decision! 8-) Glad to see we are on agreement here, I rember you saying something about we should move to Bruces code and junk yours at one time or another... >the original serial driver was a piece of crap (it was based on >a serial driver for the HP300, which has a somewhat >different set of constraints placed on it...). >i'll be glad to see it go away. We all will! >>I know of someone working on getting >>all of Chris's BIDIR and modem support stuff into Bruce's com driver. >>This is a much better solution to a lot more problems that Chris's drivers. >AMEN. >bde's driver has some serious problems: configuring it is >totally broken, but i guess people are working on that... >if not, i know somebody who wants to... Please could we get these people togeather, it would be really nice to have this completed and ready for incusion in a future patchkit. >also, it requires his NPX patches, which screw some people >with 386/387 combos... Yes, I posted one patch that allows you to get past the probe code, now we need a 387 guru to fix the other system hangs (when I run Bruce's fpetest program it locks me up tighter than a drum, suspect infinite fwait problems). This is a plea to the NET as a hole. Please some one out there fix Bruces Code for 386/387 systems so that we can ALL run it. And so that we can all run the intr code that goes withit. I have had many request to get this in the patchkit. I can't put it in until these bugs are fixed, it would be counter productive... >chris >-- >Chris G. Demetriou cgd@cs.berkeley.edu > "386bsd as depth first search: whenever you go to fix something you > find that 3 more things are actually broken." -- Adam Glass Humm, only 3, seems like 5 to 7 are more realistic numbers! -- Rod Grimes rgrimes@agora.rain.com 386BSD patchkit coordinator Wish it paid real money! Accurate Automation Company All opinions belong to me and my company!