LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "bhanu jampala" <adams.ppc@gmail.com>
To: linuxppc-embedded@ozlabs.org
Cc: Scott Wood <scottwood@freescale.com>, rmcguire@videopresence.com
Subject: How many super channels per TDM on MCC
Date: Fri, 29 Aug 2008 14:53:03 -0600	[thread overview]
Message-ID: <4a21eaea0808291353p29992a2che64854f93829d706@mail.gmail.com> (raw)

Hi Guys,

This is regarding MCC controller on MPC8260.
I am having problems figuring out how super channels fit into a TDM.

A superchannel is the combination of multiple MCC TX channels' FIFOs and one
set of an MCC channel's parameters and buffer descriptors.

If I want to support 24 super channels with 4 timeslots each.
Can I use a single TDM (i.e. from A,B ,C, D) to accomplish this task.
(each TDM has 32 timeslots).

- Mukund Jampala

             reply	other threads:[~2008-08-29 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 20:53 bhanu jampala [this message]
2008-08-29 21:55 ` How many super channels per TDM on MCC Russell McGuire

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=4a21eaea0808291353p29992a2che64854f93829d706@mail.gmail.com \
    --to=adams.ppc@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rmcguire@videopresence.com \
    --cc=scottwood@freescale.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