All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Definitions for c_cflag etc. in termbits.h???
Date: Fri, 10 Jan 2003 16:09:51 +0100	[thread overview]
Message-ID: <3E1EE23F.5BC310F3@imc-berlin.de> (raw)


Hi there,

I am playing around with UARTs and got completly confused when looking at
./include/asm-ppc/termbits.h:

E.g. the DEFINEs of c_iflags appear to me as decimal values!?

/* c_iflag bits */
#define IGNBRK  0000001
#define BRKINT  0000002
#define IGNPAR  0000004
#define PARMRK  0000010
#define INPCK   0000020
#define ISTRIP  0000040
#define INLCR   0000100
#define IGNCR   0000200
#define ICRNL   0000400
#define IXON    0001000
#define IXOFF   0002000
#define IXANY   0004000
#define IUCLC   0010000
#define IMAXBEL 0020000

So how could code like

./arch/ppc/8xx_io/uart.c:       if (I_BRKINT(info->tty) || I_PARMRK(info->tty))
or
./arch/ppc/8xx_io/uart.c:#define RELEVANT_IFLAG(iflag) (iflag &
(IGNBRK|BRKINT|IGNPAR|PARMRK|INPCK))

possibly work?

Shouldn't that be hex values as in ./include/asm-sparc64/termbits.h:

/* c_iflag bits */
#define IGNBRK  0x00000001
#define BRKINT  0x00000002
#define IGNPAR  0x00000004
#define PARMRK  0x00000008
#define INPCK   0x00000010
#define ISTRIP  0x00000020
#define INLCR   0x00000040
#define IGNCR   0x00000080
etc. ???

Thanks,

Steven

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

             reply	other threads:[~2003-01-10 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 15:09 Steven Scholz [this message]
2003-01-10 15:19 ` Definitions for c_cflag etc. in termbits.h??? Marius Groeger
2003-01-10 15:25 ` Wolfgang Denk
2003-01-10 15:27 ` Steven Scholz
2003-01-10 16:25 ` "David Müller (ELSOFT AG)"
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 15:18 Milliorn Gary-rxcr80
2003-01-10 15:33 ` 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=3E1EE23F.5BC310F3@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.