netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Andy Gay <andy@andynet.net>
Cc: Andrew Morton <akpm@osdl.org>,
	bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
	xeb@mail.ru
Subject: Re: [Bugme-new] [Bug 6530] New: MAINLINE
Date: Fri, 12 May 2006 11:59:10 +1000	[thread overview]
Message-ID: <17507.60398.845863.783477@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1147326683.29448.80.camel@tahini.andynet.net>

Andy Gay writes:

> How does the serial driver know it has to call ppp_asynctty_wakeup()?

The serial driver is supposed to call the line discipline's wakeup
function when it has room in the output buffer and the
TTY_DO_WRITE_WAKEUP bit is set in tty->flags.  When the serial port is
set to the ppp line discipline, then it uses the functions defined in
the ppp_ldisc structure in drivers/net/ppp_async.c, and the
write_wakeup field in that structure points to ppp_asynctty_wakeup.

> There were a bunch of changes to the serial drivers between 2.6.15 and
> 2.6.16, maybe that's where this problem was introduced. Do we know which
> serial driver is involved in the original report?

Apparently it's the pty driver.

Paul.

  parent reply	other threads:[~2006-05-12  1:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605100920.k4A9KC91018259@fire-2.osdl.org>
2006-05-10  9:33 ` [Bugme-new] [Bug 6530] New: MAINLINE Andrew Morton
2006-05-10 10:27   ` Paul Mackerras
2006-05-11  3:29     ` Andrew Morton
2006-05-11  4:01       ` Paul Mackerras
2006-05-11  4:06         ` Andrew Morton
2006-05-11  5:51     ` Andy Gay
2006-05-11  5:56       ` Andrew Morton
2006-05-13  5:27         ` Paul Mackerras
2006-05-12  1:59       ` Paul Mackerras [this message]
2006-05-12  2:12         ` Andy Gay

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=17507.60398.845863.783477@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=akpm@osdl.org \
    --cc=andy@andynet.net \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xeb@mail.ru \
    /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).