Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry
From: Russell King - ARM Linux <hidden>
Date: 2015-11-29 23:13:28
Also in:
linux-arm-kernel, linux-omap, lkml
From: Russell King - ARM Linux <hidden>
Date: 2015-11-29 23:13:28
Also in:
linux-arm-kernel, linux-omap, lkml
On Sun, Nov 29, 2015 at 07:19:18PM +0100, Pali Rohár wrote:
On Sunday 29 November 2015 19:09:39 Russell King - ARM Linux wrote:quoted
On Sat, Nov 28, 2015 at 12:34:23PM -0500, Nicolas Pitre wrote:quoted
Good. And Arnd likes the idea too. So we might be converging at last which is a good thing.I disagree with the idea that there is convergence. There might be convergence towards an idea, but... Here's a mail extract, from July 7th, from earlier in this very thread: Pali:quoted
Me:quoted
Are the ATAGs at a fixed address on the N900?Yes, in board-rx51.c is: .atag_offset = 0x100 and Nokia Bootloader (proprietary) store them to that address.quoted
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?I already asked question if it is possible to read ATAGs from DT booted kernel. And somebody (do not remember who) wrote to ML, that it is not possible and it can be done in that uncompress code.So you're converging on an idea that has already been rejected. That's not a good thing, IMHO.Or in other case show that such implementation is possible...
Only those with the problem can do that. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.