From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: Generic cache ops skeleton
Date: Sun, 6 Nov 2011 20:09:08 -0500 [thread overview]
Message-ID: <201111062009.09468.vapier@gentoo.org> (raw)
In-Reply-To: <CAPnjgZ1MyXxS4JtdO+o6Zf8cx5WNBLYPE85Hv5Uj8xRr215QPA@mail.gmail.com>
On Sunday 06 November 2011 14:29:47 Simon Glass wrote:
> On this particular patch, I feel it should be more explicit about L1
> cache, which is what I think it deals with. We may want to support L2
> also through a similar API. And a CONFIG option is a good idea.
the point of flushing caches is to make the memory coherent to other devices
(like peripherals). we don't differentiate between the cache levels.
> Finally, even the CP15/cache/MMU code is duplicated in different
> arch/arm/cpu subdirs. Can we unify this a bit?
things should be separated based on core and system levels. the fact that a
particular SoC is say armv4 doesn't mean it should have armv4 specific
cache/mmu handling in its SoC subdir. i think the Linux arm tree is properly
separating things.
-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/20111106/5626c6b9/attachment.pgp
next prev parent reply other threads:[~2011-11-07 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 1:16 [U-Boot] [PATCH] ARM: Generic cache ops skeleton Marek Vasut
2011-11-06 8:36 ` Mike Frysinger
2011-11-06 12:39 ` Marek Vasut
2011-11-06 18:03 ` Mike Frysinger
2011-11-06 18:07 ` Marek Vasut
2011-11-06 19:29 ` Simon Glass
2011-11-07 1:09 ` Mike Frysinger [this message]
2011-11-07 3:10 ` Simon Glass
2011-11-07 12:36 ` Albert ARIBAUD
2011-11-07 1:03 ` Mike Frysinger
2011-11-07 12:21 ` Albert ARIBAUD
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=201111062009.09468.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 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.