From: Jiri Slaby <jirislaby@gmail.com>
To: deepak.kodihalli@nokia.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about tty layer
Date: Thu, 13 Jan 2011 10:26:00 +0100 [thread overview]
Message-ID: <4D2EC528.1020704@gmail.com> (raw)
In-Reply-To: <CFCD2552B303EB4C99229AB4A7875CF901429DE1@008-AM1MPN1-021.mgdnok.nokia.com>
On 01/13/2011 07:16 AM, deepak.kodihalli@nokia.com wrote:
> Does the tty layer buffer requests from the host if the tty has not been opened?
>
> Supposing I'm working with an interface on /dev/ttyGS1. If the user space has not opened this yet, but USB is connected, would this allow the host to send data packets to this interface? If yes, and if user space opens ttyGS1 at a later stage and say adds a GIO watch on it for POLLIN, would user space receive that pollin?
It depends on the driver and the device. Most of devices are off until
open is called in their driver. So no buffers are filling neither in
device, nor in the kernel.
regards,
--
js
prev parent reply other threads:[~2011-01-13 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 6:16 Question about tty layer deepak.kodihalli
2011-01-13 9:26 ` Jiri Slaby [this message]
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=4D2EC528.1020704@gmail.com \
--to=jirislaby@gmail.com \
--cc=deepak.kodihalli@nokia.com \
--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.