Two things are required to get a product on the Integrators List. The first is passing the required Compliance Workshop tests (both compliance and interoperability tests) and the second is to submit a correctly filled out Product Listing Request Form. If your product passed all of the testing requirements, then it is possible PCI-SIG has not yet received your Product Request Form. We require that you fill out an electronic copy of the Product Listing Request Form and send to compliance@pcisig.com. The Product Listing Request form is provided on the PCI-SIG website on our Developers web page and can also be accessed directly by clicking on the above link.
FAQ
Compliance
PCI Conventional
General Information
Please use the Contact Us form available on our Contact Us web page.
Membership information is available on our Membership web page.
A list of the vendor IDs issued to current members can be found on our Member Companies web page.
Please email administration@pcisig.com with your request.
The order form is available on our Ordering Information web page.
PCI-SIG utilizes a secure online portal for credit card payments. Entering your credit card information authorizes PCI-SIG to charge your card the amount invoiced.
PCI-SIG does not currently support any Open Source projects. The use of Open ‎Source code that implements all or a portion or portions of the PCI Specification is at the users own risk, ‎and PCI-SIG disclaims any liability associated with such unaffiliated and unsponsored code. ‎Typically, Open Source projects have their own licensing terms that would apply to use of ‎code, and the fact that code or code segments reference or implement portions of PCI ‎Specifications give rise to no relationship between PCI-SIG and such Open Source projects.‎ PCI-SIG recommends members seek legal advice to determine that they can comply with legal requirements imposed by applicable licenses when using such Open Source projects.
PCI Express
PCI-SIG holds regular Compliance Workshops in various locations around the world to satisfy the needs of its members. These workshops are intended for members to demonstrate their product's interoperability with those of other PCI-SIG members. Member products that successfully demonstrate interoperability at a workshop are listed on the PCI-SIG Integrators List. Member products that conform to the PCI Express architecture may use the PCI Express logo (registered trademark of PCI-SIG) subject to the PCI-SIG Trademark and Logo Usage Guidelines.
- PCI Express architecture is an industry standard high-performance, general-purpose serial I/O interconnect designed for use in enterprise, desktop, mobile, communications and embedded platforms. It has many state-of-the-art attributes, including:
- PCI compatibility using the established PCI software programming models, thus facilitating a smooth transition to new hardware while allowing software to evolve to take advantage of PCI Express features
- A cost-effective, low-pin count interface offering maximum bandwidth per pin, reducing cost and design complexity and enabling smaller form factors
- Scalable bandwidth of 16.0 GB/s at its initial signaling rate of 2.5 GHz with much higher transfer rates in the future using higher frequency signaling technologies
- Support for multiple interconnect widths via 1, 2, 4, 8, 12, 16 and 32 lane configurations aggregated to match application bandwidth needs Support for new and innovative, hot-plug/hot-swap add-in card and module devices
- Unique, advanced features such as Power Management, Quality of Service and other native functions not available in other I/O architectures
PCI Express - 2.0
But on line 11 of pg. 130, it says downstream port registers are not affected except status update, do these contradict?
- RC sends PME_Turn_off message to EP
- EP doesn't respond with ACK due to delay
- EP responds with PME_TO_Ack message
- EP sends PM_Enter_L23 and not sending ACK.
Can the EP do without ACK?