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

When a same bootarg exists in both dtb and bootargs env, the one in dtb is selected. #73

Open
cy18 opened this issue Jan 23, 2022 · 0 comments

Comments

@cy18
Copy link

cy18 commented Jan 23, 2022

For example,

## U-Boot bootargs: earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 console=ttyFIQ0 rw root=/dev/mmcblk1p8 rootfstype=ext4 rootwait coherent_pool=1m init=/sbin/init
## Kernel bootargs: earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 console=ttyFIQ0 rw root=PARTUUID=614e0000-0000 rootfstype=ext4 rootwait coherent_pool=1m
## Merged bootargs: earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 console=ttyFIQ0 rw root=PARTUUID=614e0000-0000 rootfstype=ext4 rootwait coherent_pool=1m init=/sbin/init

The resulting rootfs is the one defined in dtb "root=PARTUUID=614e0000-0000", instead of the one given in uboot env. This behavior makes it impossible to change arguments already defined in kernel DTB. It also does not conform to the description in the document “Rockchip_Developer_Guid_Uboot_Nextdev_CN" as below:

image

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

No branches or pull requests

1 participant