From owner-freebsd-current Sat Mar 30 23:56:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 555B037B41C; Sat, 30 Mar 2002 23:56:55 -0800 (PST) Received: from pool0142.cvx22-bradley.dialup.earthlink.net ([209.179.198.142] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16raCs-00034n-00; Sat, 30 Mar 2002 23:56:55 -0800 Message-ID: <3CA6C12C.3A2B57D1@mindspring.com> Date: Sat, 30 Mar 2002 23:56:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Smith Cc: Alfred Perlstein , scott_long@btc.adaptec.com, mark_salyzyn@adaptec.com, obrien@freebsd.org, current@freebsd.org Subject: Re: asr can not map memory? References: <200203310533.g2V5XMc02681@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael Smith wrote: > > wtf is going on here? > > Your BIOS is assigning a memory range to the card that we don't believe > the bridge passes through. Our check is bogus because (as you see) the > range is actually legitimate (and we booger up some calculations). Add > the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. > > You should have bought a 3ware controller. 8) Apparently, that belief is in error, whenit comes to this bridge, if adding PCI_ALLOW_UNSUPPORTED_IO_RANGE works. What's the basis of the assumption that the I/O range is unsupported in the first place, and why isn't it true for this bridge chip, if it's a valid assumption for others? Give Alfred enough information, and a patch is bound to pop out... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message