PCIe and M.2: licence terms
AbstractBefore you build a PCIe card, the base and card specifications cost a non-member $9,000. Buying the rules settles the reading bill; it does not buy implementation permission.
You have a network adapter, storage controller or accelerator to make. The computer has a PCIe slot. Before the first prototype, there is the document, the patent arrangement and the permission to label the result.
PCI-SIG describes a link serving “enterprise, desktop, mobile, communications and embedded platforms” (FAQ). The connection is common. Access to its terms has a price.
A price on reading
For a non-member, the PCIe base specification is $4,500 and the card specification is another $4,500. A design needs both: $9,000 in hard copies. The CD of PDFs containing all current specifications is $6,000. Annual membership is $5,000, with online access, revisions and addenda included (order form; membership packet). Anyone may join. It costs less than buying the documents without joining.
Members pay $50 per printed specification or $75 for the CD. M.2 uses the same non-member hard-copy price, covering a module format used for Wi-Fi, Bluetooth and solid-state storage. Under the three tests, neither format passes Read. A large manufacturer can budget for membership. A student’s first prototype has the same annual fee.
Payment leaves conditions on the text. The specifications page requires written consent for certain uses in commercially available AI systems, including “creating, training, enhancing, developing, maintaining, or contributing to” them. How that condition binds a purchaser, as distinct from a member, is unspecified. The copy is paid for. Its permitted uses remain a question.
Reading is not building
Article 15 of the bylaws sets out the patent arrangement. A member commits to offer fellow members and affiliates licences on “reasonable terms and conditions that are demonstrably free of any unfair discrimination”. Royalties may be among those terms.
This is a promise to offer a licence, not a licence already granted. Its scope covers the compliant portion of a product, excludes design patents, and neither requires nor forbids a grant to a non-member. A member can withdraw before a specification takes effect and avoid the commitment; commitments for specifications already adopted survive.
You can therefore spend $4,500 on the document without entering this arrangement. Membership gets you an offer of terms, possibly with royalties.
The patent licence is still to come.
A controlled compliance label
Now the card works. PCI-SIG’s Trademark and Logo Usage Guidelines reserve its marks for members, with a licence-agreement route for non-members. A member’s compliant label requires PCI-SIG testing and an Integrators List entry. Your own test results do not complete the process.
The compliance programme requires a minimum of 80 percent on interoperability tests and all required compliance tests. Its workshops let members test against other members’ products. An Authorized Test Lab Program also covers PCIe 4.0 and 5.0; non-member access was not established. Nor was continued application of the older trademark guidelines confirmed.
You have made a working card. The right to call it compliant is separate.
No way round
If the terms do not suit the project, choose another host connection. The nearby specifications offer different layers, different conditions, or PCIe.
| Specification | What it is | Terms |
|---|---|---|
| CXL | Protocol on the PCIe physical layer | Evaluation licence, internal use only |
| UCIe | Die-to-die link inside a package | Download agreement grants no right to implement (2.0 and 3.0) |
| Ethernet (IEEE 802.3) | Packet network | Free to read under the GET IEEE 802 programme; patents under a reasonable-terms policy |
| virtio (OASIS) | Device model | Non-assertion covenant; runs over PCI, MMIO or Channel I/O transports |
| OCP NIC 3.0 | Card format | Royalty-free grant for compliant cards; the cards carry PCIe |
| OAM | Accelerator module | Royalty-free grant; host link PCIe by default |
OCP’s grants cover the card formats’ content. OAM’s agreement excludes referenced specifications even when compliance requires them; its alternate host-protocol pin has no protocol defined. The card can be royalty-free while the connection brings you back to PCIe.
An open-source core changes the code licence. LitePCIe is BSD-licensed; verilog-pcie has an MIT-style licence. Both use an FPGA vendor’s hard PCIe block. Neither software licence supplies patent rights under article 15.
The code is open. The connection still has terms.
The connection is infrastructure
A student or small maker can have the skill and the design while lacking the permissions needed to turn it into a product. These are conditions on a connection between ordinary computer parts. They decide who can take part.
Standards need funding. Charging for membership is one arrangement, not a requirement of writing a specification. OCP grants royalty-free rights for its own card-format content. The RISC-V instruction set is free to read; its FAQ states “There is no fee to use the RISC-V ISA”.
Agenxy treats a host connection as essential computing infrastructure. A future link should publish the physical and transaction rules without a fee or membership, grant every implementer the necessary patent claims royalty-free, and let a passing product state its conformance under a published test. OCP card formats and virtio address other layers; none of the host links examined here provides that combination.
The student should be able to build the part. Learning its rules, making it and accurately describing the result should not require admission to a body. A useful connection should connect the parts, not qualify their makers.
Sources
The order-form prices cover PCIe base 7.0, CEM 6.0.1 and M.2 revision 5.1; archive capture: 4 January 2026. M.2’s application list is in revision 1.0, 1 November 2013, section 1.2. Bylaws approved 16 December 2025: sections 15.1 and 15.3 (scope), 15.2 (withdrawal), 15.3 (licence commitment), 15.5 (non-members), 15.7 (royalties) and 15.10 (survival).
The trademark guidelines are the 34-page PDF with updated_112206 in its filename and a creation date of 22 November 2006. Their exact conditions include “THE PCI-SIG LOGOS AND TRADEMARKS MAY BE USED BY PCI-SIG MEMBERS ONLY” and “NON-MEMBERS MAY NOT USE OUR LOGOS AND TRADEMARKS UNLESS THEY FIRST EXECUTE A LICENSE AGREEMENT WITH PCI-SIG.” The compliance-page capture is dated 7 January 2026; the live page presented a bot challenge. The FAQ capture is from 2025.
UCIe’s download terms restrict access to “solely for the End User’s own non-commercial, internal evaluation purposes” and state that “nothing in this Agreement shall be deemed as granting” a licence “to implement the UCIe Specification”.
Remaining source texts:
- CXL specification download.
- UCIe 2.0 download agreement.
- UCIe 3.0 download agreement.
- GET IEEE 802 programme agreement.
- IEEE patent policy, section 6.
- virtio 1.4.
- OASIS IPR policy.
- specification 1.6.0.
- OCPHL-P 1.0.
- base specification r2.0.
- OWFa 1.0 as modified by OCP.
Sources were consulted on 10 October 2026, with subsequent checks on 22 October 2026.