On Wednesday 25 November 2015 22:29:53 Arnd Bergmann wrote: > On Wednesday 25 November 2015 13:03:10 Tony Lindgren wrote: > > * Arnd Bergmann <arnd@xxxxxxxx> [151125 11:50]: > > > On Wednesday 25 November 2015 10:16:44 Tony Lindgren wrote: > > > > At least I don't have better solutions in mind. > > > > > > I would be happier if we could restrict this as much as possible > > > to the boards that need it, as an opt-in. That way it doesn't > > > become an ABI for people that don't already rely in this > > > information. How about adding a check the code adds the > > > linux,atags property to do it only for a whitelist of board > > > numbers? > > > > Or populate /proc/atags only for the ones that need it from machine > > specific init_early? > > That would also address my main concern about /proc/atags, but still > leave the atags in /proc/device-tree/chosen/linux,atags, and it would > be bad if someone who currently uses /proc/atags changes their code > to use the other file instead of finding a proper solution. > > Arnd 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? -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
