On Wednesday 25 November 2015 22:51:00 Arnd Bergmann wrote: > 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. > Ok. So there is no better solution. With some hacks we can use U-Boot as 3rd stage bootloader. But this is not useful for debugging or developing... Ideal "wrapper" solution would be to compile wrapper and linux zImage and then glue them together to one binary. Something like internal linux uncompress code which translate atags to dt. > 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. > Yes, proprietary/closed applications are problems which we cannot fix (without rewriting them). New applications could use new "proper" interface. But without that interface we cannot do that. -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
