Skip to content

Add config.bcm for accton_as7816_64x to support port breakout.#3638

Open
chiourung wants to merge 1 commit intosonic-net:masterfrom
chiourung:tmp_as7816_breakout_config_bcm
Open

Add config.bcm for accton_as7816_64x to support port breakout.#3638
chiourung wants to merge 1 commit intosonic-net:masterfrom
chiourung:tmp_as7816_breakout_config_bcm

Conversation

@chiourung
Copy link
Contributor

Add four config.bcm for row1, row2, row3 and row4.

Signed-off-by: chiourung_huang chiourung_huang@edge-core.com

- What I did
Modify the config.bcm for breakout.

- How I did it
Reserve the port mapping for breakout.

- How to verify it
Load the config.bcm to the DUT, and check the status

- Description for the changelog

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

Add four config.bcm for row1, row2, row3 and row4.

Signed-off-by: chiourung_huang <chiourung_huang@edge-core.com>
lguohan
lguohan previously approved these changes Oct 21, 2019
@lguohan
Copy link
Collaborator

lguohan commented Oct 21, 2019

what is row{1,2,3,4}? is this for dynamic port breakout?

@chiourung
Copy link
Contributor Author

There is a limitation for port number. Not all ports can be breakout. So user can choose which row can be breakout. There are 64 ports for as7816_64x, and 16 ports for one row. For now, the new config.bcm can be modified for breakout easily. For future, when the broadcom SAI ready, the new config.bcm don't need any modified for breakout.

@lguohan
Copy link
Collaborator

lguohan commented Nov 9, 2019

we do not want multiple config.bcm for a single hardware sku.

@CharlieChenEC
Copy link
Contributor

we do not want multiple config.bcm for a single hardware sku.

I think it is flexible enough to change the pointer in the file "sai.profile" to decide which config.bcm shall be used. Could you tell me what is the reason that "multiple config.bcm" is not acceptable?

@CharlieChenEC
Copy link
Contributor

we do not want multiple config.bcm for a single hardware sku.

I think it is flexible enough to change the pointer in the file "sai.profile" to decide which config.bcm shall be used. Could you tell me what is the reason that "multiple config.bcm" is not acceptable?

@lguohan Could you please provide your concern of using multiple config.bcm? What is your suggestion to deal with the complex port breakout restriction without using this proposed method?

mssonicbld added a commit that referenced this pull request Jun 14, 2025
…lly (#22941)

#### Why I did it
src/sonic-swss
```
* 4fe09b56 - (HEAD -> 202411, origin/202411) [202411] fix dhcp_relay issue on marvell-teralynx (#3638) (2 days ago) [Ravi Minnikanti(Marvell)]
```
#### How I did it
#### How to verify it
#### Description for the changelog
vmittal-msft pushed a commit to vmittal-msft/sonic-buildimage that referenced this pull request Oct 20, 2025
…tomatically (sonic-net#1243)

#### Why I did it
src/sonic-swss
```
* aa21109 - (HEAD -> 202503, origin/202503) Merge pull request sonic-net#97 from mssonicbld/sonicbld/202503-merge (21 hours ago) [mssonicbld]
* 7c1afc6 - Merge branch '202412' of https://github.com/Azure/sonic-swss.msft into 202503 (23 hours ago) [Sonic Automation]
* 9796a41 - Merge pull request sonic-net#94 from mssonicbld/sonicbld/202412-merge (2 days ago) [mssonicbld]
* f8c4199 - Merge branch '202411' of https://github.com/sonic-net/sonic-swss into 202412 (2 days ago) [Sonic Automation]
* 4fe09b5 - [202411] fix dhcp_relay issue on marvell-teralynx (sonic-net#3638) (2 days ago) [Ravi Minnikanti(Marvell)]
```
#### How I did it
#### How to verify it
#### Description for the changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants