public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 05/10] ARM Add New Board GEC2410
Date: Sat, 31 Oct 2009 21:05:30 +0100	[thread overview]
Message-ID: <20091031200530.390EAC88C7@gemini.denx.de> (raw)
In-Reply-To: <b9e3f7a01cba3bcd76dc29d8bad2369dc8ac0349.1256898456.git.zetalabs@gmail.com>

Dear "Hui.Tang",

In message <b9e3f7a01cba3bcd76dc29d8bad2369dc8ac0349.1256898456.git.zetalabs@gmail.com> you wrote:
> Add GEC2410 Clock Setting.
> 
> Signed-off-by: Hui.Tang <zetalabs@gmail.com>
> ---
>  cpu/arm920t/s3c24x0/timer.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/cpu/arm920t/s3c24x0/timer.c b/cpu/arm920t/s3c24x0/timer.c
> index 20cedd4..d4787b9 100644
> --- a/cpu/arm920t/s3c24x0/timer.c
> +++ b/cpu/arm920t/s3c24x0/timer.c
> @@ -188,6 +188,7 @@ ulong get_tbclk(void)
>  	tbclk = timer_load_val * 100;
>  #elif defined(CONFIG_SBC2410X) || \
>        defined(CONFIG_SMDK2410) || \
> +      defined(CONFIG_GEC2410) || \
>        defined(CONFIG_VCMA9)
>  	tbclk = CONFIG_SYS_HZ;

Instead of adding more and more board names here, we should define a
feature dependency instead - I understand this is s3c2400 versus
x3c2410 code, right? So why don't we use this instead? In any case,
such lists should always be kept sorted.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The biggest difference between time and space is that you can't reuse
time.                                                 - Merrick Furst

  parent reply	other threads:[~2009-10-31 20:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 10:39 [U-Boot] [PATCH 01/10] ARM Add New Board GEC2410 Hui.Tang
2009-10-30 10:39 ` [U-Boot] [PATCH 02/10] " Hui.Tang
2009-10-30 10:39   ` [U-Boot] [PATCH 03/10] " Hui.Tang
2009-10-30 10:39     ` [U-Boot] [PATCH 04/10] " Hui.Tang
2009-10-30 10:39       ` [U-Boot] [PATCH 05/10] " Hui.Tang
2009-10-30 10:39         ` [U-Boot] [PATCH 06/10] " Hui.Tang
2009-10-30 10:39           ` [U-Boot] [PATCH 07/10] " Hui.Tang
2009-10-30 10:39             ` [U-Boot] [PATCH 08/10] " Hui.Tang
2009-10-30 10:39               ` [U-Boot] [PATCH 09/10] " Hui.Tang
2009-10-30 10:39                 ` [U-Boot] [PATCH 10/10] " Hui.Tang
2009-10-31 20:16                   ` Wolfgang Denk
2009-10-31 20:15                 ` [U-Boot] [PATCH 09/10] " Wolfgang Denk
2009-10-31 20:15               ` [U-Boot] [PATCH 08/10] " Wolfgang Denk
2009-11-03 12:14                 ` Hui Tang
2009-11-03 13:28                   ` Wolfgang Denk
2009-10-30 12:56             ` [U-Boot] [PATCH 07/10] " Ben Warren
2009-10-31 20:13           ` [U-Boot] [PATCH 06/10] " Wolfgang Denk
2009-10-31 20:05         ` Wolfgang Denk [this message]
2009-10-31 20:01       ` [U-Boot] [PATCH 04/10] " Wolfgang Denk
2009-11-03  4:08         ` Hui Tang
2009-11-03 10:27           ` Minkyu Kang
2009-11-03 11:58             ` Hui Tang
2009-11-03 13:16             ` Wolfgang Denk
2009-11-03 13:07           ` Wolfgang Denk
2009-10-30 12:58     ` [U-Boot] [PATCH 03/10] " Ben Warren
2009-10-31 19:58     ` Wolfgang Denk
2009-10-31 19:59     ` Wolfgang Denk
2009-10-31 19:52 ` [U-Boot] [PATCH 01/10] " 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=20091031200530.390EAC88C7@gemini.denx.de \
    --to=wd@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