From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Thu, 13 Sep 2012 14:52:19 +0200 Subject: [U-Boot] [PATCH 3/4 v2] arm: Support new Xilinx Zynq platform In-Reply-To: <201209131432.21613.marex@denx.de> References: <1345098630-27902-1-git-send-email-monstr@monstr.eu> <201209131231.08843.marex@denx.de> <5051C26F.8030602@monstr.eu> <201209131432.21613.marex@denx.de> Message-ID: <5051D703.7070804@monstr.eu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 09/13/2012 02:32 PM, Marek Vasut wrote: > Dear Michal Simek, > >> On 09/13/2012 12:31 PM, Marek Vasut wrote: >>> Dear Michal Simek, >>> >>>> On 09/13/2012 11:31 AM, Marek Vasut wrote: >>>>> Dear Michal Simek, >>>>> >>>>> [...] >>>>> >>>>>> +#include >>>>>> +#include >>>>>> + >>>>>> +ENTRY(lowlevel_init) >>>>>> + mov pc, lr >>>>>> +ENDPROC(lowlevel_init) >>>>> >>>>> inline void lowlevel_init(void) {} works as well and you don't need the >>>>> assembly file. >>>>> >>>> :-) yes. The reason why I have done it in this way that we have some asm >>>> :code >>>> >>>> which will go to this area. That's why I have kept it in asm instead of >>>> C. >>> >>> What code? Will the code go into lowlevel_init() ? >> >> For example SLCR locking if is not locked from the first stage bootloader. >> Also if necessary OCM and DDR remap, FPGA reset can be also there >> based on configuration. > > Can it not be in C code ? Probably can be in C code. I have no problem to move it to C. Cheers, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian