All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: solution to printk() blocking interrupts?
Date: Mon, 22 Sep 2008 15:17:15 +1000	[thread overview]
Message-ID: <1222060635.12085.11.camel@pasglop> (raw)
In-Reply-To: <9e4733910809211634u5b37e297pe8503f08de4f19a8@mail.gmail.com>

On Sun, 2008-09-21 at 19:34 -0400, Jon Smirl wrote:
> On Sun, Sep 21, 2008 at 6:21 PM, Sergei Shtylyov
> <sshtylyov@ru.mvista.com> wrote:
> >  Implementing the poll_controller() method in the network driver is usually
> > staightforward.
> 
> Good tip, the simple implementation worked.
> 
> What controls this? "carrier detect appears untrustworthy, waiting 4 seconds"
> Get that fixed and this patch could be useful,

Does the driver properly uses netif_carrier_on/off to signal the
system when the link is up/down ?

Cheers,
Ben.

  reply	other threads:[~2008-09-22  5:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 20:53 solution to printk() blocking interrupts? Jon Smirl
2008-09-21 21:43 ` Jon Smirl
2008-09-21 22:21   ` Sergei Shtylyov
2008-09-21 23:34     ` Jon Smirl
2008-09-22  5:17       ` Benjamin Herrenschmidt [this message]
2008-09-22 11:04         ` Sergei Shtylyov
2008-09-22 11:11           ` Sergei Shtylyov
2008-09-22 14:39             ` Sergei Shtylyov
2008-09-22 14:45               ` Jon Smirl
2008-09-22 14:59                 ` Sergei Shtylyov
2008-09-22 21:27             ` Benjamin Herrenschmidt
2008-09-22 10:03       ` Sergei Shtylyov
2008-09-22 11:01         ` Sergei Shtylyov
2008-09-22 11:21   ` Sergei Shtylyov
2008-09-22 13:45     ` Jon Smirl
2008-09-23  5:46       ` Benjamin Herrenschmidt

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=1222060635.12085.11.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=jonsmirl@gmail.com \
    /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.