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

I would like to know difference between BOOTBRANCH and BOOTBRANCH_BOARD #6167

Open
1 task
buldo opened this issue Jan 15, 2024 · 3 comments
Open
1 task

I would like to know difference between BOOTBRANCH and BOOTBRANCH_BOARD #6167

buldo opened this issue Jan 15, 2024 · 3 comments
Assignees

Comments

@buldo
Copy link

buldo commented Jan 15, 2024

Which feature would you like to have?

I think that documentation miss description for BOOTBRANCH and BOOTBRANCH_BOARD variables.
I trying to add support for luckfox core3566. I already created image with yocto and trying to apply my progress to armbian but not understand some variables.

Funding

Copy link

Jira ticket: AR-2026

@rpardini
Copy link
Member

You're right to be confused. BOOTBRANCH points to the branch/tag/commit to use as git base for u-boot.
BOOTBRANCH is usually defined by family code, before we had extensibility/hooks available, so family code was littered with "if board == xyz then this branch", causing board/family mixups.
BOOTBRANCH_BOARD was introduced as a pre-hooks way to let the board (not the family) set the branch.
Similar was done, I think, for BOOTPATCHDIR?

@buldo
Copy link
Author

buldo commented Jan 15, 2024

@rpardini now I more confused.
Before your answer I used BOOTBRANCH in my board.csc file and build framework understands it without problem.
Moreover more than 10 board definition files use BOOTBRANCH variable.

  1. Have I use BOOTBRANCH_BOARD instead BOOTBRANCH in my board.csc?
  2. If BOOTBRANCH variable prohibited to use in board file maybe it have to be some validations in build steps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants