Date: Thu, 08 Jun 1995 14:10:04 -0700 From: Gary Palmer <gpalmer@westhill.cdrom.com> To: Jim Bryant <jbryant@argus.iadfw.net> Cc: freebsd-hackers@freebsd.org Subject: Re: options "ALLOW_CONFLICT_IOADDR" don't work! Message-ID: <8777.802645804@westhill.cdrom.com> In-Reply-To: Your message of "Thu, 08 Jun 1995 15:47:08 CDT." <199506082047.PAA01443@argus.iadfw.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199506082047.PAA01443@argus.iadfw.net>, Jim Bryant writes: >options "ALLOW_CONFLICT_IOADDR" does not work!@# >------------------------------------------------------------ >FreeBSD 2.0.5-ALPHA #0: Wed Jun 7 20:08:02 CDT 1995 > jbryant@argus.iadfw.net:/usr/src/sys/compile/ARGUS >CPU: i486DX (486-class CPU) >real memory = 20840448 (5088 pages) >avail memory = 18968576 (4631 pages) >Probing for devices on the ISA bus: >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: VGA color <16 virtual consoles, flags=0x0> >psm0 not probed due to I/O address conflict with sc0 at 0x60 >------------------------------------------------------------ >This did work previous to ALPHA [in 950412-SNAP]. I really hate to say this, by RTFM!!!!! It is documented in LINT the correct solution to this problem - ALLOW_CONFLICT_IOADDR was a HACK of the gross order, and there is now another field in the device declaration line which allows conflicts. See LINT for more. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8777.802645804>