problem probing network interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



   Date: Thu, 08 May 2003 03:39:50 -0700 (PDT)
   From: "David S. Miller" <davem@redhat.com>

      From: Chris Hanson <cph@zurich.ai.mit.edu>
      Date: Wed, 07 May 2003 20:48:13 -0400

      So, could you explain to me why this change was made?

   Until we bring up the device it hasn't been programmed.
   And because of that, the link beat signal is unreliable.
   It remains unreliable until we program the PHY of the chip.

   We do not program the device into a usable state until it
   is upped so that we do not have to allocate resources (memory,
   etc.) while a device is down.

I see.  So I assume that means all of the drivers will be updated to
require this, rather than just the small number that now does?
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux