linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "mike zheng" <mail4mz@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: MCC problem of MPC8568
Date: Tue, 15 Apr 2008 14:29:00 -0400	[thread overview]
Message-ID: <5c9cd53b0804151129s2006af68n79975e8a8c07177b@mail.gmail.com> (raw)

Hi,

Currently, I have problem of the UBoot MCC driver. I setup the
internal loopback on MPC8568. And here is the data of each channel:

           Channel #                Tx Data            Rx Data
                  0                         0x01                0x9D
                  1                         0x02                0xE1
                  2                         0x03                0x9E
                  3                         0x04                0xF1
                  4                         0x05                0x83
           ...

Any idea on this issue? Or where can I find a working MCC Uboot driver
of MPC8568?

Thanks for your help,

Mike

             reply	other threads:[~2008-04-15 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 18:29 mike zheng [this message]
2008-04-15 18:29 ` MCC problem of MPC8568 mike zheng

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=5c9cd53b0804151129s2006af68n79975e8a8c07177b@mail.gmail.com \
    --to=mail4mz@gmail.com \
    --cc=linuxppc-dev@ozlabs.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).