From: Alessandro Rubini <rubini@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH 17/19] arm cp15: setup mmu and enable dcache
Date: Fri, 30 Jul 2010 11:31:02 +0200 [thread overview]
Message-ID: <20100730093102.GA26430@morgana.i.gnudd.com> (raw)
In-Reply-To: <4C529758.2020600@ge.com>
Thanks Heiko for picking these up, wanted to reply today offlist.
Nick Thompson:
> As you noted, not all boards define these two symbols. I don't see where you
> have added them in the config.h files.
When I've done this, I couldn't find a name that all boards were
using, so I had to make a choice. I think I just counted the various
names and picked the more common. A board enabling cache must ensure
to have the correct names defined, I see no easy solution.
tornado% grep -rl CONFIG_SYS_SDRAM_BASE include/configs | wc -l
353
tornado% grep -rL CONFIG_SYS_SDRAM_BASE include/configs/ | wc -l
193
For example integratorcp is in this "grep -L", and it has
PHYS_SDRAM_1/PHYS_SDRAM_1_SIZE . This matches less than half of those 193
boards:
tornado% grep -rl PHYS_SDRAM_1_SIZE include/configs/ | wc -l
86
However, re-reading the patch looks like I chose the wrong symbol.
This ought to be fixed, I'll try next week to address the issue.
>> + page_table[i] = i << 20 | (3 << 10) | 0x1e;
>
> These numbers ought to be defines, no?
Yes, it was a lazy RFC. I'll clean up ASAP (monday, hopefully),
unless Heiko does it in his tree. Writeback or writethtough should
be selectable.
> I have previously tested this patch on da830 and it works fine, bar the two
> issues above.
Thanks for testing and your feedback
/alessandro
next prev parent reply other threads:[~2010-07-30 9:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 10:45 [U-Boot] [RFC][PATCH 17/19] arm cp15: setup mmu and enable dcache Heiko Schocher
2010-07-30 9:11 ` Nick Thompson
2010-07-30 9:31 ` Alessandro Rubini [this message]
2010-07-30 9:32 ` Heiko Schocher
2010-07-30 9:57 ` Nick Thompson
2010-07-30 10:13 ` Heiko Schocher
2010-08-03 10:16 ` [U-Boot] [RFC][PATCH v2 " Heiko Schocher
2010-08-05 18:22 ` Ben Gardiner
2010-08-06 5:29 ` Heiko Schocher
2010-08-06 15:41 ` Ben Gardiner
2010-08-06 15:46 ` Wolfgang Denk
2010-08-06 16:14 ` Ben Gardiner
2010-08-06 16:27 ` Reinhard Meyer
2010-08-06 16:32 ` Reinhard Meyer
2010-08-06 16:44 ` Ben Gardiner
2010-08-10 17:45 ` Ben Gardiner
2010-08-11 5:56 ` Heiko Schocher
2010-08-11 13:31 ` Ben Gardiner
2010-08-11 13:53 ` Ben Gardiner
2010-08-11 17:06 ` Heiko Schocher
2010-08-11 19:56 ` Wolfgang Denk
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=20100730093102.GA26430@morgana.i.gnudd.com \
--to=rubini@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox