public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] CFI: flash_write_cfiword() slow
Date: Fri, 12 Dec 2008 17:34:40 +0100	[thread overview]
Message-ID: <494292A0.3080300@tqs.de> (raw)
In-Reply-To: <20081103201002.CA4A683568B6@gemini.denx.de>

Hi Wolfgang,

Wolfgang Denk schrieb:
> Dear Jens Gehrlein,
> 
> In message <490EDD63.1010403@tqs.de> you wrote:
>> find_sector() loops through the sector table from the last sector to
>> the current sector. And the more sectors the device has, the slower
>> the algorithm becomes. And this process for every sector to be 
>> programmed. And yes, there are still devices around without (standard) 
>> write buffer, e.g. the Samsung K8P2815UQB.
> 
> A classic (and  trivial  to  implement)  approach  is  not  to  start
> searching  at  the  end, but at the last used sector (assuming search
> driection and direction of "growth" are  identical). 

Okay. Because I never have seen, that a flash has been written
backwards, as a prerequisite I have to change the loop from counting 
down to counting up. Any objections?

> This  way,  you
> will  typically  find  the  match either immediately or with a single
> step.
> 
> Maybe you want to give that a try...

I'm currently trying :-) Had some other projects in the meantime.

Kind regards,
Jens

      reply	other threads:[~2008-12-12 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 11:15 [U-Boot] CFI: flash_write_cfiword() slow Jens Gehrlein
2008-11-03 20:10 ` Wolfgang Denk
2008-12-12 16:34   ` Jens Gehrlein [this message]

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=494292A0.3080300@tqs.de \
    --to=sew_s@tqs.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