Date: Wed, 21 Apr 2004 23:16:23 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: marcov@stack.nl Cc: freebsd-mobile@freebsd.org Subject: Re: unsupported io range problem Message-ID: <20040421.231623.128865137.imp@bsdimp.com> In-Reply-To: <20040421202556.AC9178A@toad.stack.nl> References: <20040421.035641.105105735.imp@bsdimp.com> <20040421202556.AC9178A@toad.stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040421202556.AC9178A@toad.stack.nl>
marcov@stack.nl (Marco van de Voort) writes:
: > In message: <20040420164920.24EE2D7@toad.stack.nl>
: > marcov@stack.nl (Marco van de Voort) writes:
:
: > >Could it be related to the fact that these devises are attached to bus
: > >PCI1 ?
: >
: > It is related to the fact that the pci bridge really passes all
: > addresses back upstream, rather than the addresses listed in the pci
: > bridge registers. newer versions handle this correctly, completely
: > eliminating the allow_unsupported_io_ranage option. You should try a
: > number higher than 0x20000000 since that's kind of low...
:
: I tried a lot of values 0x2.., 0x4.., 0x6.., 0x8.., 0xe....
:
: all the same result. Are you suggesting I'd have to update to a -current
: kernel?
I'm suggesting that you might have to. I'd checkout a separate
5.3-current tree, and installing with KERNEL=current so that it goes
into /boot/current in case there are major issues. At the 'ok'
prompts, you'll need to type 'unload' and then 'boot current'.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040421.231623.128865137.imp>