From: James Chargin <jimccrown@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Documentation review request: Cache management and stand alone application
Date: Fri, 23 Aug 2013 07:19:37 -0700 [thread overview]
Message-ID: <52176F79.5060103@gmail.com> (raw)
Based on some recent mailing list discussions about cache management for
stand alone applications, and on my own recent experience, I've made two
small additions to the documentation wiki. Since I can't find any
procedure for having this work reviewed, I'm asking for a review here.
Please see the new sections, _5.12.3. Processor cache considerations_
and _5.12.4 Running on core other than core 0_, at
http://www.denx.de/wiki/view/DULG/UBootStandalone#Section_5.12.3. and
http://www.denx.de/wiki/view/DULG/UBootStandalone#Section_5.12.4.,
respectively.
If there is a standard review process for the wiki that I have not seen,
I'd appreciate a pointer. I'll be happy to retroactively make any
adjustments needed.
My additions reflect my concerns with the MPC85xx (P1022) which I am
working with. I would not be surprised in the least if the discussion I
have provided apply poorly for other architectures.
Thank you and best regards,
Jim
--
Jim Chargin
AJA Video Systems jimc at aja.com
(530) 271-3334 http://www.aja.com
reply other threads:[~2013-08-23 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52176F79.5060103@gmail.com \
--to=jimccrown@gmail.com \
--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.