- Original Message -
From: "Russell King" <[EMAIL PROTECTED]>
To: "karl malbrain" <[EMAIL PROTECTED]>
Cc: "[EMAIL PROTECTED] Kernel. Org"
Sent: Friday, July 15, 2005 1:32 PM
Subject: Re: 2.6.9: serial_core: uart_open
> On Fri, Jul 15,
On Fri, Jul 15, 2005 at 09:02:48AM -0700, karl malbrain wrote:
> > -Original Message-
> > From: Russell King
> > Sent: Friday, July 15, 2005 12:29 AM
> > To: karl malbrain
> > Cc: [EMAIL PROTECTED] Kernel. Org
> > Subject: Re: 2.6.9: serial_core: uart_o
> -Original Message-
> From: Richard B. Johnson
> Sent: Friday, July 15, 2005 8:53 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: RE: 2.6.9: serial_core: uart_open
>
>
> On Wed, 13 Jul 2005, karl malbrain wrote:
>
> > I've also n
> -Original Message-
> From: Russell King
> Sent: Friday, July 15, 2005 12:29 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: Re: 2.6.9: serial_core: uart_open
>
>
> On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
&
> -Original Message-
> From: Russell King
> Sent: Friday, July 15, 2005 12:29 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: Re: 2.6.9: serial_core: uart_open
>
>
> On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
&
On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
> AT LAST I HAVE SOME DATA!!!
>
> The problem is that ALL SYSTEM CALLS to open "/dev/tty" are blocking!! even
> with O_NDELAY set and even from completely disjoint sessions. I discovered
> this via issuing "strace sh". That's why
On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
AT LAST I HAVE SOME DATA!!!
The problem is that ALL SYSTEM CALLS to open /dev/tty are blocking!! even
with O_NDELAY set and even from completely disjoint sessions. I discovered
this via issuing strace sh. That's why the new
-Original Message-
From: Russell King
Sent: Friday, July 15, 2005 12:29 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
AT LAST I HAVE SOME DATA!!!
The problem
-Original Message-
From: Russell King
Sent: Friday, July 15, 2005 12:29 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Thu, Jul 14, 2005 at 03:35:07PM -0700, karl malbrain wrote:
AT LAST I HAVE SOME DATA!!!
The problem
-Original Message-
From: Richard B. Johnson
Sent: Friday, July 15, 2005 8:53 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: RE: 2.6.9: serial_core: uart_open
On Wed, 13 Jul 2005, karl malbrain wrote:
I've also noticed that the boot sequence probes for modems
On Fri, Jul 15, 2005 at 09:02:48AM -0700, karl malbrain wrote:
-Original Message-
From: Russell King
Sent: Friday, July 15, 2005 12:29 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Thu, Jul 14, 2005 at 03:35:07PM
- Original Message -
From: Russell King [EMAIL PROTECTED]
To: karl malbrain [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] Kernel. Org linux-kernel@vger.kernel.org
Sent: Friday, July 15, 2005 1:32 PM
Subject: Re: 2.6.9: serial_core: uart_open
On Fri, Jul 15, 2005 at 09:02:48AM -0700, karl
> -Original Message-
> From: Russell King
> Sent: Thursday, July 14, 2005 11:57 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: Re: 2.6.9: serial_core: uart_open
>
>
> On Thu, Jul 14, 2005 at 10:16:23AM -0700, karl malbrain wrote:
>
> -Original Message-
> From: Russell King [mailto:[EMAIL PROTECTED] Behalf Of Russell
> King
> Sent: Thursday, July 14, 2005 11:57 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: Re: 2.6.9: serial_core: uart_open
>
>
> On Thu, Jul 14,
On Thu, Jul 14, 2005 at 10:16:23AM -0700, karl malbrain wrote:
> I'd love to do a ps listing for you, but, except for the mouse, the system
> is completely unresponsive after issuing the blocking open("/dev/ttyS1",
> O_RDRW).
>
> Telnet is dead; the console will respond to the mouse, but the only
> -Original Message-
> From: Russell King
> Sent: Thursday, July 14, 2005 1:27 AM
> To: karl malbrain
> Cc: [EMAIL PROTECTED] Kernel. Org
> Subject: Re: 2.6.9: serial_core: uart_open
>
>
> On Wed, Jul 13, 2005 at 10:53:19AM -0700, karl malbrain wrote:
> >
On Wed, Jul 13, 2005 at 10:53:19AM -0700, karl malbrain wrote:
> I've also noticed that the boot sequence probes for modems on the serial
> ports. Is it possible that 8250.c is having a problem servicing an
> interrupt from a character/state-change left over from this initialization?
I did ask
On Wed, Jul 13, 2005 at 10:53:19AM -0700, karl malbrain wrote:
I've also noticed that the boot sequence probes for modems on the serial
ports. Is it possible that 8250.c is having a problem servicing an
interrupt from a character/state-change left over from this initialization?
I did ask for
-Original Message-
From: Russell King
Sent: Thursday, July 14, 2005 1:27 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Wed, Jul 13, 2005 at 10:53:19AM -0700, karl malbrain wrote:
I've also noticed that the boot sequence
-Original Message-
From: Russell King
Sent: Thursday, July 14, 2005 11:57 AM
To: karl malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: Re: 2.6.9: serial_core: uart_open
On Thu, Jul 14, 2005 at 10:16:23AM -0700, karl malbrain wrote:
I'd love to do a ps listing for you
malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: RE: 2.6.9: serial_core: uart_open
The attached code will set the UART to a sane state, then
clear the local flag, then open, waiting for modem control.
It clearly works, executing `ps` from another terminal will
clearly show that the task waiting
malbrain
Cc: [EMAIL PROTECTED] Kernel. Org
Subject: RE: 2.6.9: serial_core: uart_open
The attached code will set the UART to a sane state, then
clear the local flag, then open, waiting for modem control.
It clearly works, executing `ps` from another terminal will
clearly show that the task waiting
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(>sem);
> schedule();
> down(>sem);
>
> if( signal_pending(current) )
>break;
-Original Message-
From: Russell King
Sent: Tuesday, July 12, 2005 2:04 PM
To: karl malbrain
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9: serial_core: uart_open
On Tue, Jul 12, 2005 at 11:36:51AM -0700, karl malbrain wrote:
> The uart_open code loops waiting for
>On Tue, 12 Jul 2005, karl malbrain wrote:
>
>>> On Tue, 12 Jul 2005, 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(>sem);
schedule();
down(>sem);
>On Tue, 12 Jul 2005, 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(>sem);
>> schedule();
>> down(>sem);
>>
>> if( signal_pending(current) )
>> break;
>>
>> When I
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(>sem);
schedule();
down(>sem);
if( signal_pending(current) )
break;
When I issue an open("/dev/ttyS1", O_RDWR) from a terminal session on
the
-Original Message-
From: Russell King
Sent: Tuesday, July 12, 2005 2:04 PM
To: karl malbrain
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9: serial_core: uart_open
On Tue, Jul 12, 2005 at 11:36:51AM -0700, karl malbrain wrote:
The uart_open code loops waiting for CD
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;
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;
When I issue an open(/dev/ttyS1, O_RDWR) from a terminal session on
the
On Tue, 12 Jul 2005, 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;
When I issue an
On Tue, 12 Jul 2005, karl malbrain wrote:
On Tue, 12 Jul 2005, 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(
32 matches
Mail list logo
