Date: Fri, 26 Feb 2010 17:24:23 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-acpi@freebsd.org Subject: Re: Nehalem PCI devices (was Re: Failure to get past a PCI bridge) Message-ID: <201002261724.23396.jhb@freebsd.org> In-Reply-To: <0147D436-C5EA-4FB2-93CF-C9DF54E9CE6A@averesystems.com> References: <0147D436-C5EA-4FB2-93CF-C9DF54E9CE6A@averesystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 26 February 2010 5:00:54 pm Andrew Boyer wrote: > I found this conversation on freebsd-acpi from last year: > http://lists.freebsd.org/pipermail/freebsd-acpi/2009-June/005796.html > > I have a Nehalem box with two CPUs and two IOHs, running an AMI BIOS and FreeBSD 7.1. I'd like to talk to the processor to change some memory controller settings. FreeBSD doesn't appear to detect anything about the processor PCI busses, but I don't speak enough ACPI to say for sure why not. > > The output of 'acpidump -d -t' is at the end of the message. [Compressed now to save everyone's email.] Would someone please look at the ACPI info to tell if the BIOS is reporting the 0xFF and 0xFE busses? > > If it's not, is there a way to talk to a PCI bus that isn't reported or detected? Is bus:dev:fn enough info? > > If this has already been addressed by a newer acpica or pci module, my apologies. I do not see any 0xfe or 0xff busses in your dump. I only see two Host-PCI bridges both of which have valid _BBN methods, so I don't think you would be hitting the issure reported in that thread. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002261724.23396.jhb>