Skip to content
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

DDR5 support: fix DIMM, memport numbering #29

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aravynd
Copy link
Collaborator

@aravynd aravynd commented Oct 9, 2023

Fix the indexing for memport and DIMMs

Fix the indexing for memport and DIMMs

Signed-off-by: Aravind T Nair <[email protected]>
Copy link
Collaborator

@RameshIyyar RameshIyyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you make sure that the index property of the non-DDR5 systems memport and dimm target index value matched? I think the FAPI_POS attribute value is not a relative index within one processor.

If the index is not matching then, there is a chance that the guard record or persisted info (device tree) will cause an issue i.e. it may pick the wrong target...

The index property which is used for the pdbg backend, expects the value should be "relative within its parent node to pull the respective target".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants