Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:9275 comp.os.386bsd.misc:2063 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!pa.dec.com!usenet.pa.dec.com!jkh From: jkh@morse.ilo.dec.com (Jordan Hubbard) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: problems with driver for a DEC pc mouse - help Date: 11 Mar 1994 13:51:37 GMT Organization: Digital Equipment Corporation, Galway Ireland Lines: 19 Distribution: world Message-ID: <JKH.94Mar11135138@morse.ilo.dec.com> References: <CMCovn.18q@curia.ucc.ie> <COGSWELL.94Mar10163657@creampie.cs.uoregon.edu> NNTP-Posting-Host: morse.ilo.dec.com In-reply-to: cogswell@creampie.cs.uoregon.edu's message of 10 Mar 94 16:36:57 In article <COGSWELL.94Mar10163657@creampie.cs.uoregon.edu> cogswell@creampie.cs.uoregon.edu (Bryce Howard Cogswell) writes: You have to hack the kernel code. There is a small test that checks if two devices are at the same address and ignores the second if so. ... BTW: This really belongs in the FAQ. Well, actually there needs to be a new config option for simply saying "psm0 .. noconflict" or something in the kernel config file so that you can disable it on a per-device basis. This would be a bit hard, since you'd need to then keep track of the devices so marked, which is probably why it's not done yet. Even simpler would be: options ALLOW_CONFLICT But I'm not sure that it would be very popular with the purists.. :-) Jordan