From: "Jim Deas" <jdeas@jadsystems.com>
To: linux-serial@vger.kernel.org
Subject: async structure for serial.c
Date: Sat, 26 Oct 2002 14:59:00 -0700 [thread overview]
Message-ID: <000701c27d3a$e4c50ed0$0264a8c0@jadp4> (raw)
I have just upgraded my kernel from 2.4.7 to 2.4.18
After the upgrade I started having problems with
my "signal_handler_IO".
In the old version, this seemed to trigger only when
bytes were waiting on the serial port. It now seems
to trigger on send as well as receive increasing my
overhead.
I saw where TTY_DO_WRITE_WAKEUP was
added to kernel/serial.c.
Was this to create the action I am seeing? If so,
is there a way that only received characters can
trigger SIGIO and not a Tx ready or Tx send?
Regards,
J. Deas
reply other threads:[~2002-10-26 21:50 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='000701c27d3a$e4c50ed0$0264a8c0@jadp4' \
--to=jdeas@jadsystems.com \
--cc=linux-serial@vger.kernel.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.