All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] OneNAND: Bad block aware read/write command support
Date: Wed, 12 Nov 2008 20:20:06 +0100	[thread overview]
Message-ID: <200811122020.06339.sr@denx.de> (raw)
In-Reply-To: <20081112173942.GA19378@ld0162-tx32.am.freescale.net>

On Wednesday 12 November 2008, Scott Wood wrote:
> On Wed, Nov 12, 2008 at 01:47:24PM +0100, Stefan Roese wrote:
> > Update OneNAND command to support bad block awareness.
> > Also change the OneNAND command style to better match the
> > NAND version.
> >
> > Signed-off-by: Stefan Roese <sr@denx.de>
> > Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
> > ---
> > Scott, I looked at merging this code with the NAND command code, but the
> > differences are too big for my taste.
>
> Understood for now, though long-term we should try to eliminate the
> differences that aren't rooted in hardware, and abstract into driver code
> the ones that are.

Ack.

> Applied to u-boot-nand-flash/next (despite a few long lines).

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2008-11-12 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 12:47 [U-Boot] [PATCH v3] OneNAND: Bad block aware read/write command support Stefan Roese
2008-11-12 17:39 ` Scott Wood
2008-11-12 19:20   ` Stefan Roese [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=200811122020.06339.sr@denx.de \
    --to=sr@denx.de \
    --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.