From: Pete Murray <pmurray@dawning.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND 16 bit buswidth issue
Date: Thu, 19 Aug 2010 09:07:48 -0400 [thread overview]
Message-ID: <4C6D2CA4.2070708@dawning.com> (raw)
I am running U-boot 2009.08 on a sequoia based custom board. The board
has a Micron 29F2G16AAD nand chip. This chip is a large page device
with a 16 bit buswidth. I have an issue in nand_base.c in the
nand_get_flash_type function where the check for buswidth fails, causing
the print out -
printk(KERN_WARNING "NAND bus width %d instead %d bit\n",
(chip->options & NAND_BUSWIDTH_16) ? 16 : 8,
busw ? 16 : 8);
The busw is read from the nand chip and is correct, but the
chip->options is incorrect. I don't see where this gets set to the
options shown in nand_ids.c. I see that here:
/* Lookup the flash id */
for (i = 0; nand_flash_ids[i].name != NULL; i++) {
if (dev_id == nand_flash_ids[i].id) {
type = &nand_flash_ids[i];
break;
}
}
type gets the correct values from nand_ids, should the value of
type->options be assigned to chip->options? Or am I missing something
and need to set chip->options somewhere in my board specific files?
next reply other threads:[~2010-08-19 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 13:07 Pete Murray [this message]
2010-08-19 19:27 ` [U-Boot] NAND 16 bit buswidth issue Scott Wood
2010-08-19 20:22 ` Pete Murray
2010-08-19 20:46 ` Scott Wood
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=4C6D2CA4.2070708@dawning.com \
--to=pmurray@dawning.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.