From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] nand: allow demand initialization
Date: Mon, 11 Oct 2010 17:02:00 -0400 [thread overview]
Message-ID: <201010111702.01571.vapier@gentoo.org> (raw)
In-Reply-To: <20101011202941.GB6394@udp111988uds.am.freescale.net>
On Monday, October 11, 2010 16:29:41 Scott Wood wrote:
> On Sun, Oct 10, 2010 at 06:37:40AM -0400, Mike Frysinger wrote:
> > --- a/common/cmd_nand.c
> > +++ b/common/cmd_nand.c
> > @@ -309,6 +309,8 @@
> >
> > if (argc < 2)
> > goto usage;
> >
> > + nand_init();
> > +
>
> Also do_nandboot().
does it need to be before the mtdparts init stuff, or can it be in
nand_load_image() ?
> > --- a/common/env_nand.c
> > +++ b/common/env_nand.c
> > @@ -359,6 +359,8 @@ void env_relocate_spec(void)
> > return;
> > }
> >
> > + nand_init();
> > +
> >
> > if (readenv(CONFIG_ENV_OFFSET, (u_char *) tmp_env1))
> > puts("No Valid Environment Area found\n");
> >
> > @@ -404,6 +406,8 @@ void env_relocate_spec(void)
> > free(tmp_env1);
> > free(tmp_env2);
> >
> > +#else
> > + nand_init();
> >
> > #endif /* ! ENV_IS_EMBEDDED */
>
> Do we really need to initialize NAND if the environment is embedded, or
> could it be delayed to when the environment is saved?
the reason i picked env_relocate_spec() is because i'd have to push the init
into the read/write/save code paths. and those may be executed multiple times
while running. the expectation is that if you're putting the env into nand,
it's going to get read, so you might as well initialize it.
-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/20101011/9914c5b9/attachment.pgp
next prev parent reply other threads:[~2010-10-11 21:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 10:37 [U-Boot] [PATCH 1/3] nand: allow demand initialization Mike Frysinger
2010-10-10 10:40 ` [U-Boot] [PATCH 2/3] nand: introduce CONFIG_NAND_EARLY_INIT and nand_early_init() Mike Frysinger
2010-10-12 17:33 ` Ben Gardiner
2010-10-12 19:35 ` [U-Boot] [PATCH 2/3 v2] " Mike Frysinger
2010-10-12 20:13 ` Ben Gardiner
2010-10-12 20:19 ` Wolfgang Denk
2010-10-12 20:55 ` Mike Frysinger
2010-10-15 18:59 ` Scott Wood
2010-10-10 10:40 ` [U-Boot] [PATCH 3/3] Blackfin: enable delayed NAND for all relevant boards Mike Frysinger
2010-10-11 20:29 ` [U-Boot] [PATCH 1/3] nand: allow demand initialization Scott Wood
2010-10-11 21:02 ` Mike Frysinger [this message]
2010-10-11 21:27 ` Scott Wood
2010-10-12 19:26 ` Mike Frysinger
2010-10-12 19:35 ` [U-Boot] [PATCH 1/3 v2] nand: introduce CONFIG_NAND_EARLY_INIT and nand_early_init() Mike Frysinger
2010-10-15 18:56 ` [U-Boot] [PATCH 1/3 v2] nand: allow demand initialization Scott Wood
2010-10-15 19:04 ` Mike Frysinger
2010-10-18 20:16 ` Scott Wood
2010-10-19 5:40 ` Mike Frysinger
2010-10-19 15:58 ` 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=201010111702.01571.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