public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: PATCH: tty ldisc work version 4
       [not found] <20040922141821.GA27672@devserv.devel.redhat.com>
@ 2004-09-23  0:21 ` Andrew Morton
  2004-09-23  5:48   ` Alan Cox
  0 siblings, 1 reply; 4+ messages in thread
From: Andrew Morton @ 2004-09-23  0:21 UTC (permalink / raw)
  To: Alan Cox; +Cc: linux-kernel

Alan Cox <alan@redhat.com> wrote:
>
> New features this time
> - Fix synclink layers - Paul Fulghum
> - Use tty_wakeup internally to tty_io
> - Add initial termios locking
> - Add ldisc hangup method for notification at hangup()
> - Fixed close to wait for running driver side events
> 
> The big changes this time are locking/ordering rules for termios changes. As
> well as various feature changes I've also begun commenting n_tty.c so we
> can start tackling the ldisc internal issues.

This gives me "init_dev but no ldisc" when initscripts start playing with
the USB keyboard.  The machine then stops.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: PATCH: tty ldisc work version 4
  2004-09-23  0:21 ` PATCH: tty ldisc work version 4 Andrew Morton
@ 2004-09-23  5:48   ` Alan Cox
  2004-09-24 13:43     ` Paul Fulghum
  0 siblings, 1 reply; 4+ messages in thread
From: Alan Cox @ 2004-09-23  5:48 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Alan Cox, linux-kernel

On Wed, Sep 22, 2004 at 05:21:39PM -0700, Andrew Morton wrote:
> > The big changes this time are locking/ordering rules for termios changes. As
> > well as various feature changes I've also begun commenting n_tty.c so we
> > can start tackling the ldisc internal issues.
> 
> This gives me "init_dev but no ldisc" when initscripts start playing with
> the USB keyboard.  The machine then stops.

Intriguing. Does this go way if you uncomment the lines below
"Switchg the line discipline back" in tty_io.c.

I'll stick a USB keyboard on my box later today and chase that down.

Alan


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: PATCH: tty ldisc work version 4
  2004-09-24 13:43     ` Paul Fulghum
@ 2004-09-24 13:04       ` Alan Cox
  0 siblings, 0 replies; 4+ messages in thread
From: Alan Cox @ 2004-09-24 13:04 UTC (permalink / raw)
  To: Paul Fulghum; +Cc: Alan Cox, Andrew Morton, Linux Kernel Mailing List

On Gwe, 2004-09-24 at 14:43, Paul Fulghum wrote:
> Did this turn out to be related to the code
> in release_dev() that switches back a tty struct
> back to N_TTY ldisc before freeing the tty struct?

No it was just a stupid mistake in my code. I'll propogate the
other changes back in now I've found it.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: PATCH: tty ldisc work version 4
  2004-09-23  5:48   ` Alan Cox
@ 2004-09-24 13:43     ` Paul Fulghum
  2004-09-24 13:04       ` Alan Cox
  0 siblings, 1 reply; 4+ messages in thread
From: Paul Fulghum @ 2004-09-24 13:43 UTC (permalink / raw)
  To: Alan Cox; +Cc: Andrew Morton, linux-kernel

On Thu, 2004-09-23 at 00:48, Alan Cox wrote:
> On Wed, Sep 22, 2004 at 05:21:39PM -0700, Andrew Morton wrote:
> > This gives me "init_dev but no ldisc" when initscripts start playing with
> > the USB keyboard.  The machine then stops.
> 
> Intriguing. Does this go way if you uncomment the lines below
> "Switchg the line discipline back" in tty_io.c.
> 
> I'll stick a USB keyboard on my box later today and chase that down.

Andrew, Alan:

Did this turn out to be related to the code
in release_dev() that switches back a tty struct
back to N_TTY ldisc before freeing the tty struct?

-- 
Paul Fulghum
paulkf@microgate.com


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-09-24 14:07 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20040922141821.GA27672@devserv.devel.redhat.com>
2004-09-23  0:21 ` PATCH: tty ldisc work version 4 Andrew Morton
2004-09-23  5:48   ` Alan Cox
2004-09-24 13:43     ` Paul Fulghum
2004-09-24 13:04       ` Alan Cox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox