SA260324R-0337
① SA Source
- Source: 開啟完整 SA 文章
- Section:
AlphaWave 112G Serdes in LP30 - Line hint:
429
Context Before
Here, we will discuss our findings on where we see there are big changes in content for the supply chain coming out of all these announcements at GTC.
AlphaWave 112G Serdes in LP30
Evidence
It may surprise readers that Qualcomm has IP in the Groq LPU 3 chip! More specifically it is AlphaWave, which Qualcomm acquired last year, that is providing the 112G SerDes for Groq’s C2C. AlphaWave was selected as the only IP provider that has high speed SerDes for Samsung Foundry. It was AlphaWave’s SerDes that caused issues for Groq LPU 2. Alphawave will continue to be used for the LP35, but Nvidia will of course use their own NVLink SerDes IP from LP40 when it transitions back to TSMC.
Context After
LPX PCB
Next, we mentioned that a very high spec PCB is required for the LPX compute tray. We estimate that each compute tray main board PCB will carry $7k ASP. The suppliers for this are Victory Giant and WUS. Of course, there are several other PCB modules in the compute tray, but they do not need a high spec. Nvidia is continuing with their cable-less philosophy similar to the Vera Rubin compute tray which requires a lot of board-to-board connectors, which brings us to the next big beneficiary.
② Atomic Claim
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/Alphawave Semi",
"label": "AlphaWave"
},
"role": "provider"
},
{
"node": {
"id": "04_knowledge_base/SerDes",
"label": "SerDes"
},
"role": "technology"
},
{
"node": {
"id": "04_knowledge_base/Groq LPU",
"label": "Groq LPU"
},
"role": "affected_product"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"2"
],
"temporal_mentions": []
},
"relation_type": "SERDES_CAUSED_LPU_ISSUES"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| provider | AlphaWave | 02_companies/Alphawave Semi |
| technology | SerDes | SerDes |
| affected_product | Groq LPU | 04_knowledge_base/Groq LPU |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
AlphaWave 的 SerDes 曾造成 Groq LPU 2 的問題。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/Alphawave Semi",
"label": "AlphaWave"
},
"role": "provider"
},
{
"node": {
"id": "04_knowledge_base/SerDes",
"label": "SerDes"
},
"role": "technology"
},
{
"node": {
"id": "04_knowledge_base/Groq LPU",
"label": "Groq LPU"
},
"role": "affected_product"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"2"
],
"temporal_mentions": []
},
"relation_type": "SERDES_CAUSED_LPU_ISSUES"
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "COMPLETE"
}⑥ Human Review
請在 Properties 逐項確認：
- 原文 → Atomic Claim 是否忠實
- Atomic Claim → Semantic Frame 是否忠實
- Canonical Entity mapping 是否正確
- Epistemic mode 是否保留原文語氣
- 最後選擇
review_action
Review state
Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。