Date: Mon, 11 Dec 2006 11:26:45 +0100 From: Andre Oppermann <andre@freebsd.org> To: John Polstra <jdp@polstra.com> Cc: freebsd-arch@freebsd.org Subject: Re: Where do MSI quirks belong? [patch] Message-ID: <457D3265.7070004@freebsd.org> In-Reply-To: <095D8C4E-5C80-451A-8DF9-C3B307A0F603@polstra.com> References: <XFMail.20061119201122.jdp@polstra.com> <200611201242.58088.jhb@freebsd.org> <095D8C4E-5C80-451A-8DF9-C3B307A0F603@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote: > > On Nov 20, 2006, at 9:42 AM, John Baldwin wrote: > >> It's going to be a function of the chipset, as something in the chipset >> (presumably a Host -> PCI bridge) has to listen for writes to >> 0xfeeXXXXXX and >> convert them into APIC messages. There are two ways I planned on >> doing this: >> >> 1) Allow PCI-PCI bridges to be blacklisted, and the pcib_alloc_msi[x]() >> methods would compare the bridge's device id against a blacklist. >> This can >> matter if you have virtual PCI-PCI bridges that really a HT -> PCI >> bridge or >> the like. >> >> 2) Blacklist chipsets in the x86 MD code based on the device ID of the >> first >> Host -> PCI bridge at device 0.0.0. > > I have implemented both of these checks, except that I put #2 into the > MI code since I couldn't find any reason to make it x86-specific. > Here's the patch. Does it look OK to you? It works fine here. IIRC it is not only a chipset problem but also sometimes how a MSI capable chipset is wired on the mainboard. So some probing would have to be done as well. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?457D3265.7070004>