Date: Sun, 31 Mar 2002 00:19:01 -0800 From: Alfred Perlstein <bright@mu.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Michael Smith <msmith@freebsd.org>, scott_long@btc.adaptec.com, mark_salyzyn@adaptec.com, obrien@freebsd.org, current@freebsd.org Subject: Re: asr can not map memory? Message-ID: <20020331081901.GM93885@elvis.mu.org> In-Reply-To: <3CA6C341.AF6D3FDD@mindspring.com> References: <200203310801.g2V81Dc03587@mass.dis.org> <3CA6C341.AF6D3FDD@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Terry Lambert <tlambert2@mindspring.com> [020331 00:05] wrote: > Michael Smith wrote: > > > 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? > > > > The information was provided in the debugging output and code that Alfred > > supplied in earlier messages. The short answer is "programmer error". > > > > You're walking into another conversation with insufficient context. 8) > > Hey, I'll always sit still for someone willing to give me context... > 8-). > > I was thinking it would be easier to get enough info to Alfred, > and let the patch pop out there. 8-) 8-). Issue is that there's something wonky with the PCI code such that it doesn't realize that the bus hanging off of a bus wants another memory range outside the PCI device's range. I wonder if there should be a flag to allow this? Some sort of escape mechanism? I need sleep. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020331081901.GM93885>