From: Matt Gessner <mattg@aiinet.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 8260, FCC and local bus
Date: Tue, 27 Jun 2000 10:36:33 -0400 [thread overview]
Message-ID: <3958BBF1.20E543AB@aiinet.com> (raw)
Hello list,
Has anyone done anything with mapping local bus memory
so that it can be used for FCC BD's and buffers?
I **thought** I had it right, but my driver eventually
causes the machine to hang (EST SBC8260).
I had ioremap'd it, and put va's and pa's where each belonged
(va's for the kernel's tracking stuff and pa's for the CPM stuff).
Alas, to no avail.
Has anyone had any success with this, and if so, would you be
willing to share?
TIA,
--
Matt Gessner, mattg@aiinet.com--NOSPAM
Senior Software Engineer, R&D
Applied Innovation, Inc.
614-798-2000
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-06-27 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-27 14:36 Matt Gessner [this message]
2000-06-27 20:01 ` 8260, FCC and local bus Matt Gessner
2000-06-27 23:19 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-09-24 15:48 8260 " Sylvain Latulippe
2002-09-24 16:25 ` Allen Curtis
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=3958BBF1.20E543AB@aiinet.com \
--to=mattg@aiinet.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).