public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH for drivers/cfi_flash.c
Date: Fri, 06 May 2005 03:20:34 -0500	[thread overview]
Message-ID: <427B28D2.9010704@orkun.us> (raw)

This patch is prepared against current CVS:

* Patch by Tolunay Orkun, 06 May 2005:
   Fixes for drivers/cfi_flash.c:
   - Fix wrong timeout value usage in flash_status_check()
   - Fix incorrect if condition in flash_full_status_check()
   - Remove clearing flash status at the end of flash_write_cfibuffer()
     which set Intel 28F640J3 flash back to command mode on CSB472

~~~~

Verbose description of fixes:

Fix #1: flash_status_check() receives the timeout as a parameter. 
Existing code is using erase_blk_tout which is too conservative for
some operations but insufficient for others (like buffered writes)

Fix #2: flash_full_status_check() does not combine conditions properly 
in the if statement.

This fix was suggested by "Peter Pearse" <Peter.Pearse@arm.com> but a 
patch was never submitted as far as I can tell. Refer to:

http://sourceforge.net/mailarchive/message.php?msg_id=10546157

Fix #3: flash_write_cfibuffer() would leave the flash in command mode. I 
had mentioned this problem on the list a couple of times but never had 
time to investigate until now.

* Intel 28F640J3 flash on CSB472 board reverts to command mode if the 
removed line is present. Thus immediately after cp to flash operation, 
imls, boot etc would not work properly. md to flash displays 0x0080 
(repeated) which is the value of status register of the flash.

* When this line is present and executed the flash is already in Array 
Read mode (flash_full_status_check issues a reset command in the end). 
So clearing the status is unnecessary at best.

Best regards,
Tolunay Orkun

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cfi_flash_bufwrite_fix.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050506/0492edd7/attachment.txt 

             reply	other threads:[~2005-05-06  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  8:20 Tolunay Orkun [this message]
2005-05-28 22:15 ` [U-Boot-Users] PATCH for drivers/cfi_flash.c Andrew Dyer
2005-05-30  8:23   ` Wolfgang Denk
2005-05-31 16:14     ` Tolunay Orkun
2005-05-31 20:06       ` Wolfgang Denk
2005-05-31 16:02   ` Tolunay Orkun
2005-05-31 20:05     ` Wolfgang Denk
2005-05-31 20:54       ` Tolunay Orkun
2005-06-01  7:24         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01  7:03 Peter Pearse
2005-07-03  0:50 Tolunay Orkun
2006-02-28 16:33 ` 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=427B28D2.9010704@orkun.us \
    --to=listmember@orkun.us \
    --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