linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: "Junping Zhang" <JZhang@erinc.com>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: question on mcc driver
Date: Thu, 30 Jan 2003 09:13:13 +0100	[thread overview]
Message-ID: <005d01c2c837$70018720$0700a8c0@pc005> (raw)
In-Reply-To: F4608F665DF5D311B231009027B70F700155D4D2@MAIL


>    Do you have some test programs for MPC8260 mcc driver that I can use? I

The driver itself does not need a particular code to be tested. Once it has
been loaded,the function module_init() provides to initialize the MCC1 on
the two TDMs C1 & D1. The interrupt handler is responsible of re-loading the
BDs after the completion of receiving process.
Obviously You must check it with an oscilloscope and verify that all the
signal needed by the MCC are active.

Be aware that all the I/O pins and accessories functions have been
previously programmed, because the driver does not provide any configuration
of the I/O neither than clocks routing

> managed to compiled
> and loaded your driver, but seems like it has some conflicts with Pete's
ATM
> driver, once I load
> ATM driver, mcc driver won't load; if I load mcc driver first, then ATM
> driver, mcc driver won't unload.

We have succesfully tested the driver with both M.V. 2.4.0-test2 (by Linux
CDK 1.2) and 2.4.4 (by ELDK 2.0.2), but unfotunately We did not implemented
any ATM driver.

Regards

Ing.Gianfranco Morandi
Eurostudio s.r.l.
Rome Italy


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2003-01-30  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F4608F665DF5D311B231009027B70F700155D4D2@MAIL>
2003-01-30  8:13 ` Ing.Gianfranco Morandi [this message]
2007-03-20 16:40 question on mcc driver aram vartanian

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='005d01c2c837$70018720$0700a8c0@pc005' \
    --to=gianfranco.morandi@euro-studio.it \
    --cc=JZhang@erinc.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).