public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: XIP aware file system
Date: Tue, 15 Feb 2005 17:50:48 +0100	[thread overview]
Message-ID: <20050215165048.GE831@synertronixx3> (raw)
In-Reply-To: <Pine.LNX.4.61.0502151055150.27338@localhost.localdomain>

You got it!

Finally I considered the OSCR running at 3.6MHz and did

#define xip_elapsed_since(x)    (signed)((IMX_TCN(IMX_TIM1_BASE) - (x)) * 28)

i.e. 112/4. And it runs and does xip and I can write to flash.
Im not believing what I see...

Am 2005-02-15 11:38 -0500 schrieb Nicolas Pitre:

> I'm not sure if it is strictly necessary to use ICMR.  According to the 
> manual quoted above masked interrupts only update ICPR and not ICIP.  If 
> so the & with ICMR is redundent.

I think it is redundant but I don't know exactly the meaning of
ICMR|ICCR.

> If your time base runs at 32kHz you need:
> 
> #define xip_elapsed_since(x) (signed)((IMX_TCN(IMX_TIM1_BASE) - (x)) * 31)

Right. As said, I assumed OSCR runs 3.6MHz and came to * 28, but I
should do 112/3.6.
Thanks for your nice explanation.

> Where do you see that?

ARGH! It was mine! 

> Please study carefully xip_udelay() and try to understand _when_ it is 

Im trying hard :)

> Look at your xip_elasped_since() implementation.

All right, I did while you calculated the values for me :)

Thanks for your help, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2005-02-15 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 15:48 XIP aware file system Konstantin Kletschke
2005-02-15 16:12 ` Konstantin Kletschke
2005-02-15 16:38 ` Nicolas Pitre
2005-02-15 16:50   ` Konstantin Kletschke [this message]
2005-02-15 17:12     ` Nicolas Pitre
2005-02-15 18:08       ` Konstantin Kletschke
2005-02-15 18:25         ` Nicolas Pitre
2005-02-15 18:51     ` Konstantin Kletschke
2005-02-15 17:36   ` David Woodhouse
2005-02-15 18:04     ` Nicolas Pitre

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=20050215165048.GE831@synertronixx3 \
    --to=lists@ku-gbr.de \
    --cc=linux-mtd@lists.infradead.org \
    /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