From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v6, 4/9] nand: Extend nand_(read|write)_skip_bad with *actual and limit parameters
Date: Thu, 11 Apr 2013 08:07:31 -0400 [thread overview]
Message-ID: <5166A783.6070500@ti.com> (raw)
In-Reply-To: <51665A3C.8090802@compulab.co.il>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/11/2013 02:37 AM, Igor Grinberg wrote:
> On 04/10/13 16:08, Tom Rini wrote:
>> On Thu, Mar 14, 2013 at 05:32:50AM -0000, Tom Rini wrote:
>
>>> We make these two functions take a size_t pointer to how much
>>> space was used on NAND to read or write the buffer (when
>>> reads/writes happen) so that bad blocks can be accounted for.
>>> We also make them take an loff_t limit on how much data can be
>>> read or written. This means that we can now catch the case of
>>> when writing to a partition would exceed the partition size due
>>> to bad blocks. To do this we also need to make check_skip_len
>>> count not just complete blocks used but partial ones as well.
>>> All callers of nand_(read|write)_skip_bad are adjusted to call
>>> these with the most sensible limits available.
>>>
>>> The changes were started by Pantelis and finished by Tom.
>>>
>>> Signed-off-by: Pantelis Antoniou
>>> <panto@antoniou-consulting.com> Signed-off-by: Tom Rini
>>> <trini@ti.com>
>
>> With current master, the following changes are needed to adapt
>> cm_t35 to these call changes:
>
> I guess, you will squash both patches into one, right?
Yes, Marek already squashed this in as part of his pull request that I
need to switch hats and grab.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRZqeDAAoJENk4IS6UOR1WLuIP/RWThgn2nc7xMuMA2soKHQQQ
rSrF/wAAvVNRV3g0g6qQ7VZ/+IkH8C+cjPhpD/VUVbeodx+0b24kiW1Zfxcpblmw
G5cgIMDtAT9prs7upcktjzUwnU/JuZDx0HAfIeA7kWu/hpm2xhe7p3JIID47/sr1
k5Cw+8X+pKYVCt4px68TWhy+gEdKgfvK5rXKVpB4RCLVjTC9hyfmdySo7h6n1M+t
JhmuoHRbDmQsB/qVcauZypirO5AidrRU+baak83XBqgQnwTAPy/i6jDOegHYlaou
9rVzpyOpCUDXNEqDNrU9lOslFpSf0NfpRsAsWsvu35AbcA7yMnRR2kNXeOr2Djur
sUvWpaLpWYpvhT16GGvk8xyoj6eaA3G+LycBFdTcRZPsdeIfs4/lnjRn0Nreq1jQ
CST9w6HyMzBEUhwV4BarPmR4nk1tRwbmX6hfkRbH4iENhG63PYRuX5A18uC8O8uS
wCOZo71a2GvOHFvDSNd2Qkscs3A1QC+6jcm9FBbvydzU4NXo9yIFt+QlsWjenhwv
MWHsFZX5tBP4U2N/mkkRoaJfrpTW137RqPvxwsqB96JObeafdw0SNGGlks6N7X1Z
/83jyM2iEy7icg8e3g+cVTtrJUwAifyZI6wjBGiEV4rxtthLyxNBhm0nerJcXvX+
B8AiXe67JK9wju7t7fRt
=ACw6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-11 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 15:32 [U-Boot] [PATCH v6 0/9] Improve DFU support, enable for am335x_evm Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 1/9] README: Document current DFU CONFIG options Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 2/9] dfu: Support larger than memory transfers Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 3/9] dfu: Change indentation of defines in <dfu.h> Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 4/9] nand: Extend nand_(read|write)_skip_bad with *actual and limit parameters Tom Rini
2013-04-10 13:08 ` [U-Boot] [U-Boot, v6, " Tom Rini
2013-04-11 6:37 ` Igor Grinberg
2013-04-11 12:07 ` Tom Rini [this message]
2013-03-14 15:32 ` [U-Boot] [PATCH v6 5/9] cmd_nand.c: Fix CONFIG_CMD_NAND_YAFFS Tom Rini
2013-03-14 17:32 ` Scott Wood
2013-03-14 15:32 ` [U-Boot] [PATCH v6 6/9] dfu: NAND specific routines for DFU operation Tom Rini
2013-03-14 17:32 ` Scott Wood
2013-03-14 15:32 ` [U-Boot] [PATCH v6 7/9] am335x_evm: Define CONFIG_SYS_CACHELINE_SIZE Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 8/9] am335x_evm: Add CONFIG_CMD_MTDPARTS and relevant defaults Tom Rini
2013-03-14 15:32 ` [U-Boot] [PATCH v6 9/9] am335x_evm: Enable DFU for NAND and MMC, provide example alt_infos Tom Rini
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=5166A783.6070500@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