On Mon, Jun 29, 2015 at 07:00:22AM -0700, Josh Triplett wrote:
> Definitely not FW_BUG. The field is reserved *now*; it would be
> legitimate for a new version of the BGRT spec to define one of those
> bits for something else.
Which would mean that booting old kernels on new FW which defines those
reserved bits would cause that warning to fire erroneously.
So then we probably don't need it at all or we need to check implemented
BGRT version of the FW running to know which bits are defined by the
spec and which are reserved...
Also, does the spec really say that reserved bits must be zero? Or it
doesn't specify their value?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
