From: Chris Hallinan <clh@zing.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: ioctl constants
Date: Tue, 28 Mar 2000 15:25:22 -0500 [thread overview]
Message-ID: <38E11532.958228C3@zing.net> (raw)
I'm using kernel 2.2.13 and a slightly modified version of serial.c to
operate an additional 16550 device at a non-standard i/o address.
I'm troublshooting a ppp disconnect problem which has led me to the
serial driver. I've noticed that a large number of rs_ioctl() calls hit
the driver with incorrect constants. Using printk()'s, I'm able to
determine what values are being passed in, but of course, not who is
calling them.
I've studied the related header files: the constants used in serial.c
are hard coded in asm/ioctls.h. (Two examples are TIOCGSERIAL and
TIOCSSERIAL for get/set_serial_info). I've grepped for these values,
and don't see anywhere where they are re-defined. Virtually every ioctl
that hits the driver has a bad value.
I can only assume that the results of this are ugly! I'm guessing that
the libraries are compiled with a different convention? Has anyone run
into this issue?
-Chris Hallinan
DS4.COM, Inc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-28 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 20:25 Chris Hallinan [this message]
[not found] <20000329001916.D2C3C355E2@elph.research.canon.com.au>
2000-03-29 17:55 ` ioctl constants Chris Hallinan
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=38E11532.958228C3@zing.net \
--to=clh@zing.net \
--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).