Netdev List
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Fleming Andy <afleming@freescale.com>,
	Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [PATCH 7/9] [ETH]: Start net device with carrier down
Date: Wed, 24 Sep 2008 15:43:55 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0809241534370.7680@t2.domain.actdsltmp> (raw)
In-Reply-To: <20080924.152457.13104395.davem@davemloft.net>

On Wed, 24 Sep 2008, David Miller wrote:
> From: Trent Piepho <tpiepho@freescale.com>
> Date: Wed, 24 Sep 2008 14:20:55 -0700
>
>> The problem is that when the device is first created and opened, the state
>> bit indicating the carrier is down isn't set, i.e. the state is wrong.
>> When the carrier comes up for the first time no netlink event is sent,
>> since the device state indicated the carrier was already up.
>
> It works properly if the device driver does as it is supposed to,
> which is invoke netif_carrier_off() in it's ->open() method in this
> situation.
>
> Please fix the drivers where this is not happening.

I tried that first, but if the carrier is already up, opening the interface
generated extra rt-netlink messages for carrier down then carrier up, even
though the carrier was up all along.

But maybe I didn't have it at the right place in the open() method.  I'll try
Stephen's suggestion to put it after allocation but before register_netdev()
and see if the problem is still there.

  reply	other threads:[~2008-09-24 22:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e665d9ff8b50796ce65c503604453056217bfc8a.1221537369.git.tpiepho@freescale.com>
2008-09-24 21:20 ` [PATCH 7/9] [ETH]: Start net device with carrier down Trent Piepho
2008-09-24 21:32   ` Stephen Hemminger
2008-09-24 22:25     ` David Miller
2008-09-24 22:24   ` David Miller
2008-09-24 22:43     ` Trent Piepho [this message]
2008-10-02 21:12       ` [PATCH v2] gianfar: Create " Trent Piepho

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=Pine.LNX.4.64.0809241534370.7680@t2.domain.actdsltmp \
    --to=tpiepho@freescale.com \
    --cc=afleming@freescale.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox