public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] CFI: increase performance
Date: Mon, 26 Jan 2009 11:23:29 +0100	[thread overview]
Message-ID: <200901261123.29440.sr@denx.de> (raw)
In-Reply-To: <497D8E22.5010709@tqs.de>

Hi Jens,

On Monday 26 January 2009, Jens Gehrlein wrote:
> >> The following patches should increase the performance of the CFI driver,
> >> particularly with regard to single word programming mode.
> >>
> >> I tested it on TQM5200S with NOR-Flash Samsung K8P2815UQB, which has no
> >> write buffer. At least no write buffer, that could be programmed using
> >> standard commands.
> >>
> >> Performance increase on this TQM is about factor 2.6 (37 KiB/s -> 95
> >> KiB/s). On the same module with Spansion S29GL128N (with write buffer)
> >> it is about factor 1.2 (455 KiB/s -> 585 KiB/s).
> >>
> >> TQM5200 is a bottom boot module with 2x16 Bit Flash connection. Could
> >> someone test the patches on other HW, particularly top boot, other CPU,
> >> other flash width, please?
> >
> > Tested on AMCC Kilauea (PPC405EX, with 1*16bit Spansion S29GL512N.
>
> The S29GL512N has a write buffer, AFAIK. Thus, U-Boot chooses another
> programming algorithm. Possibly, you only tested patch 2 or did you
> override buffered programming for your test so that patch 1 was
> included?

No, I tested both your patches with the unchanged kilauea config to see if you 
patch broke this (standard) configuration. Nothing bad happened so I applied 
it to the master branch. Others will surely test it as well when its 
available in mainline.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2009-01-26 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 16:25 [U-Boot] [PATCH 0/2] CFI: increase performance Jens Gehrlein
2008-12-16 16:25 ` [U-Boot] [PATCH 1/2] CFI: avoid redundant function call in single word programming mode Jens Gehrlein
2008-12-16 16:25 ` [U-Boot] [PATCH 2/2] CFI: increase performance of function find_sector() Jens Gehrlein
2008-12-16 16:36 ` [U-Boot] [PATCH 0/2] CFI: increase performance Jean-Christophe PLAGNIOL-VILLARD
2008-12-16 16:46   ` Jens Gehrlein
2008-12-16 17:13     ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-17  6:24       ` Jens Gehrlein
2008-12-17  8:22         ` Stefan Roese
2008-12-17  8:56         ` Wolfgang Denk
2008-12-17  9:04         ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-26 10:00 ` Stefan Roese
2009-01-26 10:19   ` Jens Gehrlein
2009-01-26 10:23     ` Stefan Roese [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=200901261123.29440.sr@denx.de \
    --to=sr@denx.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