public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: seedshope <bocui107@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] S3C64XX: timer: replace bss variable by gd
Date: Wed, 05 Jan 2011 23:57:32 +0800	[thread overview]
Message-ID: <4D2494EC.7020205@gmail.com> (raw)
In-Reply-To: <AANLkTinF0BxBEzY381V5U=wh5MnKQGF33L0PRvU2KK6M@mail.gmail.com>

On 01/05/2011 03:04 PM, Minkyu Kang wrote:
> Dear seedshope,
>
> On 4 January 2011 23:56, seedshope<bocui107@gmail.com>  wrote:
>> On 01/04/2011 10:46 PM, seedshope wrote:
>>> On 01/04/2011 04:14 PM, Minkyu Kang wrote:
>>>> Use the global data instead of bss variable, replace as follow.
>>>> timer_load_val ->   timer_rate_hz
>>>> timestamp ->   timer_reset_value
>>>> lastdec ->   lastinc
>>> I have already test the patch on s3c6410 . It is work perfect.
>> Before I am not use the patch, When I use the command "nand read",
>> The some information will generate. as following:
>> raise: Signal # 8 caught
>>
>> I also trace the timer.c, But I can't resolve it. As if after the first
>> initial timer,
>> I guess the bss will be clear.
>>
>> Now It is ok after patch this patch.
>>
>> Thanks,
>> seedshope
> Thanks for testing.
>
> Did you test with latest version?
Yes,
> Currently, SMDK6400 can't build because didn't rework for relocation.
> If you are OK, could you please fix it?
Ok, recently, I do the patch for SMD6400 and SMDK6410,
I will send request review in the weekend?

Thank?
seedshope
> I appreciate your help.
>
> Minkyu Kang

  reply	other threads:[~2011-01-05 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04  8:14 [U-Boot] [PATCH] S3C64XX: timer: replace bss variable by gd Minkyu Kang
2011-01-04 14:46 ` seedshope
2011-01-04 14:56   ` seedshope
2011-01-05  7:04     ` Minkyu Kang
2011-01-05 15:57       ` seedshope [this message]
2011-01-06  8:34         ` Minkyu Kang
2011-01-06  8:53           ` Reinhard Meyer
2011-01-09 16:20             ` Wolfgang Denk
2011-01-09 16:14 ` 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=4D2494EC.7020205@gmail.com \
    --to=bocui107@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