linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dmitriy.Zavin@infineon.com
Cc: Chuck_Partridge@amx.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: SCC2 and SCC3 serial ports on RPX Classic (MPC860)
Date: Thu, 27 Mar 2003 00:57:40 +0100	[thread overview]
Message-ID: <20030326235745.437B0C58BA@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 26 Mar 2003 14:38:40 PST." <FD90897E35ABD311AE0E0008C7E6404A07192EE0@ca02exch4.sjc.infineon.com>


In message <FD90897E35ABD311AE0E0008C7E6404A07192EE0@ca02exch4.sjc.infineon.com> you wrote:
>
> I also took a look at the hex values that I actually receive and it does NOT look like the bit-string is offset by any bits. There's no direct mapping that I can see..

Well, can you post an example, i. e. which output  do  you  get  when
sending the string "01234567890123456789abcdefghabcdefgh" ?


Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I usually tell my classes "if you are using @ and [] together in this
class, you will almost certainly NOT get what you want. That's  going
down  the wrong tunnel. There's no cheese at the end of that tunnel."
         -- Randal L. Schwartz in <8czptuomey.fsf@gadget.cscaper.com>

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

  reply	other threads:[~2003-03-26 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:38 SCC2 and SCC3 serial ports on RPX Classic (MPC860) Dmitriy.Zavin
2003-03-26 23:57 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 22:21 Chuck Partridge
2003-03-26 19:17 Dmitriy.Zavin
2003-03-26 20:27 ` Dan Malek
2003-03-26 21:54 ` Wolfgang Denk

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=20030326235745.437B0C58BA@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Chuck_Partridge@amx.com \
    --cc=Dmitriy.Zavin@infineon.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).