From: "Bob White" <bwhite@perigee.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Dual-Port SRAM
Date: Mon, 03 May 2004 12:47:43 -0400 [thread overview]
Message-ID: <40963F6F.31001.1A36BB44@localhost> (raw)
I've got a board with a dual-port SRAM attached to the 440GP on the
peripheral bus (at CS1_N). I can map the TLB and access the device
from the bdi2000 and the u-boot command prompt.
What configuration is necessary to map this memory into the kernel?
Can you point me to some examples? How does it then get accessed from
a user program?
Thanks.
Bob
--
Robert B. White Perigee, A Division of Sensis Corp
Software Design Engr 316 Commerce Blvd.
TEL: 315.453.7842x29 Liverpool, NY 13088
FAX: 315.453.7917 www.Perigee.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-05-03 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 16:47 Bob White [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-04 8:48 Dual-Port SRAM Fillod Stephane
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=40963F6F.31001.1A36BB44@localhost \
--to=bwhite@perigee.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).