Add th6

[luka-micas]

Why I did it

Add two new products

platform m2-w6950-128oc(TH6P)
ASIC Vendor: Broadcom
Switch ASIC: BCM78910_A0
Port Config:128x800G

platform m2-w6951-64hc-cp(TH6C)
ASIC Vendor: Broadcom
Switch ASIC: BCM78914_A0
Port Config: 64x1600G

code structure summarization:

device/micas

port config about two platform

x86_64-micas_m2-w6950-128oc-r0 (th6p)

• M2-W6950-O128-COPPER - sku for 128x800G copper
• M2-W6950-O128-LPO-N - sku for 128x800G LPO-N
• M2-W6950-O128 - sku for 128x800G normal module
• M2-W6950-Q256 - sku for 256x400G normal module
• others - port common config

x86_64-micas_m2-w6951-64hc-cp-r0 (th6c)

• M2-W6951-64HC-CP - sku for 64x1.6T Cold Plate Platform
• others - port common config

---

platform/broadcom/sonic-platform-modules-micas

platform driver and config

common/app/fw_upgrade

• driver of firmware updating

common/modules

• i2c-designware - driver of AMD I2C adapter
• ixgbe - driver of E610
• s3ip_sysfs - driver of S3IP_sysfs
• others - driver developed by micas

m2-w6950-128oc

• platform config of th6p

m2-w6951-64hc-cp

• platform config of th6c

Work item tracking

• Microsoft ADO (number only):

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[luka-micas]

luka-micas please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Micas Networks"

[luka-micas]

/azp run to run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 2911 in repo Azure/sonic-buildimage-msft

[bingwang-ms]

luka-micas Can you fill PR title and description properly?

[bingwang-ms]

This PR contains two unrelated changes bundled together:

1. 7e0eae6d08 — the actual cherry-pick of #27734 (add TH6 m2-w6950-128oc / m2-w6951-64hc-cp)
2. 393d7aee12 — "Fix Micas compatibility issues on Trixie Debian 13 with kernel 6.12", which touches ~58 files across most existing Micas platforms (w6510-, w6520-, w6920-32qc2x, w6930-64qc, w6940-64oc, common drivers, debian/rules, platform/broadcom/rules.mk/rules.dep, etc.) — this is unrelated to TH6 and isn't mentioned in the PR description at all.

Could you split the Debian 13/kernel 6.12 compatibility fix into its own PR? It affects platforms far beyond the TH6 SKUs this PR is meant to add, so it deserves independent review and its own changelog entry, and bundling it here makes this PR harder to review as a clean cherry-pick.