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

reports: dasharo-hcl-report: remove board_config call #8

Merged
merged 1 commit into from
May 9, 2024

Conversation

TomaszAIR
Copy link
Contributor

Running HCL on platforms that are not listed in board_config ends on exiting the script. Calling that function was added while working on APU support, as there is multiple flash chip detected when try to use flashrom on that platform so chip name definition was added to specific platform in board_config.

There is no need for that as check_flash_chip function check one by one known chips from the list defined as FLASH_CHIP_LIST (in dts_environment) and uses one, that does not return error when flashrom is invoked.

Later in HCL we uses check_intel_regions func which needs PROGRAMMER_BIOS variable but this is by default defined in dts_enviroment as internal so in HCL we can assume to use this programmer for every platform.

Running HCL on platforms that are not listed in board_config ends on
exiting the script. Calling that function was added while working on APU
support, as there is multiple flash chip detected when try to use
flashrom on that platform so chip name definition was added to specific
platform in board_config.

There is no need for that as check_flash_chip function check one by one
known chips from the list defined as FLASH_CHIP_LIST (in dts_environment)
and uses one, that does not return error when flashrom is invoked.

Later in HCL we uses check_intel_regions func which needs
PROGRAMMER_BIOS variable but this is by default defined in
dts_enviroment as `internal` so in HCL we can assume to use this
programmer for every platform.

Signed-off-by: Tomasz Żyjewski <[email protected]>
@TomaszAIR TomaszAIR requested review from macpijan and DaniilKl April 18, 2024 09:00
@TomaszAIR
Copy link
Contributor Author

Tested on APU, by running hcl there, logs - https://paste.dasharo.com/?753f7115cbea70bd#23UKN1Japa9iTDMoh85uLKaqzPSUwMxaRNFbUyp1uTuh

Also tested on BoltGate machine (to check this on any, non supported platform), logs - https://paste.dasharo.com/?74b50160dbc6afe6#Ahngd5eh5G9R5pRhJSExUEANajqH9atRuGn9gpU27Tbi

@DaniilKl
Copy link
Contributor

Running HCL on platforms that are not listed in board_config ends on exiting the script.

@macpijan, bad error handling might be the problem here.

@TomaszAIR
Copy link
Contributor Author

@DaniilKl you did approve this, can you merge?

@DaniilKl DaniilKl merged commit e59da61 into main May 9, 2024
@DaniilKl DaniilKl deleted the fix-hcl-nonsupported branch May 9, 2024 09:56
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.

3 participants