From: Thomas Maenner <tmaenner@aehr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uboot newbie - tqm823 and memory conf question
Date: Tue, 18 Feb 2003 18:15:22 -0800 [thread overview]
Message-ID: <3E52E8BA.4000402@aehr.com> (raw)
In-Reply-To: 20030217222028.6E5B5C6E0D@atlas.denx.de
OK, thanks again!
Wolfgang Denk wrote:
> In message <Pine.LNX.4.44.0302171146460.7989-100000@loki.aehr.com> you wrote:
>
>>Thanks!
>
>
> You're welcome.
>
>
>>>So depending if you have CAN on your modules or not you can chose
>>>form CS4...CS7 or from CS3...CS7.
>>>
>>
>>Well then, how does the CPU "know" about that area?
>
>
> Ummm... please read the memory controller section of the MPC8xx
> User's Manual.
Found it! Chapter 15. Digesting it...
---snip---
>
>>- How does the CPU know, that it is SRAM or something else?
>
>
> It doesn't know, and it doesn't need to know. It just goes through
> the memory controller registers to find a BRx/ORx pair that matches
> the physical address, and then it accesses the corresponding CS
> according to the other params in BRx/ORx.
>
> Not that the scanning always starts at BR0/OR0, so if you define
> overlapping memory regions always the first one will win.
>
Good info.
---snip---
>
>>I will search in the source there.
>
>
> What for? Just add it to your Linux device driver's init() code.
>
If the "when" almost doesn't matter, it could be done there.
---snip---
Thanks a lot Wolfgang for your help!
Have a successful show in Nuremberg!
--
Thomas Maenner
prev parent reply other threads:[~2003-02-19 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 1:29 [U-Boot-Users] uboot newbie - tqm823 and memory conf question Thomas Maenner
2003-02-16 17:59 ` Wolfgang Denk
2003-02-17 19:57 ` Tom Maenner
2003-02-17 22:20 ` Wolfgang Denk
2003-02-19 2:15 ` Thomas Maenner [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=3E52E8BA.4000402@aehr.com \
--to=tmaenner@aehr.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