-
Notifications
You must be signed in to change notification settings - Fork 1
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
Detect WP and skip the area on users request #6
Conversation
Thank you for your contribution. The flashrom project does not handle GitHub issues or pull requests, since this repository on GitHub is just a mirror of our actual repository. Thus, we would like to encourage you to have a look at on our development guidelines and submit your patch to review.coreboot.org. Issues are handled over our ticket system. If you have questions, feel free to reach out to us. There are multiple ways to contact us. |
oh, we certainly do not want github bot close our PRs here automatically |
0692a9c
to
4a5a8fe
Compare
648c78a
to
f5b65a2
Compare
cf23702
to
9c3ba8d
Compare
Change-Id: I971a07d9d8b16f5c0ead9a9b6de1efe0b69288c9 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Used to control skipping of write-protected part of a chip. Change-Id: Icdc56cb1876aab8f8229cd1a485aa297d8b7b1e9 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Change-Id: I73c9a1a1e348820cc438f347a5e09f348e397fe6 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Change-Id: I5848ea57ec389f2830e92d972ce6fe6c38737509 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
f5b65a2
to
d047111
Compare
Change-Id: Ifcd6cffa22dffd05241515fc30e0f550f89b5b16 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
@krystian-hebel Any more comments to that? Generally, it looks good to me. @tlaurion Do you have any more comments to that? I know you have mentioned somewhere else that in the end it might be difficult to apply this approach to heads. But this MR was focusing on the goal:
which seems to be covered. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Depending on where this will land eventually, notes column in chips.md
may require redacting.
I can only speak from past experience here, but from current documentation, it seems that the user would receive a warning saying that bootblock region is going to have some changes applied PRIOR of applying them, requiring the user to adapt its command line arguments to apply explicitly do the change. As for Heads, or any internal upgrade (think FWUPD) I'm still unsure how that would be implemented. The ideal would be for the user to not do the obviously stupid move of flashing the whole SPI if bootblock region was not expected to change from internal flash upgrade. And I guess some wrapper telling to the user to stay on a same coreboot version branch from GUI output, and/or to externally flash the firmware image on the platform. |
@macpijan @krystian-hebel ping on #6 (comment) Also, looking to find chips.md which seems to have been lost in master/upstream; 94083d0 Was that intended? |
A simple test can look like this: