From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Fri, 25 Feb 2011 07:34:45 +0100 Subject: [U-Boot] ARM: Incorrect ROM protection range? In-Reply-To: References: <4D660030.409@free.fr> <4D6609C5.3040203@denx.de> <4D6611A7.5050802@free.fr> <20110224093925.90139146940@gemini.denx.de> <4D664801.2000001@free.fr> <4D665969.1@free.fr> <20110224134139.92BD0D5AF8C@gemini.denx.de> <4D6680E4.1070405@free.fr> <20110224183805.C3CB0D708E3@gemini.denx.de> <4D66A7CD.9020309@free.fr> <20110224201748.7225613676F@gemini.denx.de> Message-ID: <4D674D85.40904@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Po-Yu Chuang, Le 25/02/2011 03:41, Po-Yu Chuang a ?crit : > Dear Wolfgang and Albert, > > On Fri, Feb 25, 2011 at 4:17 AM, Wolfgang Denk wrote: >> Dear Albert ARIBAUD, >> >> In message<4D66A7CD.9020309@free.fr> you wrote: >>> >>>> As far as I can tell, arch/powerpc/lib/board.c , >>>> arch/avr32/lib/board.c and examples/standalone/stubs.c actually all >>>> mean __bss_end, as well as all the start.S files, so this seems to be >>>> consistently used at least. >>> >>> I'd come to the same conclusion on my side. However you don't say how >>> you would like the change to be done. Would a single commit for renaming >>> _end into _bss_end and then creating _end after .dynsym be ok for you? >> >> Ah, sorry. >> >> Well, these are two logically separate things: the first is just a >> renamer that should basicly result in the very same images built on >> all systems (which can easily be verified semi-automatically). The >> second step would be adding _end at the end of the used data area (end >> of .dynsym) on ARM only. > > I don't have the environment to build other platforms, so... does any > of you please to provide such patches? I suggest you do the changes for all of U-Boot and test them on your specific board, then submit the patchset and Cc: all architecture custodians, who will run tests on their respective architectures. will give you all info on preparing and sending patches -- remember that's a two-patch set. IMO you don't necessarily need a cover letter as long as each patch has a clear commit message. will give you the list of all custodians; you can pick the architecture ones there. All this, of course, if Wolfgang agrees to this suggestion. Amicalement, -- Albert.