Hi Ard. > I take it this is working around buggy firmware that passes both a DT > and ACPI tables, and the DT in question is broken? > > If so, this should be fixed in the firmware. The EFI stub does not > reason at all about ACPI boot vs DT boot, and I would prefer to keep > it that way, especially because this code is shared with other > architectures. For instance, the meaning of acpi= could differ between > architectures, or they may not implement ACPI in the first place. What I concern is that It doesntt necessary to check DT otherwise if the FDT variable in variable storage's contents is corrupted, it would complain while it check in early_init_dt_scan() thou the dt isn't used in boot process. also, although acpi= could differ from architecture, the force option's menaing seems the same over architecture (ignore DT boot with ACPI tables). So I think the check the "acpi=force" option to prevent loading DT seems good. Am I missing? Thanks
