From: Mark Hounschell <markh@compro.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: line BRK detection on ttyS0
Date: Thu, 23 Sep 2010 16:48:14 -0400 [thread overview]
Message-ID: <4C9BBD0E.4010804@compro.net> (raw)
In-Reply-To: <20100923010329.0a66546c@lxorguk.ukuu.org.uk>
On 09/22/2010 08:03 PM, Alan Cox wrote:
> On Wed, 22 Sep 2010 15:36:48 -0400
> Mark Hounschell <markh@compro.net> wrote:
>
>> Does the kernel support sending a SIGINT from a line BRK on ttyS0 to a thread of a process
>> where the process has a controlling terminal that is NOT ttyS0 and the thread is using ttyS0
>> in a cfmakeraw mode? I see doc that implies that ttyS0 must be the controlling terminal but
>> can my thread have a controlling terminal while my main process has it's own ?
>
> If they have two different ttys open then yes at least as far as Linux is
> concerned. I don't know how glibc handles it as it can do signal groups
> and the like and delivery of signals to process not threads etc.
>
> You can see parity anyway. In PARMRK mode you get \377 \0 [whatever] for
> parity/break etc but \377 is also doubled for a real one - ie \377 \377
>
\377 \0 or [whatever] just looks like valid data to my thread though.
So you're saying it's gonna be a glibc thing and not a kernel thing that
prevents my thread from getting a signal?
Thanks
Mark
next prev parent reply other threads:[~2010-09-23 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 19:36 line BRK detection on ttyS0 Mark Hounschell
2010-09-23 0:03 ` Alan Cox
2010-09-23 20:48 ` Mark Hounschell [this message]
2010-09-23 21:23 ` Alan Cox
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=4C9BBD0E.4010804@compro.net \
--to=markh@compro.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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.