From: Philip Oberstaller <Philip.Oberstaller@septentrio.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: Printf hangs when internal buffer of driver is temporarily full
Date: Tue, 15 Jan 2013 15:23:58 +0100 [thread overview]
Message-ID: <50F5667E.8010303@septentrio.com> (raw)
In-Reply-To: <20130114193645.63a2d12c@pyramind.ukuu.org.uk>
On 01/14/2013 08:36 PM, Alan Cox wrote:
>> which happens when the driver's internal buffer is temporarily full.
>> I would have expected that the TTY layer or the libc implementation of
>> printf would requery write_room automatically and thus would notice
>
> How is it going to magically notice ?
>
>> after a while that there is space again, but this doesn't seem to happen.
>> Eventually the printf function returns after a very long timeout but without
>> that the remaining characters have been printed.
>
> You need to wake it up and tell it there is room in your completion
> interrupts. It will then think about retrying.
Yeah, behind the magic there is most of the time some manual work. Thanks
for the hint of the wakeup! That definitely makes it working. Don't ask
me why I didn't see it before...
> I would suggest recycling that book 8)
Agreed, but as it's pretty cold these days, it might well be used for
some other purpose...
(Sorry for the disclaimer, but it cannot be circumvented when sending
from this domain - at least I would not know how)
________________________________
This e-mail communication contains information that is confidential and may also be privileged. It is intended for the exclusive use of the addressees. If you are not the person or organization to whom it is addressed, you must not copy, distribute or take any action in reliance upon it. If you received this communication in error, please notify Septentrio nv immediately [ telephone +32 [0] 16 300800 ]. Septentrio nv will not accept liability for contractual commitments made by individuals employed by this company outside the scope of our business.
prev parent reply other threads:[~2013-01-15 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 13:11 Printf hangs when internal buffer of driver is temporarily full Philip Oberstaller
2013-01-14 16:19 ` Greg KH
2013-01-14 19:36 ` Alan Cox
2013-01-15 14:23 ` Philip Oberstaller [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=50F5667E.8010303@septentrio.com \
--to=philip.oberstaller@septentrio.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox