clm_618e2fc7dc9b4f0fa5332d0aa4d139b7_r1

2025-11-28_tpuv7-google-takes-a-swing-at-the::TPU7-0025

① SA Source

• Source: 開啟完整 SA 文章
• Section: What does this mean for Nvidia?
• Line hint: 637

Context Before

This is where MediaTek comes in who is much more flexible on the custom silicon model. With MediaTek, Google is on the way to moving to a “Customer Owned Tooling” model where the end customer owns and is responsible the entire design end to end. This is the point where custom silicon because truly vertically integrated and the end goal of every hyperscaler. This is ambitious, as it would require the hyperscalers to have full end to end silicon capability like one of major silicon design houses.

For TPU V8X, Google was still assisted by MediaTek on the compute side of things with MediaTek owning the tapeout at TSMC and providing their 3nm design libraries to the Google engineering team. Without Broadcom holding their hand, taping out this chip took much longer than expected but this finally happened this quarter.

Evidence

What moves the needle in a big way is that with MediaTek, Google can directly procure HBM from primarily SK Hynix, rather than have it go run through the COGS of a silicon house and have margin stacked on it.

Context After

While the big change in TPU V8 is that Google is working with 2 design houses, engineering resources seemed to have been spent adapting to this new model and ramping up their collaboration with MediaTek. We were the first to reveal the dual track approach and have constantly been sending status updates on the TPUv8 projects as it has huge implications for Broadcom and Mediatek in the Accelerator Model. ↗

The result is that the gen-on-gen TPUv8 performance uplifts are much milder relative to what Nvidia plans achieve with Rubin in terms of both compute and memory. For external customers the TCO per effective FLOP advantage remains, but it is much narrower than Ironwood compared to Blackwell.

② Atomic Claim

透過 MediaTek 合作模式，Google 可主要向 SK Hynix 直接採購 HBM，避免 HBM 經 silicon design house COGS 再加 margin。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/GOOG",
        "label": "Google"
      },
      "role": "buyer"
    },
    {
      "node": {
        "id": "02_companies/MediaTek",
        "label": "MediaTek"
      },
      "role": "partner"
    },
    {
      "node": {
        "id": "04_knowledge_base/HBM",
        "label": "HBM"
      },
      "role": "memory"
    },
    {
      "node": {
        "id": "02_companies/000660",
        "label": "SK Hynix"
      },
      "role": "supplier"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "DIRECT_HBM_PROCUREMENT"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
buyer	Google	GOOG
partner	MediaTek	MediaTek
memory	HBM	HBM
supplier	SK Hynix	000660

⑤ 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 才是正式決策。