From: Clemens Koller <clemens.koller@anagramm.de>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Complete ccsr map for mpc8540 available?
Date: Tue, 31 May 2005 18:03:16 +0200 [thread overview]
Message-ID: <429C8AC4.9000801@anagramm.de> (raw)
In-Reply-To: <5be2f8f42a2cfaea381a88c5de9cbb4e@freescale.com>
Hello, Kumar!
Yes, I want to add another Local Bus Address Range for our FPGA on
an extra CS line. I've tried to do that in U-Boot as the Code is already there.
But my modified (some old 1.1.2 (not the official release) version) U-Boot
didn't work (I guess compiling issues) and rendered my Board non-bootable, which
was really no fun!
I also want to play around with the bus-timing and GPCM/UPM configurations.
So, changing U-Boot for every little waitstate and re-booting just to get
a register changed is a showstopper for me. (Yes, I know, a BDI2000 would be fun).
So I decided to do all my stuff first in linux in a module to shorten the design
cycle by a factor of 1E+3 which works fine now, as I started this immr_t thingy
for mpc8540 on my own...
Now it seems that u-boot's immap_85xx.h is pretty much what I was looking
for, I will try to merge my stuff with it and get a immap_8540.h out of it.
So, you answered my question indirectly (get back to mainline) that there
is no code available on the linux side yet, right?
I can release my stuff, if anybody is interested... no problem.
The LBC part is verified (some others are dummys and untested) and in
a /works for me/ state.
Thanks and best greets,
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
>> 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
>
next prev parent reply other threads:[~2005-05-31 16:03 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
2005-05-31 16:03 ` Clemens Koller [this message]
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=429C8AC4.9000801@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=kumar.gala@freescale.com \
--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).