* Pali Rohár <pali.rohar@xxxxxxxxx> [151126 01:08]: > On Wednesday 25 November 2015 20:19:21 Frank Rowand wrote: > > > Or populate /proc/atags only for the ones that need it from machine > > > specific init_early? > > > > This is circling back to the first comment from Russell King where > > he suggested a legacy file for the N900 which calls save_atags(): > > > > Are the ATAGs at a fixed address on the N900? Can that be handled in > > some kind of legacy file for the N900 which calls save_atags() on it, so > > we don't end up introducing yet more stuff that we have to maintain into > > the distant future? If not, what about copying a known working atag > > structure into a legacy file for the N900? > > > > It seems to me that patches 1, 2, 4, and 5 could be replaced by this > > approach. > > Hi Frank, in this case I will ask my question again: It is possible to > read atags from that legacy file. And if yes how? I was not thinking > about this approach because somebody in past wrote that this is not > possible... 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.. That would work as long as the kernel no longer needs it. Regards, Tony -- 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
