From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC
Date: Tue, 13 Apr 2010 17:40:10 +0200 [thread overview]
Message-ID: <4BC4905A.7050405@free.fr> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1878702925@SC-VEXCH4.marvell.com>
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?
> Regards..
> Prafulla . .
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-04-13 15:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 8:29 [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC Albert Aribaud
2010-04-09 8:29 ` [U-Boot] [PATCH V6 2/3] Add Orion5x support to 16550 device driver Albert Aribaud
2010-04-09 8:29 ` [U-Boot] [PATCH V6 3/3] Add support for the LaCie ED Mini V2 board Albert Aribaud
2010-04-09 9:37 ` Prafulla Wadaskar
2010-04-12 11:13 ` Prafulla Wadaskar
2010-04-10 21:16 ` [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC Wolfgang Denk
2010-04-11 7:35 ` Albert ARIBAUD
2010-04-11 7:41 ` Albert ARIBAUD
2010-04-12 8:32 ` Prafulla Wadaskar
2010-04-12 10:42 ` Albert ARIBAUD
2010-04-12 10:45 ` Wolfgang Denk
2010-04-12 11:09 ` Prafulla Wadaskar
2010-04-12 12:00 ` Albert ARIBAUD
2010-04-12 12:41 ` Wolfgang Denk
2010-04-12 15:02 ` Albert ARIBAUD
2010-04-13 10:33 ` Prafulla Wadaskar
2010-04-13 11:08 ` Albert ARIBAUD
2010-04-13 13:37 ` Prafulla Wadaskar
2010-04-13 15:40 ` Albert ARIBAUD [this message]
2010-04-14 7:42 ` Prafulla Wadaskar
2010-04-15 6:34 ` Albert ARIBAUD
2010-04-29 9:57 ` Prafulla Wadaskar
2010-04-11 11:56 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC4905A.7050405@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox