-
-
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
merge dgpu-t430 configs #1176
merge dgpu-t430 configs #1176
Conversation
Maximized boards being supported here only. I do not have a board to test. But these have been tested as working by another user (see #1057 (comment)).
Add support for t430 dgpu-versions
…d configs point to them
…d configs point to them
…for FL1 files only. Also add sudo calls where required still need correct code in line 64
@walliams ! Awesome, t430-dgpu owners will be happy (where documentation on disassembling and supported platforms is totally out of date (non-existing) in regard of t430 w530 t530 in wiki and users confused that only x230 i documented.) I would love to see a at least a reference in the boards configs to the blobs required/included in the coreboot configurations, otherwise hidden under coreboot configuration file alone, also a pointer to the script that is required to be ran to have the blobs put in place, and a reference to the README in the blobs dir, even more if that needs to have nvramutil ran to configure things properly (might not be, i'm still not super knowledgeable about the dgpu requirements and mix dgpu requirements myself of the lately added dgpu boards)? @walliams : since you are owner of all those boards, are you up to drafting some documentation updates, at least in regard to this t430-dgpu additional board support ? Last time I agreed for doc to follow board addition, that documentation..... never followed. And flows millions of questions from Heads community because doc is missing.... https://osresearch.net/Contributing-to-Heads-wiki/ Any suggestion welcome on that level. Documentation is a burden as of now. I don't seem to place myself properly as a non-technical user when producing doc content :| Affected links: |
happy to help with documentation on xx30-dgpu models as my next task. didn't notice that even the existing dgpu configs lack reference to vbios blob scripts... that could be improved. i can work on that as well. also, any clue why the circleci check failed here? i didn't change anything related to the x230, though these boards do reference x230-hotp-maximized in .circleci/config.yml |
@walliams please rebase on master.... mbetls is not downloadable from its main website, the website is broken. I just merged the change so that download happens over githib instead. CircleCI is failing for race conditions, I have to kick the builds on merging... This is annoying but will change when updating coreboot and linux kernels.... |
Houla. git fetch master Should be an empty commit. Now we have an undesired commit in this branch :/ |
o darn. sry i'm new to this. do i need to setup a github desktop cli or something |
i can just close this and redo my branch. i don't want to create any more work for anyone else |
Those are from command line? |
i'm just confused about doing this from cli... i forked the repo and edited this all in browser. |
just github.com web interface, via firefox. is this something i can do here, or do i need to clone to a local repo and run commands? sorry. am git noob |
i mean i build heads in a debian vm, with manually inserted code for the t430-dgpu, but my fork and PR here were all done on the web interface because the only git commands i know are clone and pull. |
i'll just make a new PR once i figure out what i'm doing. thanks for the pointers |
Well, I can quickly fix this, create a PR. |
sourced from eganonoa/heads and edited. conflicts should be resolved now