[AS9716-32D]:Support 0x57 and 0x56 eeprom #4103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
[AS9716-32D]:Add to support 0x57 and 0x56 eeprom
- How I did it
Modify accton_as9716_32d_util.py and eeprom.py to check i2c 0x57 exist or not. If yes, it is new board. So create 0x57 sysfs. If no, create 0x56 for old board. For eeprom.py that check 0x57 and 0x56 sysfs to provide information to caller.
- How to verify it
root@sonic:/home/admin# decode-syseeprom
TlvInfo Header:
Id String: TlvInfo
Version: 1
Total Length: 53
TLV Name Code Len Value
ONIE Version 0x29 13 2018.08.00.03
Base MAC Address 0x24 6 80:A2:35:C6:69:22
Vendor Name 0x2D 9 ACCTON_EC
Diag Version 0x2E 11 0b.01.00.15
CRC-32 0xFE 4 0x894390A7
(checksum valid)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)