From: Scott Wood <scottwood@freescale.com>
To: Liu Shengzhou-B36685 <B36685@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Liu Shuo-B35362 <B35362@freescale.com>
Subject: Re: Linuxppc-dev Digest, Vol 88, Issue 24
Date: Fri, 9 Dec 2011 12:41:34 -0600 [thread overview]
Message-ID: <4EE2565E.7050700@freescale.com> (raw)
In-Reply-To: <3F453DDFF675A64A89321A1F352810216B0A24@039-SN1MPN1-005.039d.mgd.msft.net>
On 12/09/2011 03:27 AM, Liu Shengzhou-B36685 wrote:
> Before calling nand_scan_ident(), we can still use 2k FCM RAM, not need=
a buffer greater than 2k=A3=AC
> After nand_scan_ident(), if writesize > 2048, then allocate a large bu=
ffer.
> We can do it in fsl_elbc_chip_init_tail()
> if (mtd->writesize > 2048)
> ctrl->buffer =3D kmalloc(mtd->writesize + mtd->oobsize, GFP_KERNE=
L);
As we discussed elsewhere in the thread, the buffer is a controller-wide
resource. It is not associated with any one NAND chip.
-Scott
prev parent reply other threads:[~2011-12-09 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5273.1323013984.15294.linuxppc-dev@lists.ozlabs.org>
2011-12-09 9:27 ` Linuxppc-dev Digest, Vol 88, Issue 24 Liu Shengzhou-B36685
2011-12-09 18:41 ` Scott Wood [this message]
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=4EE2565E.7050700@freescale.com \
--to=scottwood@freescale.com \
--cc=B35362@freescale.com \
--cc=B36685@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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.