From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/6] arm: mvf600: Add Vybrid MVF600 CPU support
Date: Wed, 15 May 2013 15:20:17 +0200 [thread overview]
Message-ID: <51938B91.5020909@denx.de> (raw)
In-Reply-To: <20130515143957.16e6bebc@lilith>
On 15/05/2013 14:39, Albert ARIBAUD wrote:
> Hi Stefano,
>
Hi Albert, hi Alison,
>> Agree. I think adding armv{4,5,6,7...} is the most clean solution.
>
> This is a clean solution, but do we have the problem? IOW, do we have a
> substantial quantity of code that is common to a given ISA but neither
> generic to ARM (if it were, it would go to arch/arm or arch/arm/lib) nor
> specific to a CPU (if it were, then it should stay under arch/arm/cpu/)?
> If we do then moving this code under an isa tree makes sense; if we
> don't, then arch/arm/cpu/<cpu>/<soc> is enough, and mvf600 just jas to
> move under arch/arm/cpu/ and copy the few ARMv5 snippets it needs from
> another ARMv5-based cpu.
Roght - this is also a clean solution, because we have already arm926
and so on. Alison, please check how you can move your initialization
code as Alber suggested.
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-05-15 13:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:51 [U-Boot] [PATCH v2 0/6] arm: mvf600: Add Freescale Vybrid MVF600 CPU and MVF600TWR board support Alison Wang
2013-05-14 9:51 ` [U-Boot] [PATCH v2 1/6] arm: mvf600: Add Vybrid MVF600 CPU support Alison Wang
2013-05-15 8:13 ` Stefano Babic
2013-05-15 12:09 ` Albert ARIBAUD
2013-05-15 12:24 ` Stefano Babic
2013-05-15 12:39 ` Albert ARIBAUD
2013-05-15 13:20 ` Stefano Babic [this message]
[not found] ` <81BA6E5E0BC2344391CABCEE22D1B6D8322144@039-SN1MPN1-002.039d.mgd.msft.net>
2013-05-15 14:23 ` [U-Boot] 答复: " Stefano Babic
2013-05-16 4:00 ` [U-Boot] " Wang Huan-B18965
2013-05-14 9:51 ` [U-Boot] [PATCH v2 2/6] arm: mvf600: Add IOMUX support for Vybrid MVF600 Alison Wang
2013-05-15 8:16 ` Stefano Babic
2013-05-15 13:53 ` Benoît Thébaudeau
2013-05-14 9:51 ` [U-Boot] [PATCH v2 3/6] arm: mvf600: Add FEC " Alison Wang
2013-05-15 8:15 ` Stefano Babic
2013-05-15 14:19 ` Benoît Thébaudeau
2013-05-14 9:51 ` [U-Boot] [PATCH v2 4/6] arm: mvf600: Add watchdog " Alison Wang
2013-05-14 9:51 ` [U-Boot] [PATCH v2 5/6] arm: mvf600: Add uart " Alison Wang
2013-05-14 9:51 ` [U-Boot] [PATCH v2 6/6] arm: mvf600: Add basic support for Vybrid MVF600TWR board Alison Wang
2013-05-15 4:14 ` Shawn Guo
2013-05-15 8:11 ` Wang Huan-B18965
2013-05-15 9:01 ` Stefano Babic
2013-05-17 15:20 ` Wang Huan-B18965
2013-05-17 16:07 ` Stefano Babic
2013-05-17 16:06 ` Benoît Thébaudeau
2013-05-17 16:57 ` Stefano Babic
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=51938B91.5020909@denx.de \
--to=sbabic@denx.de \
--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