From owner-freebsd-hackers Thu Jun 8 14:10:18 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA28603 for hackers-outgoing; Thu, 8 Jun 1995 14:10:18 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.57]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA28597 for ; Thu, 8 Jun 1995 14:10:16 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id OAA08779 ; Thu, 8 Jun 1995 14:10:04 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Jim Bryant cc: freebsd-hackers@freebsd.org Subject: Re: options "ALLOW_CONFLICT_IOADDR" don't work! In-reply-to: Your message of "Thu, 08 Jun 1995 15:47:08 CDT." <199506082047.PAA01443@argus.iadfw.net> Date: Thu, 08 Jun 1995 14:10:04 -0700 Message-ID: <8777.802645804@westhill.cdrom.com> From: Gary Palmer Sender: hackers-owner@freebsd.org Precedence: bulk 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