Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
- From: "Naren (Narendra) Sankar" <nsankar@xxxxxxxxxxxx>
- Date: Fri, 23 Jun 2006 08:43:26 -0700
BCM seems to need a blacklist to force MSI off (or at least tg3 iscomplaining
that MSI doesn't work). I guess we can try to contact someone at BCMwould
and ask them if they actually tested it. If they did then enabling it
I just got forwarded this discussion on LKML. Unfortunately I am not
subscribed to the mailing list.
I want to clarify that all of Broadcom's AMD chipsets do support MSI and
have done so from the very beginning. The only issue is that we did not
enable the support by default in the hardware. However some platform
vendors are choosing for their own reasons not to use the BIOS required
programming to enable the MSI support in our chipsets. So the current
state of the market is that we have some systems out there that support
MSI on our chipsets and others that do not. We are trying to work with
every vendor to make sure this gets enabled.
MSI is fully tested on our chipsets and the kernel can safely turn it on
on any platform.
The BIOS/kernel programming requirement is that the HyperTransport MSI
mapping be enabled in all the PCIX and PCIe bridges of our chipsets.
Hence PCI register 0xa2 needs to be set to 1, in the standard PCI space
of all our Bridges. This is true for the HT2000, the HT2100 and the
Please cc me if there are any questions.
Chipset Product Line
2451 Mission College Blvd
Santa Clara, CA 95054
Office: (408) 922-7143
Email: nsankar@xxxxxxxxxxxx <mailto:nsankar@xxxxxxxxxxxx>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: Re: GFS2 and DLM
- Next by Date: Re: 2.6.17-mm1
- Previous by thread: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
- Next by thread: RE: Attempt to contact -- ICj