Re: [PATCH] new device support for forcedeth.c fourth try

[Roland Dreier <roland@topspin.com>]

>>>>> "Jeff" == Jeff Garzik <jgarzik@pobox.com> writes:

    > Andi Kleen wrote:
    >> Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
    >> writes:

    >>> Known Bug: You will get a "bad: scheduling while atomic"
    >>> message because of the msleep(500) in PHY reset.

    >>> Any suggestions how I can avoid this message? Using
    >>> mdelay(500) has its share of problems too, because it will
    >>> cause lost time.

    >> Use schedule_work() to push it into a worker thread.

    > Agreed.  This is what I am moving net drivers to, for slow
    > path stuff like chip reset or twiddling the phy.

In this case is it possible to use schedule_delayed_work() to avoid
stalling keventd for half a second?

 - R.