Re: confusing comment, explanation of @IFF_RUNNING in if.h

On Sun, 26 Aug 2018, Stephen Hemminger wrote:

On Sun, 26 Aug 2018 15:20:24 -0400 (EDT)
"Robert P. J. Day" [off-list ref] wrote:

quoted

On Sun, 26 Aug 2018, Andrew Lunn wrote:

quoted

quoted

  i ask since, in my testing, when the interface should have been
up, the attribute file "operstate" for that interface showed
"unknown", and i wondered how worried i should be about that.

Hi Robert

You should probably post the driver for review. A well written
driver should not even need to care about any of this. phylib and
the netdev driver code does all the work. It only gets interesting
when you don't have a PHY, e.g. a stacked device, like bonding, or a
virtual device like tun/tap.

  i wish, but i'm on contract, and proprietary, and NDA and all that.
so i am reduced to crawling through the code, trying to figure out
what is misconfigured that is causing all this grief.

rday

So you expect FOSS developers to help you with proprietary licensed
driver. Good Luck with that.

  sorry, i'm sure this will all be released upon production, just not
while it's in the midst of development.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================