From: "Mark A. Greer" <mgreer@mvista.com>
To: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: [PATCH} include/asm-ppc/cpu2.h typo
Date: Tue, 22 Feb 2005 16:32:33 -0700 [thread overview]
Message-ID: <421BC111.1050602@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hi,
This bug/typo was pointed out to me. I looked at the 8260 & 8272
manuals and it should be 0x0002 in both cases. I don't work with the
82[67]x processors but it looks like this would have quickly bit anyone
trying even parity on their serial line. Nobody uses even parity on
those platforms? Is there something I don't know (and the manual isn't
telling me)?
Mark
[-- Attachment #2: cpm2_1.patch --]
[-- Type: text/plain, Size: 432 bytes --]
diff -Nru a/include/asm-ppc/cpm2.h b/include/asm-ppc/cpm2.h
--- a/include/asm-ppc/cpm2.h 2005-02-22 16:26:07 -07:00
+++ b/include/asm-ppc/cpm2.h 2005-02-22 16:26:07 -07:00
@@ -531,7 +531,7 @@
#define SCU_PSMR_RPM ((ushort)0x000c)
#define SCU_PSMR_REVP ((ushort)0x0008)
#define SCU_PSMR_TPM ((ushort)0x0003)
-#define SCU_PSMR_TEVP ((ushort)0x0003)
+#define SCU_PSMR_TEVP ((ushort)0x0002)
/* CPM Transparent mode SCC.
*/
reply other threads:[~2005-02-22 23:32 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=421BC111.1050602@mvista.com \
--to=mgreer@mvista.com \
--cc=linuxppc-embedded@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).