-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mellanox] Remove EEPROM write limitation if it is software control #17030
Merged
liat-grozovik
merged 7 commits into
sonic-net:master
from
Junchao-Mellanox:master-limit-write
Dec 13, 2023
Merged
[Mellanox] Remove EEPROM write limitation if it is software control #17030
liat-grozovik
merged 7 commits into
sonic-net:master
from
Junchao-Mellanox:master-limit-write
Dec 13, 2023
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
keboliu
approved these changes
Oct 27, 2023
@prgeor kindly reminder to review this PR. |
prgeor
reviewed
Dec 1, 2023
prgeor
approved these changes
Dec 12, 2023
liat-grozovik
approved these changes
Dec 13, 2023
keboliu
pushed a commit
to keboliu/sonic-buildimage
that referenced
this pull request
Dec 19, 2023
…onic-net#17030) - Why I did it When module is under software control (CMIS host management enabled), EEPROM should be controlled by software and there should be no limitation for any write operation. - How I did it Remove EEPROM write limitation if a module is under software control - How to verify it Manual test UT
mssonicbld
pushed a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jan 5, 2024
…onic-net#17030) - Why I did it When module is under software control (CMIS host management enabled), EEPROM should be controlled by software and there should be no limitation for any write operation. - How I did it Remove EEPROM write limitation if a module is under software control - How to verify it Manual test UT
Cherry-pick PR to 202311: #17694 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Why I did it
When module is under software control (CMIS host management enabled), EEPROM should be controlled by software and there should be no limitation for any write operation.
Work item tracking
How I did it
Remove EEPROM write limitation if a module is under software control
How to verify it
Manual test
UT
Which release branch to backport (provide reason below if selected)
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)