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 of X230 board with FHD mod #165

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

jyvet
Copy link
Contributor

@jyvet jyvet commented Aug 25, 2020

The strategy would be the following in order to make a release: find the latest coreboot commit on which the latest version of the FHD patch (https://review.coreboot.org/c/coreboot/+/28950) can be applied. Allowing to cherry-pick the patch makes the future releases more flexible as it may apply without conflict on a newer version of coreboot.

The first patch of this serie allow to cherry-pick a patch which is hosted on the gerrit owned by coreboot.org.
The second patch creates a x230_fhd directories. f5b3a49b76 commit is used as the FHD patch does not apply on 24e6221706 (coreboot commit used by skulls-x230-0.1.10).

This patch adds the -p/--patchset option to cherry-pick
a patchset on the top of a coreboot tag or commit. The patchset
should be submitted for review (not necessarily merged) to
the gerrit owned by coreboot.org.
@jyvet
Copy link
Contributor Author

jyvet commented Aug 25, 2020

I'll test the generated binaries (free & nonfree) after a first round of reviews. My setup: nitrocaster mod + LG LP125WF4-SPB1.

@jyvet
Copy link
Contributor Author

jyvet commented Aug 31, 2020

I've just tested the binaries. There is a tiny issue I'm not sure to be able to fix: The splashscreen is displayed but when pressing ESC, the screen goes black and I'm not able to see the menu with the different payloads. I'm able to control the backlight and the screen is turned off when the laptop is closed.

Any idea how to fix the boot menu?

@merge
Copy link
Owner

merge commented Nov 6, 2020

doesn't cherry-picking break reproducibility? I think we need to know the final git HEAD we build which won't be possible with this.

@jyvet
Copy link
Contributor Author

jyvet commented Nov 13, 2020

I'm sorry, I'm not sure to understand. With this PR, skulls would apply the FHD patch on the top of a known git HEAD. It does not checkout the version of the FHD patch on which it was originally rebased on. 

To me a release would be fully reproducible. Assuming: 

  • coreboot version is based on the commit hash used contained in the name of the config files (e.g.  x230_fhd/free-defconfig-f5b3a49b76 and x230_fhd/nonfree-defconfig-f5b3a49b76).

  • x230_fhd/build.sh contains the patch set revision to apply (e.g. revision 12 with --patchset refs/changes/50/28950/12 x230_fhd).   

From previous examples, if the refs/changes/50/28950/12 x230_fhd patch set applies on the top of f5b3a49b76, then the version can be compiled, tested and released (and reproducibility is ensured).

So basically when preparing a new release, we would need to ensure the patch set applies (revision 12 in my example) on the top of the new git HEAD. If it does not apply, we can modify x230_fhd/build.sh to use a newer revision of the FHD patch set (revision 13 would be  --patchset refs/changes/50/28950/13 x230_fhd).

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.

2 participants