All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH - Fix oob data copied into supplied buffer
Date: Mon, 24 Sep 2007 16:41:43 -0700	[thread overview]
Message-ID: <46F84B37.5050305@boundarydevices.com> (raw)
In-Reply-To: <20070922230326.188F224811@gemini.denx.de>

Wolfgang Denk wrote:
> In message <46F3294C.2030206@boundarydevices.com> you wrote:
>>> First chunk fixes a minor spelling error. Then I can't understand why
>>> introduce a new variable. Everything works fine with existing structures 
>>> and
>>> it's been like this for ages, both in Linux kernel and U-Boot.
>>>
>> If you look at the kernel, you'll see that oobavail is set there the way I did it.
>> The other bug doesn't show up unless you have multiple oobfree groups. The new variable
>> is used when reading or writing pages that an initial program loader reads. It's purpose
>> is to correct pages without using a bad block table. I'll submit that code if this is approved.
> 
> kis's comments were legitimate.
> 
> Please add this variable only when adding code that uses it. I will
> always reject patches that attempt to add unused code or variables.
I should have known that, guess I have a lazy streak in me.
> 
> Also, please describe *all* your changes.
Sorry, I didn't realize that you wanted typo fixes, and error messages described.
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 
First segment fixes a typo
Second segment fixes a bug where oob data may be copied incorrectly.
Third segment adds an error message when exiting due to write protect.
Forth segment fixes a bug where oobavail may be set incorrectly.

All segments are independent and may be accepted or rejected as deemed appropriate.
Do they need to be separate patches?
Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>


diff --git a/drivers/nand/nand_base.c b/drivers/nand/nand_base.c
index 151f535..2da1d46 100644
--- a/drivers/nand/nand_base.c
+++ b/drivers/nand/nand_base.c
@@ -931,7 +931,7 @@ static int nand_write_page (struct mtd_info *mtd, struct nand_chip *this, int pa
  			for (i = 0; i < eccbytes; i++, eccidx++)
  				oob_buf[oob_config[eccidx]] = ecc_code[i];
  			/* If the hardware ecc provides syndromes then
-			 * the ecc code must be written immidiately after
+			 * the ecc code must be written immediately after
  			 * the data bytes (words) */
  			if (this->options & NAND_HWECC_SYNDROME)
  				this->write_buf(mtd, ecc_code, eccbytes);
@@ -1299,7 +1299,7 @@ static int nand_read_ecc (struct mtd_info *mtd, loff_t from, size_t len,
  				for (i = 0, j = 0; j < mtd->oobavail; i++) {
  					int from = oobsel->oobfree[i][0];
  					int num = oobsel->oobfree[i][1];
-					memcpy(&oob_buf[oob], &oob_data[from], num);
+					memcpy(&oob_buf[oob+j], &oob_data[from], num);
  					j+= num;
  				}
  				oob += mtd->oobavail;
@@ -1644,8 +1644,10 @@ static int nand_write_ecc (struct mtd_info *mtd, loff_t to, size_t len,
  	this->select_chip(mtd, chipnr);

  	/* Check, if it is write protected */
-	if (nand_check_wp(mtd))
+	if (nand_check_wp(mtd)) {
+		printk (KERN_NOTICE "nand_write_ecc: Device is write protected\n");
  		goto out;
+	}

  	/* if oobsel is NULL, use chip defaults */
  	if (oobsel == NULL)
@@ -2486,12 +2488,9 @@ int nand_scan (struct mtd_info *mtd, int maxchips)

  	/* The number of bytes available for the filesystem to place fs dependend
  	 * oob data */
-	if (this->options & NAND_BUSWIDTH_16) {
-		mtd->oobavail = mtd->oobsize - (this->autooob->eccbytes + 2);
-		if (this->autooob->eccbytes & 0x01)
-			mtd->oobavail--;
-	} else
-		mtd->oobavail = mtd->oobsize - (this->autooob->eccbytes + 1);
+	mtd->oobavail = 0;
+	for (i=0; this->autooob->oobfree[i][1]; i++)
+		mtd->oobavail += this->autooob->oobfree[i][1];

  	/*
  	 * check ECC mode, default to software

  reply	other threads:[~2007-09-24 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  0:24 [U-Boot-Users] PATCH - Fix oob data copied into supplied buffer Troy Kisky
2007-09-21  1:33 ` ksi at koi8.net
2007-09-21  2:15   ` Troy Kisky
2007-09-22 23:03     ` Wolfgang Denk
2007-09-24 23:41       ` Troy Kisky [this message]
2008-04-21  6:46         ` 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=46F84B37.5050305@boundarydevices.com \
    --to=troy.kisky@boundarydevices.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.