linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Luo Yanjun" <linux_arm_kernel@sohu.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: where does kernel config MPC860 memory controller BRx register?
Date: Sun, 29 Sep 2002 10:33:58 +0200	[thread overview]
Message-ID: <20020929083403.001EAFA8F@denx.denx.de> (raw)
In-Reply-To: Your message of "Sun, 29 Sep 2002 15:23:13 +0800." <03db01c26789$12dcb5b0$6100a8c0@udtech.net>


In message <03db01c26789$12dcb5b0$6100a8c0@udtech.net> you wrote:
>
> I want to use CS3 of MPC860 for some devices,
> so I need config BR3 register, I don't know where
> to config it, I have not find BR0's config code.
> Where can I find BR0's config code? If I find that,
> I think I can place my code there.

The initialziation of the memory controller (and things like  testing
and  sizing available memory) have to be done by the firmware on your
board, so look in your firmware sources.

For additional chip selects, you can  of  course  add  the  necessary
BRx/ORx initialization in the init function of the device driver that
will be accessing this hardware.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I think it's a new feature. Don't tell anyone it was an accident. :-)
  -- Larry Wall on s/foo/bar/eieio in <10911@jpl-devvax.JPL.NASA.GOV>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-09-29  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29  7:23 where does kernel config MPC860 memory controller BRx register? Luo Yanjun
2002-09-29  8:33 ` Wolfgang Denk [this message]
2002-09-29 13:17   ` Dr. Craig Hollabaugh

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=20020929083403.001EAFA8F@denx.denx.de \
    --to=wd@denx.de \
    --cc=linux_arm_kernel@sohu.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).