From: Russell King <rmk+lkml@arm.linux.org.uk>
To: karl malbrain <karl@petzent.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9: serial_core: uart_open
Date: Tue, 12 Jul 2005 22:03:48 +0100 [thread overview]
Message-ID: <20050712220348.D11389@flint.arm.linux.org.uk> (raw)
In-Reply-To: <02ad01c58710$ab9851c0$4b010059@petzent.com>; from karl@petzent.com on Tue, Jul 12, 2005 at 11:36:51AM -0700
On Tue, Jul 12, 2005 at 11:36:51AM -0700, karl malbrain wrote:
> The uart_open code loops waiting for CD to be asserted (whenever CLOCAL
> is not set). The bottom of the loop contains the following code:
>
> up(&state->sem);
> schedule();
> down(&state->sem);
>
> if( signal_pending(current) )
> break;
This does cause the process to sleep - in an interruptible wait.
Please give more details about the problem you're seeing. Have you
tried getting a process listing from a different virtual console,
xterm or whatever you normally use? What does that say?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-12 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 18:36 2.6.9: serial_core: uart_open karl malbrain
2005-07-12 21:03 ` Russell King [this message]
2005-07-12 21:17 ` karl malbrain
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 19:27 karl malbrain
2005-07-12 20:32 karl malbrain
[not found] <Pine.LNX.4.61.0507130850110.18969@chaos.analogic.com>
2005-07-13 17:53 ` karl malbrain
2005-07-14 8:26 ` Russell King
2005-07-14 17:16 ` karl malbrain
2005-07-14 18:57 ` Russell King
2005-07-14 19:30 ` karl malbrain
2005-07-14 22:35 ` karl malbrain
2005-07-15 7:28 ` Russell King
2005-07-15 16:02 ` karl malbrain
2005-07-15 20:32 ` Russell King
2005-07-15 20:48 ` karl malbrain
2005-07-15 16:20 ` karl malbrain
[not found] <Pine.LNX.4.61.0507151150290.11664@chaos.analogic.com>
2005-07-15 16:57 ` karl malbrain
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=20050712220348.D11389@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=karl@petzent.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.