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

PoC: x230-fhd_edp (on top of efifb next steps) [coreboot 4.22+) #1524

Closed
wants to merge 9 commits into from

Conversation

tlaurion
Copy link
Collaborator

@tlaurion tlaurion commented Nov 10, 2023

DO NOT FLASH yet. This is build test and regression test for x230 and x230-fhd (non-hotp) for #1523.

There is an observable tendency of everybody forking coreboot... But I still prefer pointing to releases with pending patches in files then forking and maintaining patches in fork, in the goalof tracking files related to patches on top of chosen releases in the goal of seeing those patches merged upstream...) as currently defined under modules/coreboot (since 4.22 is not yet released and I would love to see fhd/edp merged upstream) and have Heads users test fhd on top of ~4.22 so that it has a chance of being under 4.22...

So here we have:

  • patches/coreboot-x230fhd-x230fhd/7a42712.patch created per git fetch https://review.coreboot.org/coreboot refs/changes/50/28950/23 && git format-patch -1 --stdout FETCH_HEAD > ~/heads/patches/coreboot-x230fhd-x230fhd/7a42712.patch on top of coreboot commit 42f1fef5a620e98e7ece6a60744992265cc409d7
  • config/coreboot-*.config automatically adjusted per
    • make BOARD=x230-maximized coreboot.save_in_oldconfig_format_in_place
    • make BOARD=x230-maximized-fhd_edp coreboot.save_in_oldconfig_format_in_place

Only last commit is relevant here (atop of #1522 fixes)

…iommu=igfx_off, add CONFIG_BOOT_KERNEL_REMOVE=intel_iommu=on intel_iommu=igfx_off, remove quiet removal from CONFIG_BOOT_KERNEL_REMOVE. TLDR: do not interfere with OS setting its own boot policies

Signed-off-by: Thierry Laurion <[email protected]>
…s. TODO: check linux config to see if enabling automatically works as expected.

Signed-off-by: Thierry Laurion <[email protected]>
…all intel boards touched in past commit

Touches c216, x230-flash, x230-legacy and x230-maximized.
TODO: Other boards, including AMD ones (qemu/kgpe) have this ON, including nv41/ns50 (which uses i915drm which most probably causes problems)
 Note that qemu boards use q35 in config, but were made to have both i440fx and q35, where q35 is tested, which explains why its on by default there.

Signed-off-by: Thierry Laurion <[email protected]>
Taken from : https://github.com/Nitrokey/heads/tree/temp-release-v2.3

- Move branding/Heads/bootsplash-1024x768.jpg -> branding/Heads/bootsplash.jpg (We don't care about the size. Make filename generic)
- Adapt all coreboot configs so bootsplash is adapted by BRAND_NAME CONFIG_BOOTSPLASH_FILE="@BRAND_DIR@/bootsplash.jpg"
  - Reminders :
    - Makefile changes Heads to defined BRAND_NAME in board config
    - Makefile changes -e 's!@BRAND_DIR@!$(pwd)/branding/$(BRAND_NAME)!g'
- nv41/nv50
  - coreboot oldefconfigs adapted by:
    - make BOARD=nitropad-ns50 coreboot.modify_and_save_oldconfig_in_place
    - make BOARD=nitropad-nv41 coreboot.modify_and_save_oldconfig_in_place
  - linux oldefconfigs adapted by
    - make BOARD=nitropad-nv41 linux.modify_and_save_oldconfig_in_place
      - since this is shared config across nv41/ns50: it only needs to be done for a single board

Signed-off-by: Thierry Laurion <[email protected]>
…t for qemu/flash boards

Signed-off-by: Thierry Laurion <[email protected]>
…overriden

TODO: linuxboot still not touched...
Signed-off-by: Thierry Laurion <[email protected]>
…ix coreboot config path to bootsplash

Signed-off-by: Thierry Laurion <[email protected]>
@tlaurion tlaurion marked this pull request as draft November 10, 2023 17:56
@tlaurion
Copy link
Collaborator Author

tlaurion commented Nov 10, 2023

Builds happening for x230-maximized and x230-maximized-fhd_edp (non-hotp) below under checks.

…mized and x230-maximized-fhd_edp for regression test on x230 and single user test

patches/coreboot-pre422-x230fhd/7a42712.patch created per git fetch https://review.coreboot.org/coreboot refs/changes/50/28950/23 && git format-patch -1 --stdout FETCH_HEAD > ~/heads/patches/coreboot-pre422-x230fhd/7a42712.patch on top of coreboot commit 42f1fef5a620e98e7ece6a60744992265cc409d7 as specified under x230fhd coreboot fork defined under modules/coreboot

Signed-off-by: Thierry Laurion <[email protected]>
@tlaurion
Copy link
Collaborator Author

tlaurion commented Nov 10, 2023

misnamed x230-maximized for x230-hotp-maximized under circleci, which created caches that were invalid....
Rebuilding with proper naming under 428c33a for coreboot fork (pre422) and patches under patches/coreboot-pre422-x230fhd with revised coreboot module config (CircleCI caches per module definition consistency (hashes) so needed to invalidate those and used the chance to proper name.

@tlaurion
Copy link
Collaborator Author

tlaurion commented Nov 10, 2023

@pcm720 sorry for the noise. Testing for #1524 on top of coreboot 4.22 (to be released soon) will be here.
Sorry if that was unclear for the needed testing so that fhd is merged upstream over coreboot and maintained patches are deleted under Heads tree (that's the goal!)

@pcm720
Copy link

pcm720 commented Nov 10, 2023

I just don't mind testing both :)
Glad to see this patch finally getting closer to being merged upstream!

@tlaurion
Copy link
Collaborator Author

tlaurion commented Nov 14, 2023

Not forgot, but doesn't build. Patches are being worked on upstream which when I receive signal will update PR to point to proper fixed pre 4.22 commit and fhd patch to have user reports of x230 fhd so that hopefully is part of 4.22 this time.

@tlaurion tlaurion changed the title PoC: x230-fhd_edp (on top of efifb next steps) PoC: x230-fhd_edp (on top of efifb next steps) [coreboot 4.22+) Nov 26, 2023
@tlaurion
Copy link
Collaborator Author

tlaurion commented Feb 5, 2024

Superseeded by #1604

@tlaurion tlaurion closed this Feb 5, 2024
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