> still didn't apply

---
From: Randy Dunlap <[EMAIL PROTECTED]>

PHYLIB can be used by non-NET_ETHERNET (10/100 ethernet) devices;
e.g., GIANFAR (gigabit) uses it.

We also have USB ethernet devices trying to use MII
without NET_ETHERNET being enabled, so move MII outside of
NET_ETHERNET, along with PHYLIB.

They both still depend on NET && NETDEVICES.

Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
 drivers/net/Kconfig     |   16 ++++++++--------
 drivers/net/phy/Kconfig |   21 +++++----------------
 2 files changed, 13 insertions(+), 24 deletions(-)

--- netdev-ups.orig/drivers/net/Kconfig
+++ netdev-ups/drivers/net/Kconfig
@@ -145,6 +145,14 @@ config NET_SB1000
 
 source "drivers/net/arcnet/Kconfig"
 
+config MII
+       tristate "Generic Media Independent Interface device support"
+       depends on NET_ETHERNET
+       help
+         Most ethernet controllers have MII transceiver either as an external
+         or internal device.  It is safe to say Y or M here even if your
+         ethernet card lack MII.
+
 source "drivers/net/phy/Kconfig"
 
 #
@@ -180,14 +188,6 @@ config NET_ETHERNET
          kernel: saying N will just cause the configurator to skip all
          the questions about Ethernet network cards. If unsure, say N.
 
-config MII
-       tristate "Generic Media Independent Interface device support"
-       depends on NET_ETHERNET
-       help
-         Most ethernet controllers have MII transceiver either as an external
-         or internal device.  It is safe to say Y or M here even if your
-         ethernet card lack MII.
-
 config MACB
        tristate "Atmel MACB support"
        depends on NET_ETHERNET && AVR32
--- netdev-ups.orig/drivers/net/phy/Kconfig
+++ netdev-ups/drivers/net/phy/Kconfig
@@ -2,69 +2,59 @@
 # PHY Layer Configuration
 #
 
-menu "PHY device support"
-
-config PHYLIB
+menuconfig PHYLIB
        tristate "PHY Device support and infrastructure"
-       depends on NET_ETHERNET && (BROKEN || !S390)
+       depends on (BROKEN || !S390)
        help
          Ethernet controllers are usually attached to PHY
          devices.  This option provides infrastructure for
          managing PHY devices.
 
+if PHYLIB
+
 comment "MII PHY device drivers"
-       depends on PHYLIB
 
 config MARVELL_PHY
        tristate "Drivers for Marvell PHYs"
-       depends on PHYLIB
        ---help---
          Currently has a driver for the 88E1011S
        
 config DAVICOM_PHY
        tristate "Drivers for Davicom PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports dm9161e and dm9131
 
 config QSEMI_PHY
        tristate "Drivers for Quality Semiconductor PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports the qs6612
 
 config LXT_PHY
        tristate "Drivers for the Intel LXT PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports the lxt970, lxt971
 
 config CICADA_PHY
        tristate "Drivers for the Cicada PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports the cis8204
 config VITESSE_PHY
         tristate "Drivers for the Vitesse PHYs"
-        depends on PHYLIB
         ---help---
           Currently supports the vsc8244
 
 config SMSC_PHY
        tristate "Drivers for SMSC PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports the LAN83C185 PHY
 
 config BROADCOM_PHY
        tristate "Drivers for Broadcom PHYs"
-       depends on PHYLIB
        ---help---
          Currently supports the BCM5411, BCM5421 and BCM5461 PHYs.
 
 config FIXED_PHY
        tristate "Drivers for PHY emulation on fixed speed/link"
-       depends on PHYLIB
        ---help---
          Adds the driver to PHY layer to cover the boards that do not have any 
PHY bound,
          but with the ability to manipulate the speed/link in software. The 
relevant MII
@@ -79,5 +69,4 @@ config FIXED_MII_100_FDX
        bool "Emulation for 100M Fdx fixed PHY behavior"
        depends on FIXED_PHY
 
-endmenu
-
+endif #PHYLIB
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to