Date: Wed, 4 May 2011 09:00:02 -0400 From: John Baldwin <jhb@freebsd.org> To: Michael Butler <imb@protected-networks.net> Cc: freebsd-current@freebsd.org Subject: Re: cardbus memory allocation problem Message-ID: <201105040900.02840.jhb@freebsd.org> In-Reply-To: <4DC09489.6060804@protected-networks.net> References: <4DBF68A4.6050405@protected-networks.net> <201105030758.12792.jhb@freebsd.org> <4DC09489.6060804@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, May 03, 2011 7:49:29 pm Michael Butler wrote: > > I have WIP patches to fix this but they aren't ready yet. > > > >> pcib4: I/O decode 0x4000-0x4fff > >> pcib4: memory decode 0xf0900000-0xf09fffff > >> *** this memory widow is what I expected all children to allocate from > >> > >> pcib4: no prefetched decode > >> pcib4: Subtractively decoded bridge. > > > > It's a subtractive bridge, so the resources do not have to be allocated from > > the window. That said, I'm committing the last of my patches to HEAD today to > > rework how PCI-PCI bridges handle I/O windows to support growing windows, etc. > > and the new PCI-PCI bridge driver will attempt to grow the memory window to > > allocate a new range before falling back to depending on the subtractive > > decode. > > You might be pleased to hear that, without any "special arrangements" in > loader.conf, the new PCI-PCI code does The Right Thing with memory > allocation :-) > > Parent bridge: > > I "fixed" the subordinate bus using "setpci -s 07:06.2 4c.b=02" I believe it should work even if you don't disable subtractive decoding. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105040900.02840.jhb>