Quoting Andrew Lunn :
On Wed, Dec 12, 2018 at 08:16:55AM -0500, rpj...@crashcourse.ca wrote:
(i asked about this on the kernel newbies list earlier as a kind of
puzzle but i think i really want a definitive answer so i'm taking it
to the experts. (i will *try* to be concise.)
imagine i'm
(totally willing to embarrass myself further, this time with respect to
inconsistency in basic terminology in the kernel files.)
from include/linux/mod_devicetable.h:
/**
* struct mdio_device_id - identifies PHY devices on an MDIO/MII bus
* @phy_id: The result of
* (mdio_read(&MII_PHY
(i asked about this on the kernel newbies list earlier as a kind of
puzzle but i think i really want a definitive answer so i'm taking it
to the experts. (i will *try* to be concise.)
imagine i'm building a bunch of 8-port switches, using PHYs from
acme corp, who manufacture four different PHY
Quoting Eric Dumazet :
On 08/27/2018 09:16 AM, rpj...@crashcourse.ca wrote:
Quoting David Miller :
From: "Robert P. J. Day"
Date: Mon, 27 Aug 2018 04:55:29 -0400 (EDT)
another pedantic oddity -- is there a reason for these two double
negations in net/core/net-sysfs.c?
It turns an ar
Quoting David Miller :
From: "Robert P. J. Day"
Date: Mon, 27 Aug 2018 04:55:29 -0400 (EDT)
another pedantic oddity -- is there a reason for these two double
negations in net/core/net-sysfs.c?
It turns an arbitrary integer into a boolean, this is a common
construct across the kernel tre
Quoting Michal Kubecek :
On Fri, Aug 24, 2018 at 06:58:38AM -0400, rpj...@crashcourse.ca wrote:
just pedantry here ... was perusing include/linux/netdevice.h, and in the
declaration for struct net_device, the kerneldoc, one reads:
* @flags: Interface flags (a la BSD)
*
more curious pedantry ... in netdevice.h, one reads:
/* These flag bits are private to the generic network queueing
* layer; they may not be explicitly referenced by any other
* code.
*/
enum netdev_state_t {
__LINK_STATE_START,
__LINK_STATE_PRESENT,
__LINK
just pedantry here ... was perusing include/linux/netdevice.h, and in the
declaration for struct net_device, the kerneldoc, one reads:
* @flags: Interface flags (a la BSD)
* @priv_flags:Like 'flags' but invisible to userspace,
* see if.h for the def
i'm still unclear what the qualifier "volatile" means when used
WRT net_device_flags. the explanation given in include/uapi/linux/if.h:
"Flags which can be toggled through sysfs are annotated below, note
that only a few flags can be toggled and some other flags are always
preserved from the ori
I can see from the documentation that the callback adjust_link() is invoked
"for the enet controller to respond to changes in the link state." Is there
a specific list of the events that would generate such a change? Are we
talking initially opening the device, ifup/ifdown, physically unplugging
(warning that i have a few questions that are probably trivial
until i get up to speed
with networking code.)
a colleague asked for advice about the following -- apparently a
new PHY driver works
properly when being brought up with "ifconfig up", part of
that process
apparently set
11 matches
Mail list logo
