public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Darius Augulis <augulis.darius@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3 v4] arm: A320: Add support for Faraday A320 evaluation board
Date: Tue, 04 Aug 2009 23:10:49 +0300	[thread overview]
Message-ID: <4A7895C9.8060506@gmail.com> (raw)
In-Reply-To: <20090804194831.GC4638@game.jcrosoft.org>

On 08/04/2009 10:48 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 09:42 Mon 03 Aug     , Darius Augulis wrote:
>> On 07/08/2009 02:30 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> On 15:14 Fri 03 Jul     , Po-Yu Chuang wrote:
>>>> This patch adds support for A320 development board from Faraday. This board
>>>> uses FA526 processor by default and has 512kB and 32MB NOR flash, 64M RAM.
>>>> FA526 is an ARMv4 processor and uses the ARM920T source in this patch.
>>>>
>>> as I understand correctly the faraday and the CS3518 share the same core and
>>> IP so it will be better to have the same dir
>> I don't think so. Both A320 and Gemini share the same FA526 core,
>> but different peripheral. There is no reason to create generic dir
>> for A320 and Gemini. Also, no reason to create cpu/fa526 because
>> fa526 is almost arm920t.
> duplicate code is worse
> as example on at91 we do support multiple soc of the family in the same
> generic dir which allow us to factorize common code and ofcourse split
> soc specific code too

Gemini and A320 are not from the same family. There isn't any common 
code *yet*. They share only the same core.
There are more dirs in cpu/arm920t: "imx", "s3c24x0", etc. Perhaps you 
won't suggest to move all these SoC's into single dir?

A320 and Gemini *maybe* have the same timer IP, but there are few 
'small' problems. First: these processors, made in China, have very poor 
documentation. I must do lot of reverse-engineering work to create 
something working. Second, I don't have any A320 hardware to test 
something. It's very difficult to make most optimal release at the very 
beginning. After we have Gemini in main line, somebody interested in 
A320 should feel free to submit patches to optimize support for SoC's, 
based on FA526 core. Now I can't do this job and I guess it shouldn't be 
reason to reject my patches?

>
> Best Regards,
> J.
>

  reply	other threads:[~2009-08-04 20:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 11:13 [U-Boot] [PATCHv2 3/3] A320: Add support for Faraday A320 evaluation board Po-Yu Chuang
2009-07-02  3:05 ` Po-Yu Chuang
2009-07-02  6:11   ` [U-Boot] [PATCH v3 " Po-Yu Chuang
2009-07-03  7:14     ` [U-Boot] [PATCH 3/3 v4] arm: " Po-Yu Chuang
2009-07-08 11:30       ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-03  6:42         ` Darius Augulis
2009-08-04 19:48           ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-04 20:10             ` Darius Augulis [this message]
2009-08-06  4:45               ` Po-Yu Chuang
2009-08-17 21:49                 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-17 21:45               ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-06  6:13         ` Po-Yu Chuang
2009-08-17 21:52           ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-18  1:38             ` Po-Yu Chuang
2009-08-19 21:36               ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-20  1:54                 ` Po-Yu Chuang
2009-08-20  5:21                   ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-08 22:19     ` [U-Boot] [PATCH v3 3/3] " Wolfgang Denk
2009-07-09  7:36       ` Po-Yu Chuang
2009-07-09  8:03         ` Wolfgang Denk
2009-07-02  8:35 ` [U-Boot] [PATCHv2 " Darius Augulis
2009-07-03  2:02   ` Po-Yu Chuang
2009-07-03  6:38     ` Po-Yu Chuang

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=4A7895C9.8060506@gmail.com \
    --to=augulis.darius@gmail.com \
    --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