linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Clemens Koller" <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Complete ccsr map for mpc8540 available?
Date: Tue, 31 May 2005 10:17:25 -0500	[thread overview]
Message-ID: <5be2f8f42a2cfaea381a88c5de9cbb4e@freescale.com> (raw)
In-Reply-To: <429B2B54.1060504@anagramm.de>


On May 30, 2005, at 10:03 AM, Clemens Koller wrote:

> Hi, There!
>
> I want to access the local bus controller (LBC) registers
> of the mpc8540 from within a module.
> Therefore I want to use similar structures as for the 8560's cpm2_immr
> or the 8xx. However, I was not able to find a complete ccsr map for the
> mpc8540 in the 2.6.11.x kernels. (immap_85xx.h, 8xx_immr.h, ...)
>
> Can someone point me to get the memc_brx / orx and friends for mpc8540?
> (the complete CCSR map.) Or some code to recycle?
> Or do I need to patch more into immap_85xx.h on my own? I just want to
> avoid to do duplicate work.
>
> Or is it better to extend the fsl_ocp or the platform device 
> structures?

What do you plan on doing with the local bus controller in the kernel?  
If this is only configuration of the controller for a given chip select 
that I would suggest doing something similar to how we handle PCI.  You 
can probably find a description of the localbus registers in the u-boot 
source tree.

Is this a change you want to get back into the mainline kernel tree?

- kumar

  reply	other threads:[~2005-05-31 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 15:03 Complete ccsr map for mpc8540 available? Clemens Koller
2005-05-31 15:17 ` Kumar Gala [this message]
2005-05-31 16:03   ` Clemens Koller
2005-05-31 16:08     ` Kumar Gala
2005-05-31 16:17       ` Clemens Koller

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=5be2f8f42a2cfaea381a88c5de9cbb4e@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=clemens.koller@anagramm.de \
    --cc=linuxppc-embedded@ozlabs.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).