From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wade Maxfield" <wmaxfield@gmail.com>
Cc: ppc <linuxppc-embedded@ozlabs.org>
Subject: Re: PPC beginner questions
Date: Mon, 21 Aug 2006 08:14:36 -0600 [thread overview]
Message-ID: <528646bc0608210714g51928043lb729e80bda753d4d@mail.gmail.com> (raw)
In-Reply-To: <45a1b53e0608210651s4f5de382w77e092463dbbf5b7@mail.gmail.com>
On 8/21/06, Wade Maxfield <wmaxfield@gmail.com> wrote:
>
> We are using Xilinx with PPC built in.
>
> The PPC has a memory management unit. All of the IP we've added is
> mapped to physical addresses.
>
> 1. Can I access the memory the peripherasl are mapped to directly within
> the driver without going through functions?
No, you need to map them into virtual memory, then you can use the in*
out* functions to read/write. (You can also directly use the virtual
addresses as pointers, but in*/out* is more portable)
> if NOT, then Do I use
> 1. ioremap(),
> 2. request_mem_region(),
> 3. request_region()
> 4. something else?
ioremap
>
> 2. Are there any gotcha's with the ppc 405 that Xilinx uses that I
> should know about?
Yes, lots. :)
Actually it's pretty straight forward. Mainline Linux 2.6 contains
support for both the Virtex-II Pro and the Virtex 4, but not a lot of
device drivers. The MontaVista 2.4 tree is supported by Xilinx with
drivers, but then you have to use linux 2.4. :p
Also, it's a good idea to read the Xilinx errata.
have fun.
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2006-08-21 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 13:51 PPC beginner questions Wade Maxfield
2006-08-21 14:14 ` Grant Likely [this message]
[not found] ` <45a1b53e0608210759p270c2f8dy694e91f409d57729@mail.gmail.com>
2006-08-21 15:38 ` Grant Likely
2006-08-21 16:07 ` Wade Maxfield
2006-08-21 16:24 ` Grant Likely
2006-08-22 8:53 ` David H. Lynch Jr.
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=528646bc0608210714g51928043lb729e80bda753d4d@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wmaxfield@gmail.com \
/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).