public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] mtd/nand : Add function board_nand_init_tail() for some special NAND controllers
Date: Wed, 23 Nov 2011 14:31:17 -0500	[thread overview]
Message-ID: <201111231431.18629.vapier@gentoo.org> (raw)
In-Reply-To: <4ECC0FF8.7080801@freescale.com>

On Tuesday 22 November 2011 16:11:20 Scott Wood wrote:
> On 11/22/2011 03:03 PM, Mike Frysinger wrote:
> > On Tuesday 22 November 2011 03:54:14 Shengzhou Liu wrote:
> >> In some NAND controllers there is a size limitation of RAM buffer(2K
> >> bytes). To support large-page NAND chips with greater than 2K pagesize,
> >> we need a large buffer, but we don't know pagesize before calling
> >> nand_scan_ident(), for more flexible and to identify different cases of
> >> large-page greater than 2K bytes, we have a board_nand_init_tail()
> >> between nand_scan_ident() and nand_scan_tail().
> > 
> > iirc, newer Linux mtd tree handles this better by breaking up the code
> > paths so individual drivers can call things in the right order.  perhaps
> > we should update our mtd stack so we can do that ?
> 
> We already have that on the mtd side -- this patch uses it.  The issue
> is the U-Boot glue code calling nand_scan() rather than letting the
> drivers control the process.
> 
> This patch is less intrusive than changing all the drivers, but if
> someone wants to actually do that (without breaking anything), or more
> realistically set up a transition mechanism, that'd be great. :-)

ok, so it is a short coming in the current u-boot mtd framework that we should 
look at migrating away from.  no, i'm not volunteering to take this on :).
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111123/dafe6222/attachment.pgp>

      reply	other threads:[~2011-11-23 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  8:54 [U-Boot] [PATCH 1/3] mtd/nand : Add function board_nand_init_tail() for some special NAND controllers Shengzhou Liu
2011-11-22  8:54 ` [U-Boot] [PATCH 2/3] mtd/nand : workaround for Freescale FCM to support 4k pagesize Nand chip Shengzhou Liu
2011-11-22  8:54   ` [U-Boot] [PATCH 3/3] mtd/nand: Add NAND chip ID to support Micron 4K pagesize NAND chip Shengzhou Liu
2011-11-22 23:58   ` [U-Boot] [PATCH 2/3] mtd/nand : workaround for Freescale FCM to support 4k pagesize Nand chip Scott Wood
2011-11-22 21:03 ` [U-Boot] [PATCH 1/3] mtd/nand : Add function board_nand_init_tail() for some special NAND controllers Mike Frysinger
2011-11-22 21:11   ` Scott Wood
2011-11-23 19:31     ` Mike Frysinger [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=201111231431.18629.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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