Re: [PATCH] 3c59x: read current link status from phy

From: Bogdan Costescu (Bogdan.Costescu_at_iwr.uni-heidelberg.de)
Date: 09/09/05

  • Next message: Jan Beulich: "Re: [PATCH] new kallsyms approach"
    Date:	Fri, 9 Sep 2005 12:10:04 +0200 (CEST)
    To: Andy Fleming <afleming@freescale.com>
    
    

    On Thu, 8 Sep 2005, Andy Fleming wrote:

    > The new PHY Layer (drivers/net/phy/*) can provide all these features
    > for you without much difficulty, I suspect.

    As pointed to be Andrew a few days ago, this driver supports a lot of
    chips - for most of them the test hardware would be hard to come by
    and the documentation even more. Unless you'd like to do it based on
    "whoever is interested should cry loud"...

    > The layer supports handling the interrupts for you, or (if it's
    > shared with your controller's interrupt)

    Yes, there is only one interrupt that for data transmission (both Tx
    and Rx), statistics, errors and (for those chips that support it) link
    state change.

    > Is the cost of an extra read every minute really too high?

    You probably didn't look at the code. The MII registers are not
    exposed in the PCI space, they need to be accessed through a serial
    protocol, such that each MII register read is in fact about 200 (in
    total) of outw and inw/inl operations.

    -- 
    Bogdan Costescu
    IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
    Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
    Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
    E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De
    -
    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: Jan Beulich: "Re: [PATCH] new kallsyms approach"

    Relevant Pages

    • Re: [PATCH] 3c59x: read current link status from phy
      ... register twice in all cases, ... interrupt whenever the link changes, which can be used instead of ... Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: is killing zombies possible w/o a reboot?
      ... An interrupt could be received at any time, ... in uninterruptible state because it is uninterruptible ... Processes must never get stuck in D, it's a kernel bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test7-mm1
      ... >> handlers happens to start a thread, ... Problem is, things like bus resets happen in interrupt, and while I can ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: CONFIG_IRQBALANCE for AMD64?
      ... Provide some sort of cache-affinity for network interrupt processing, ... Utilize idle CPUs where possible to shoulder the load. ... I'll confess to not having looked at non-i386 arches. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.28-1
      ... >with our inhouse java project under a Blackdown 1.4 jdk. ... get to a con, I'm sure it does, because hitting the keys generates an interrupt ... then try hitting Sysrq+T when it hangs. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)