On Thu, Dec 10, 2015 at 1:20 AM, Tomas Winkler <tomasw@xxxxxxxxx> wrote: > Intel uses EFI variables for that on some AOS platforms. There is a > need for persistent storage abstraction and generalize the reboot > reasons strings. Yea. I've been told there isn't any sort of standardized method for EFI here. But I have seen a few different implementations floating around. One of the machines I want to support with this driver is actually using a UEFI bootloader, but we don't have separate storage to use to communicate back via the UEFI methods, so the ram based approach looks like the best solution. > Second, I wonder why this is submitted under drivers/misc when it > doesn't bind the misc API. Heh. Apologies. Its more of a "where do I put this?", misc rather then "this should be part of the established misc infrastructure!" Suggestions for alternative locations? thanks -john -- 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
