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.

Sign up for GitHub

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

linux-iot2050: Add the missing kbuildtarget #581

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

linux-iot2050: Add the missing kbuildtarget #581

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1227237
linux-iot2050: Add the missing kbuildtarget
BaochengSu Jan 24, 2025
031769f
linux-iot2050: Mask the upstream recipe
BaochengSu Feb 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions conf/distro/iot2050-debian.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,14 @@ DISTRO_NAME = "IOT2050 Debian System"
HOSTNAME ??= "iot2050-debian"

PREFERRED_VERSION_linux-iot2050 ?= "6.1.%"
PREFERRED_VERSION_linux-iot2050-kbuildtarget ?= "${PREFERRED_VERSION_linux-iot2050}"
PREFERRED_VERSION_linux-iot2050-rt ?= "6.1.%"
PREFERRED_VERSION_linux-iot2050-rt-kbuildtarget ?= "${PREFERRED_VERSION_linux-iot2050-rt}"
Copy link
Collaborator

@jan-kiszka jan-kiszka Feb 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't the missing PREFERRED_VERSION...-native bite you?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we append the -native to the linux-iot2050? How it looks like when it bites us? At least the recipe parsing has no problem and kernel/rt-kernel is building

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You will see multiple provider warnings when bitbake identifies them during parsing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't see any warnings... I guess due to isar version? Let me try

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-kbuildtarget and -native were introduced by the same isar changes. It takes two or more providers for those targets to make bitbake complain. I cannot explain, though, why 6.x-upstream should trigger the warning for kbuildtarget but not for native.

BTW, iot2050-linux-rt should only have one provider at this stage.

So much for the theory...


KERNEL_NAME ?= "cip"

BBMASK:append = " linux-iot2050_.+-upstream\.bb"

PREFERRED_VERSION_customizations ?= "0.1-iot2050-debian"
PREFERRED_VERSION_customizations-debug ?= "0.1-iot2050-debian"

Expand Down
1 change: 1 addition & 0 deletions kas/opt/upstream.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,5 @@ header:

local_conf_header:
upstream-versions: |
BBMASK:remove = "linux-iot2050_.+-upstream\.bb"
PREFERRED_VERSION_linux-iot2050 = "6.x-upstream"