From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Thu, 15 Apr 2010 08:34:37 +0200 Subject: [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC In-Reply-To: References: Message-ID: <4BC6B37D.8050707@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 Prafulla Wadaskar a ?crit : > > >> -----Original Message----- >> From: Albert ARIBAUD [mailto:albert.aribaud at free.fr] >> Sent: Tuesday, April 13, 2010 9:10 PM >> To: Prafulla Wadaskar >> Cc: Wolfgang Denk; U-Boot at lists.denx.de >> Subject: Re: [U-Boot] [PATCH V6 1/3] Initial support for >> Marvell Orion5x SoC >> >> Prafulla Wadaskar a ?crit : >> >>> You are right, the code is SoC specific, but the values to >> be programmed are board specific. >>> if you are interested, >>> Look at cpu/arm926ejs/at91/lowlevel_init.s how it programs SMRDATA. >>> Follow similar arch here too. >>> -Define similar data segment for holding soc_reg_addr and data array >>> -Define macros for SOC register addresses in soc specific >> header file >>> -Define macros for SOC register values in board specific header file >>> This way we can retain lowlevel_init.S in soc specific >> folder, whereas you can pass data through board specific macros. >> >> Ok. >> >>> DRAM init should go in lowlevel_init i.e. asm code, that's >> need of Orion5X >>> Either its location or its architecture need to change to >> address board specific issues. >> >> Agreed. >> >> Now, what about that overall cpu/arch hierarchy change that's been >> started? Is there a branch with the new file hierarchi that I should >> rebase on, or do I keep the current organization in my patch? > > I am waiting for u-boot-arm.git to get rebased so that I can rebase u-boot-mravell.git > Meanwhile this happens, you can post your patches w.r.to u-boot.git. > > Regards.. > Prafulla . . Prafulla, FYI, I will unfortunately be unable to work further on this patch until next wednesday. Amicalement, -- Albert.