-
Notifications
You must be signed in to change notification settings - Fork 904
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
Replace pflash with direct MTD access. #553
Comments
There is not support for parsing the FFS TOC in power. We did a prototype it but didn't stick. Point 1 and 3 are mutually exclusive. I think we should design for 3, which means the mtd device is present in the device tree and is always owned by the BMC. |
If we want to design for 3 we need to ensure the host firmware team is on board and ready to go for that. We also need a plan for what to do with userspace on P8 machines. It is also a pain to have two different implementations. |
remove pflash as part of cleanup |
We will be removing pflash in favor of UBI-managed volumes. |
Don't remove it until the alternative exists. AFAIK the current pflash will use /dev/mtd when available and has the whole FFS stuff we need when updating skiboot etc... So until you have the new UBI stuff, please keep pflash around |
In #542, @shenki suggested it may be better to use direct MTD access provided by the kernel instead of pflash's direct register manipulation. We need to better understand what the design for that would be and then an appropriate refactoring of the host flash code.
My immediate thoughts and questions would be:
The text was updated successfully, but these errors were encountered: