From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/12] cmd_sf: Add support for read and write instructions
Date: Tue, 5 Mar 2013 14:59:53 -0500 [thread overview]
Message-ID: <51364EB9.9010907@ti.com> (raw)
In-Reply-To: <CAD6G_RRd5bvVkfLydPjhoyCT-rAOCLpGCpQWaD0B6VPnO2mp=g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/05/2013 01:34 PM, Jagan Teki wrote:
>> Okay.. what I understand is - Currently, all the flash supported
>> commands are provided to user as choice. what what i suppose to
>> implement. He needs to choose the best option based on what the
>> controller and chip connected supports. I guess your idea is to
>> dynamically perform the fastest read/write command based on
>> fastest command supported by controller and chip. I don't know
>> how to support this.
Dang, OK.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIbBAEBAgAGBQJRNk65AAoJENk4IS6UOR1Wg1wP92uphDCgIEaxfykmLfEOWM0Z
XnWUFEkFi5Qe2Q2HpxVl9sjPXLr2/YHSFvWWTuPPWakXDt1OlgTU4erD3Fl2eQfQ
Sz0xiP8MbE8MdL8gQ7mGsZYb7ENLBL8yiGmP4P6Bonm6fKPGZK8LyZMMIfI8mm3R
X7TQKuJsTrZ8lUNZMuh9chumAVyWJzP5vsnCCsJ26yX75eQ2J8jKo4K3nkwMX5GM
SdGzKtRhr8niB93hZ3Dym2l8PylJL6Vvxj2Do4RUOVKL1D7MtiGThRVNlTKEih7h
rc3zRjWZqoMaF6kpUwz7ffZrPEerckoA6JkEE9hx+TJwcs43TXC2Gn4IaNyp38pu
XCQYauQPHPB/5gYSIdoF1o+USUFIvDITFd6YXYT4KIrOVsUslQCMKHayozetWdQ+
3M0x0Xp3z53kn1YUBDKZ4z7juw2FdwTrZAxuXky8ET/zO8AU1gFaQivSk+YxNH4h
yPVFknCg1r1ehpPetin7NxxASUBw57J06xOHITStod6PlD2dLv5U1c4I1QMTFjgj
5pCYdQYpe45+J/D+jnwYhQtVncjIYUHLJxm19DYxYR4dXsn2eIWjsYFl4DnqI0n3
l+teqn6H5tGW5FyRtQ7wHipSdJKZwyKrkX4Gm4U/dA5WTKxiWUGhDytN8OzqRtmw
1vnfvgQdBsub1euZa/s=
=SYEM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-05 19:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 11:13 [U-Boot] [PATCH 00/12] cmd_sf: Add support for read and write instructions Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 01/12] cmd_sf: Add wr_inst argument to 'sf write' command Jagannadha Sutradharudu Teki
2013-01-11 2:11 ` Simon Glass
[not found] ` <CAD6G_RSQXL3RsSuK=4QkRGRNfzuKvU-s7JPrsuB+o5O7GRxJuA@mail.gmail.com>
2013-02-14 14:35 ` Simon Glass
2012-12-31 11:13 ` [U-Boot] [PATCH 02/12] cmd_sf: Add rd_inst argument to 'sf read' command Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 03/12] cmd_sf: Add wr_inst argument to 'sf update' command Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 04/12] cmd_sf: Add rd_inst " Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 05/12] cmd_sf: Define a functions for parsing read and write instructions Jagannadha Sutradharudu Teki
2013-01-11 2:18 ` Simon Glass
2012-12-31 11:13 ` [U-Boot] [PATCH 06/12] cmd_sf: Add QPP(Quad-input Page Program) write instruction support Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 07/12] cmd_sf: Add ASR(Array Slow Read) read " Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 08/12] cmd_sf: Add DOFR(Dual Output Fast " Jagannadha Sutradharudu Teki
2012-12-31 11:13 ` [U-Boot] [PATCH 09/12] cmd_sf: Add QOFR(Quad " Jagannadha Sutradharudu Teki
2013-01-11 2:16 ` [U-Boot] [PATCH 00/12] cmd_sf: Add support for read and write instructions Simon Glass
2013-01-11 2:16 ` Simon Glass
2013-03-02 8:29 ` Jagan Teki
2013-03-04 21:02 ` Jagan Teki
2013-03-04 21:08 ` Tom Rini
2013-03-05 17:00 ` Jagan Teki
2013-03-05 17:08 ` Tom Rini
2013-03-05 17:21 ` Jagan Teki
2013-03-05 17:45 ` Tom Rini
2013-03-05 18:34 ` Jagan Teki
2013-03-05 19:59 ` Tom Rini [this message]
2013-03-08 12:22 ` Michal Simek
2013-03-08 23:55 ` Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 14:33 Langer Thomas
2013-01-11 2:28 ` Simon Glass
2013-01-16 7:47 ` Jagan Teki
2013-01-16 19:51 ` Langer Thomas
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=51364EB9.9010907@ti.com \
--to=trini@ti.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