Yocto bsp kernel
Review and debug Yocto BSP, MACHINE configuration, kernel provider selection, kernel recipes, kernel config fragments, defconfig, devicetree, U-Boot, FIT images, deploy artifacts, and kernel module installation. Use for machine/BSP/kernel/devicetree/bootloader issues or when kernel artifacts are missing from deploy output.From its SKILL.md
npx -y skills add Higangssh/yocto-agent-skills --skill yocto-bsp-kernelAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Yocto BSP Kernel
Use this skill for machine, BSP, kernel, devicetree, and bootloader work. Verify the selected machine, enabled BSP layers, kernel provider, and deploy artifacts before changing recipes.
Evidence
Ask for or inspect:
MACHINE
conf/machine/*.conf
enabled BSP layers
PREFERRED_PROVIDER_virtual/kernel
kernel recipe and bbappends
KERNEL_DEVICETREE
defconfig or config fragments
U-Boot variables
tmp/deploy/images/<machine>/
Useful commands:
bitbake-layers show-layers
bitbake-layers show-recipes virtual/kernel
bitbake-layers show-appends | rg 'linux|kernel|u-boot'
bitbake -e virtual/kernel | rg '^(MACHINE|PREFERRED_PROVIDER|KERNEL|UBOOT|SRC_URI|S)='
bitbake -c kernel_configme virtual/kernel
bitbake -c kernel_configcheck virtual/kernel
bitbake -c menuconfig virtual/kernel
bitbake -c diffconfig virtual/kernel
bitbake -c savedefconfig virtual/kernel
Review Rules
- Machine config should express hardware policy; distro config should express product policy.
- Select kernel through
PREFERRED_PROVIDER_virtual/kernelin machine or distro policy. - Keep devicetree names aligned with kernel source and machine config.
- Use kernel config fragments or defconfig intentionally; validate with kernel config tasks.
- Verify deploy artifacts before debugging bootloader or flashing.
- Check vendor BSP branch compatibility before modernizing syntax.
References
- Read references/bsp-kernel.md.
- Read references/classes-core.md for kernel and U-Boot classes.
- Read references/migration.md for release compatibility risks.
Output
Answer with:
- selected machine and kernel provider
- BSP/layer compatibility risk
- kernel/devicetree/bootloader metadata issue
- command to validate config or deploy artifacts
- minimal metadata change
What ships with it: 3 files
11.3 KB alongside SKILL.md
references/
- bsp-kernel.md2.5 KB
- classes-core.md4.6 KB
- migration.md4.2 KB
Gives 0 of the 12 instructions most project setup skills give
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- Verify the selected machine and layers
- Check preferred kernel provider
- Validate kernel config with tasks
- Verify deploy artifacts before debugging
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.