Skip to content

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

Description

@cy18

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

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions