Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Jan 2004 15:08:10 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        pete@altadena.net
Cc:        current@freebsd.org
Subject:   Re: allow_unsupported_io_range
Message-ID:  <20040117.150810.62651340.imp@bsdimp.com>
In-Reply-To: <20040117.133410.17267747.imp@bsdimp.com>
References:  <20040117141129.GA28446@users.altadena.net> <20040117.133410.17267747.imp@bsdimp.com>

index | next in thread | previous in thread | raw e-mail

In message: <20040117.133410.17267747.imp@bsdimp.com>
            "M. Warner Losh" <imp@bsdimp.com> writes:
: In message: <20040117141129.GA28446@users.altadena.net>
:             Pete Carah <pete@altadena.net> writes:
: : Someone removed (or changed) "hw.pci.allow_unsupported_io_range".  This breaks
: : LOTS of laptops, in particular the pccard hardware.  Causes a hang after
: : init is started...
: 
: That was me.  Before, we handled bridges incorrectly.  I did add one
: item to the allocation stuff.  We now have a higher chance of
: collision of resources, which causes the problems.

I've committed some code that restores the old resource allocation
scheme to pci_pci.c.  The new one will be needed for the lazy resource
allocation patches I'm working on, but I'll resolve those issues.

Warner


help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040117.150810.62651340.imp>