Summary: meta-ti created beagleboard .config is causing the Linux kernel to 
fail during boot

Question:  How do I connect with the people that can correct the MACHINE equal 
beagleboard .config file?


Information that may explain why I ask the question above:

Based on Denys' recent reply, I confirmed a mainline Linux kernel v4.19.73 
build runs on the Beagleboard-xM (when compiled with an appropriate kernel 
.config).

After identifying an appropriate .config for the mainline Linux kernel 
v4.19.73, I used that .config for defconfig in a poky 2.7.1 and meta-ti 
(44a979c5265) build. The meta-ti build using my defconfig override runs on the 
Beagleboard-xM.

When not overridden, the defconfig used for MACHINE equal beagleboard is the 
one line "use-tisdk-config=ti_sdk_omap2_release" file. During do_configure(), 
the one line defconfig causes execution of the lines below (with config equal 
to "ti_sdk_omap2_release").
/short/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-ti-staging/4.19.59+gitAUTOINC+50ceb3c6e7-r127a/git/ti_config_fragments/defconfig_builder.sh
 -w 
/short/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-ti-staging/4.19.59+gitAUTOINC+50ceb3c6e7-r127a/git
 -t $config
oe_runmake -C 
/short/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-ti-staging/4.19.59+gitAUTOINC+50ceb3c6e7-r127a/git
 
O=/short/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-ti-staging/4.19.59+gitAUTOINC+50ceb3c6e7-r127a/build
 "$config"_defconfig

After my quick scan of the defconfig_builder.sh, I found a 
"ti_sdk_omap2_release_defconfig" file I believe to be based on 
arch/arm/configs/multi_v7_defconfig (based on defconfig_map.txt redirection via 
"defconfig: multi_v7_defconfig").


  

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient and may contain material that is proprietary, 
confidential, privileged or otherwise legally protected or restricted under 
applicable government laws. Any review, disclosure, distributing or other use 
without expressed permission of the sender is strictly prohibited. If you are 
not the intended recipient, please contact the sender and delete all copies 
without reading, printing, or saving.


-- 
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

Reply via email to