On 14/05/2013 11:51, Alison Wang wrote:
This patch adds generic codes to support Freescale's Vybrid MVF600 CPU.
It aligns Vybrid MVF600 platform with i.MX platform. As there are
some differences between MVF600 and i.MX platforms, the specific
codes are in the arch/arm/cpu/armv7/mvf600
Hi Stefano,
On Wed, 15 May 2013 10:13:36 +0200, Stefano Babic sba...@denx.de
wrote:
On 14/05/2013 11:51, Alison Wang wrote:
This patch adds generic codes to support Freescale's Vybrid MVF600 CPU.
It aligns Vybrid MVF600 platform with i.MX platform. As there are
some differences between
On 15/05/2013 14:09, Albert ARIBAUD wrote:
Albert, what do you think about ? Should these files be moved away from
armv7 ?
If the SoC is ARMv5, then yes, its arch/arm/cpu files should not go in
armv7 -- and then, we may have to discuss whether, and how, to factorize
ISA-level code. Maybe
Hi Stefano,
On Wed, 15 May 2013 14:24:33 +0200, Stefano Babic sba...@denx.de
wrote:
On 15/05/2013 14:09, Albert ARIBAUD wrote:
Albert, what do you think about ? Should these files be moved away from
armv7 ?
If the SoC is ARMv5, then yes, its arch/arm/cpu files should not go in
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
Hi, Stefano,
On 14/05/2013 11:51, Alison Wang wrote:
This patch adds generic codes to support Freescale's Vybrid MVF600 CPU.
It aligns Vybrid MVF600 platform with i.MX platform. As there are some
differences between MVF600 and i.MX platforms, the specific codes are
in the
6 matches
Mail list logo