-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add t530 boards #1072
Closed
Closed
Add t530 boards #1072
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 5, 2021
Closed
Have brought boards back up to 4.13 now that master has migrated. |
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
Dec 5, 2021
…rs only) -CircleCI addition. -Removal of t530-flash, w530-flash boards and coreboot configs This is a merger of linuxboot#1071, linuxboot#1072 and linuxboot#1073 so that test builds are available over CircleCI until osresearch/master CircleCI gets unlocked.
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
Dec 5, 2021
…rs only) -CircleCI addition. -Removal of t530-flash, w530-flash boards and coreboot configs This is a merger of linuxboot#1071, linuxboot#1072 and linuxboot#1073 so that test builds are available over CircleCI until osresearch/master CircleCI gets unlocked.
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
Dec 6, 2021
…rs only) -CircleCI addition. -Removal of t530-flash, w530-flash boards, flash scripts and associated coreboot configs (no more legacy boards additions) This is a merger of linuxboot#1071, linuxboot#1072 and linuxboot#1073 so that test builds are available over CircleCI until osresearch/master CircleCI gets unlocked.
Merged per #1074 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a cleaned up PR for adding t530 boards (from #1059) separating the t530 from t520 and w530 for clarity and ease of merging. Boards for flash, maximized and hotp-maximized have been added. I am not intending to support non-maximized boards.
Tested and working on both dGPU and iGPU-only boards. For dGPU Coreboot does not initialize the dGPU using these configs. I do not intend to add support for initializing the dGPU at this stage (it will require some changes to the config file and addition of blobs in the blob directory).
Boards currently point to Coreboot 4.8.1 as that is the default in heads:master, but 4.13 and 4.14 also tested and working.
Note: it can be tricky to properly read the 8MB chip on the T530 and W530 (see #996). This appears to be because the two chips share a power source on these boards (see generally). This is true for both the Rasbperry Pi and the CH431a. There appears to be two workarounds: (1) the Wake on Lan method (which has the one downside of only working once, because it is not supported by coreboot and is, therefore, not available after flashing); or (2) keeping the CMOS battery plugged in, which works also post-flashing. Both methods provide a little extra power to the board and appear to then be sufficient to get enough power to the 8MB chip to get a proper read of it. The Skulls team generally suggest using an external power source with the CH341a, and it's possible that this might help, but I have not tested.