Re: [PATCH] MII bus API for PHY devices

From: Manfred Spraul (manfred_at_colorfullife.com)
Date: 11/19/04

  • Next message: Roman Zippel: "Re: HFS+ Bug which causes coreutils "make test" to fail"
    Date:	Fri, 19 Nov 2004 21:18:19 +0100
    To: Andy Fleming <afleming@freescale.com>, Jason McMullan <jason.mcmullan@timesys.com>
    
    

    Hi,

    I don't like the polling/interrupt setup part:
    - for a nic driver, there is no irq line that could be requested by
    mii_phy_irq_enable().
    - if the mii bus driver uses it's own timers, then locking within the
    nics will be more difficult.

    Could you make that part optional? For a nic driver, I would prefer if I
    could just call the ->startup part without the request_irq. If the nic
    irq handler notices that the nic got an event, then it would call an
    appropriate mii_bus function.

    This also applies for something like /dev/phy/xy: With natsemi, it would
    be very tricky to add proper locking. The nic as an internal phy and an
    external mii bus. The internal phy is partially visible on the external
    bus and any accesses to the phy id of the internal phy on the external
    bus cause lockups. No big deal, I just move the internal phy around [the
    phy id doesn't matter], but I would prefer if I have to do that just for
    ethtool, not for multiple interfaces.

    --
        Manfred
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Roman Zippel: "Re: HFS+ Bug which causes coreutils "make test" to fail"

    Relevant Pages

    • Re: [PATCH] MII bus API for PHY devices
      ... > - if the mii bus driver uses it's own timers, ... > nics will be more difficult. ... > and an external mii bus. ... The internal phy is partially visible on the ...
      (Linux-Kernel)
    • Re: sync/async NdisTransferData()
      ... Let's assume that NdisTransferData() call has begun. ... and NIC driver is doing some work and is going to call ... do use DMA and still need to do their DMA transfers asynchronously. ... This is in contrast to most modern NICs, ...
      (microsoft.public.development.device.drivers)
    • watchdog timeout
      ... This machine has two 3com nics and i see too much "watchdog timeout" on both cards. ... xl1: ... miibus0: <MII bus> on xl0 ...
      (freebsd-stable)
    • Re: Is it possible to bridge three NIC on a Windows 2000 Server
      ... > Where can I get a teaming NIC driver for all those NIC cards? ... There may be an add-on driver for random NICs, ... >>> multiple NIC cards on the server, you can Send Data and Retrieve data ...
      (microsoft.public.win2000.networking)
    • [RFC] irqbalance: Mark in-kernel irqbalance as obsolete, set to N by default
      ... keeps swapping irq's for NICs from cpu to cpu causing extremely high network latency. ... Another NIC driver already has severe warnings in their documentation file against using CONFIG_IRQBALANCE, but this is a general problem for all NIC drivers and other subsystems. ... I suggest that the in-kernel irqbalance is phased out, by marking it OBSOLETE first and removing the code later. ...
      (Linux-Kernel)