Re: ACPI vs DT at runtime

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Tue, Nov 19, 2013 at 02:38:40PM +0000, Mark Rutland wrote:
> On Tue, Nov 19, 2013 at 01:56:26PM +0000, Stefano Stabellini wrote:

> > I would not go as far as requiring that only one is available.
> > Certainly I would mandate that either of them are independently complete
> > and sufficient to describe the platform.
> 
> At that point we need to choose one to prefer. This will be a completely
> arbitrary choice, but as in the EFI case we would expect a DTB stub (for
> passing some options in /chosen), preferring the DT if it's more than a
> stub would make sense to me.
> 
> The key point is that the kernel will rely solely on one of them to
> provide hardware description.

Given that the likley path is to have a static DT override a broken ACPI
table on a system, giving preference to DT seems like the logical choice
at this time.

There's also presendence from x86 to allow bootargs such as "noacpi" to disable
one or the other, but hopefully we can avoid that as long as possible.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux