From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] CFI: increase performance
Date: Wed, 17 Dec 2008 10:04:08 +0100 [thread overview]
Message-ID: <20081217090408.GA26222@game.jcrosoft.org> (raw)
In-Reply-To: <49489B37.9020000@tqs.de>
On 07:24 Wed 17 Dec , Jens Gehrlein wrote:
> Dear Jean-Christophe,
>
> Jean-Christophe PLAGNIOL-VILLARD schrieb:
>> On 17:46 Tue 16 Dec , Jens Gehrlein wrote:
>>> Jean-Christophe PLAGNIOL-VILLARD schrieb:
>>>> On 17:25 Tue 16 Dec , Jens Gehrlein wrote:
>>>>> Hi list,
>>>>>
>>>>> 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?
>>>> Could you try it against the qemu SVN HEAD
>>> ??? Sorry, what is qemu SVN HEAD ???
>>>
>> In qemu you have 2 boards emulated with u-boot support qemu_mips and SX1
>
> Now, I understand, what you meant.
>
>>
>> it'll be nice to test them also
>>
>> please note they are only in the SVN tree of qemu
>
> Because I'm neither familiar with qemu nor with svn I can't do that
> with little effort (installation, familiarization, etc.). Beside that,
> how could a virtual machine simulate the real bus access with it's
> bus timing? If I'm right in this point, only testing on another
> architecture is possible, but no performance test.
It's simple to use I've write a doc about the qemu_mips usage in
doc/README.qemu_mips
and I've resend doc update yesterday to the ML
for the SX1
it's nearly the same as the qemu_mips but the cmdline to start qemu will be
dd of=SX1/flash bs=1k count=32k if=/dev/zero
dd of=SX1/flash bs=1k conv=notrunc if=SX1/u-boot.bin
/opt/qemu/bin/qemu-system-arm -M sx1 -monitor pty -nographic -m 98 -pflash SX1/flash
and the tree to use the SX1 is u-boot-arm/next
with make SX1_stdout_serial_config
Best Regards,
J.
next prev parent reply other threads:[~2008-12-17 9:04 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 [this message]
2009-01-26 10:00 ` Stefan Roese
2009-01-26 10:19 ` Jens Gehrlein
2009-01-26 10:23 ` Stefan Roese
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=20081217090408.GA26222@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--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