linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: serial on lombard
Date: Thu, 14 Oct 1999 16:34:25 +0200	[thread overview]
Message-ID: <19991014163425.001988@mailhost.mipsys.com> (raw)
In-Reply-To: <199910141421.QAA10144@opal.biophys.uni-duesseldorf.de>


On Thu, Oct 14, 1999, Michael Schmitz
<schmitz@opal.biophys.uni-duesseldorf.de> wrote:

>Nah, that's the 2.5 sec wait for powering up the modem, which is,
>unfortunately, before the block_til_ready. We could forgo this wait period
>on O_NONBLOCK (maybe mark the wait pending, and make the next operation wait
>instead). 
>Anyway: how come open returns successfully but minicom still gets the
>timeout? 

I fixed my minicom by bumping the timeout to 4 seconds:

--- minicom-1.82.orig/src/main.c	Thu Aug 27 00:54:16 1998
+++ minicom-1.82/src/main.c	Thu Oct 14 16:20:00 1999
@@ -158,7 +158,7 @@
   if (setjmp(albuf) == 0) {
 	portfd = -1;
 	signal(SIGALRM, get_alrm);
-	alarm(2);
+	alarm(4);
 #if defined(O_NDELAY) && defined(F_SETFL)
 	portfd = open(dial_tty, O_RDWR|O_NDELAY);
 	if (portfd >= 0){

I'll send this to the maintainer as well.

I'd like to add the patch to the existing patches in the .rpm, however I
don't know at all how RPM works and how to re-package that stuff, and I
really don't have time to read a doc today.

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-14 14:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-14 19:12 serial on lombard Mario Scarpa
1999-10-14 11:06 ` Benjamin Herrenschmidt
1999-10-14 11:19 ` Michael Schmitz
1999-10-14 11:31   ` Momchil Velikov
1999-10-14 12:35     ` Chris Ridd
1999-10-14 13:06       ` Benjamin Herrenschmidt
1999-10-14 13:43         ` Momchil Velikov
1999-10-14 14:21         ` Michael Schmitz
1999-10-14 14:34           ` Benjamin Herrenschmidt [this message]
1999-10-14 14:53             ` Momchil Velikov
1999-10-14 16:10               ` Michael Schmitz
1999-10-15  7:26                 ` Momchil Velikov
1999-10-14 16:00             ` Michael Schmitz
1999-10-14 16:10               ` Benjamin Herrenschmidt
1999-10-14 17:41                 ` Michael Schmitz
1999-10-15  4:12                   ` Mario Scarpa
1999-10-15  8:33                     ` Benjamin Herrenschmidt
1999-10-15 20:17                       ` Mario Scarpa
1999-10-15  8:42                     ` Michael Schmitz

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=19991014163425.001988@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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).