* Pali Rohár <pali.rohar@xxxxxxxxx> [151127 00:39]: > On Thursday 26 November 2015 12:39:30 Tony Lindgren wrote: > > Just to explore options.. How about make a minimal device driver that > > just loads the atags blob from /lib/firmware and then shows it in > > /proc/atags? Of course some checking on the atags should be done by > > the driver.. > > And who can dynamically create that blob file in /lib/firmware? If > kernel does not export those atags (somehow) from bootloader, then > userspace is not able to create that blob... cyclic problem. > > So no, problem is that bootloader provides via custom atags dynamic > information like: boot reason (how was device started, by rtc alarm? by > reboot? by usb charger? by power button?), boot mode (should be enter > into firmware update mode?, is this normal boot mode?), ... and those > information are needed for some proprietary software (e.g. firmware > upgrade/flash) but also by any other open source applications (based on > usb charger we enter different runlevel -- for just only charging > device). OK if the ATAGs are not static then naturally we can't create the blobs then. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
