On Wednesday 25 November 2015 22:44:28 Pali Rohár wrote: > > Arnd, my question about proper solution reminds... Proprietary > bootloader which cannot be replaced (e.g. it is signed or do unknown > magic) provides information to booted kernel via custom specific ATAGs > fields. How userspace could properly read those custom information from > bootloader? The typical solution for nonstandard bootloaders is to have a boot wrapper like the one from https://github.com/zonque/pxa-impedance-matcher that translates whatever information we have at the bootloader level into DT properties. As I understand, the reason we are not doing that here is that we also have proprietary user space that we can't fix to look in a different place, i.e. the interface is between the bootloader and some user binary, not bootloader to kernel. Arnd -- 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
