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

Support for compile time disabling of SPD #2

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

Conversation

pandrej
Copy link

@pandrej pandrej commented Mar 6, 2017

(needed for platforms with soldered memory chips)
Patch includes cleanup of spd module interface allowing for its clean disabling.
Changes:

  • Add SPD_DISABLED config option (config.h)
  • Cleanup of spd module interface (movinf all private functions and variables do spd.c)
  • Disable spd code when SPD_DISABLED option is set (spd.c)
  • Hide 'Display SPD Data' option on the configuration screen is SPD_DISABLED (display.c)

…soldered memory chips)

Patch also includes cleanup of spd module interface allowing for its clean disabling.
Changes:
- Add SPD_DISABLED config option (config.h)
- Cleanup of spd module interface (movinf all private functions and variables do spd.c)
- Disable spd code when SPD_DISABLED option is set (spd.c)
- Hide 'Display SPD Data' option on the configuration screen is SPD_DISABLED (display.c)
@pietrushnic
Copy link
Member

@pandrej I'm not sure if we should do anything with that ? It looks mostly like clean up, do you want to push this to mailing list ?

@mek-x
Copy link

mek-x commented Mar 7, 2017

Looks fine to me. We should try to mainline it and in the meantime we should use this implementation in Pcengines releases. In the future we may think about some way of getting the spd data directly from cbfs. It looks like a standard way for coreboot to incorporate spd data on platform without physical spd.

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.

3 participants