All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinhard Arlt <reinhard.arlt@t-online.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] cfi_flash init got real slow
Date: Sun, 19 Mar 2006 22:14:47 +0100	[thread overview]
Message-ID: <441DC9C7.5070301@t-online.de> (raw)

Hello,

i have changed the flash support in u-boot for the CPCI750 from a local 
flash.c to the usage of cfi_flash.c a month ago.

With the u-boot version from git from yesterday, flash init take about 
20 seconds (it tooks no noticeable time with the last version).

This is not acceptable.

It is also not acceptable to disable flash protection.

The problem is the code, that "invents" this "auto" flash unprotection 
in the flash_init routine. Please consider, that there are systems out 
with the env in eeprom, and, by the way, reading the "unlock" variable 
with the loop for each devive two times is not too good coding style.

Please be carefull with changes, that have an impact to other systems.

Kind regards

Reinhard

             reply	other threads:[~2006-03-19 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 21:14 Reinhard Arlt [this message]
2006-03-19 22:05 ` [U-Boot-Users] cfi_flash init got real slow Wolfgang Denk
2006-03-20 10:07   ` Reinhard Arlt
2006-03-20 20:16     ` 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=441DC9C7.5070301@t-online.de \
    --to=reinhard.arlt@t-online.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.