From: Steven Vacca <svacca@valcom.com>
To: "LinuxEmbeddedMailList (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: QMC SCC2 time slot data input to data buffer.
Date: Wed, 3 Apr 2002 15:43:58 -0500 [thread overview]
Message-ID: <01C1DB26.5F692110.svacca@valcom.com> (raw)
I have an MPC860T setup, using QMC mode.
In my kernel driver, in the immap_t struct, I set the QMC Multi-channel
base ptr = the address of the Buffer Desc pool. I also set the interrupt
queue ptr = the addr of the circular interrupt queue.
When a QMC channel is activated, for Rx, then TDM data should get
written to a buffer, thru the associated TDM time slot.
My question is,
is it OK to allocate the Rx Buff Descriptor Pool in the Kernel driver,
and then set the immap_t reg using that kernel space addr,
or do I need to do any kind of re-mapping in order
for the external CPM hardware section to access kernel space memory?
Once the data is written into the buffer, SCC2 should interrupt, for
data buff processing.
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-04-03 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01C1DB26.5F692110.svacca@valcom.com \
--to=svacca@valcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.