From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] OneNAND: Bad block aware read/write command support
Date: Sat, 8 Nov 2008 06:30:58 +0100 [thread overview]
Message-ID: <200811080630.58638.sr@denx.de> (raw)
In-Reply-To: <20081107212635.GA25714@ld0162-tx32.am.freescale.net>
On Friday 07 November 2008, Scott Wood wrote:
> On Fri, Nov 07, 2008 at 04:01:13PM +0100, Stefan Roese wrote:
> > Update OneNAND command to support bad block awareness.
> > Also change the OneNAND command style to better match the
> > NAND version.
>
> Is there any chance that we could merge this code with cmd_nand.c?
Possibly. I'm not sure yet. I'll try to investigate this next week.
> > +static struct mtd_info *mtd = &onenand_mtd;
>
> Will this cause relocation problems on some architectures?
Yes, you're correct. I missed removing this assignment here. do_onenand() does
it correctly though. I'll fix it in the next patch version.
> Could you have more than one OneNAND on a board?
No, currently only one OneNAND device is supported. We will add this
multi-OneNAND support later.
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
=====================================================================
prev parent reply other threads:[~2008-11-08 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 15:01 [U-Boot] [PATCH v2] OneNAND: Bad block aware read/write command support Stefan Roese
2008-11-07 21:26 ` Scott Wood
2008-11-08 5:30 ` 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=200811080630.58638.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox