This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83640/DP83630 configuration with kernel device tree

Other Parts Discussed in Thread: DP83640, DP83630

Hi,

Anyone ever configured DP83630 (DP83640) with device tree file (.dts).   i use Atmel SAM9X25 CPU.

Thanks a lot

Kevin

  • Kevin,

    We will check to see if we have any applications with device tree file (.dts) configuration and/or operation with the Atmel SAM9X25 CPU.

    Patrick
  • Thanks Patrick. any .dts example for DP83630/DP83640 related with AT91, or even other CPU is ok. there used to have a patch for Linux Documentation/devicetree/bindings/net/dp83640.txt (e.g., http://lkml.iu.edu/hypermail/linux/kernel/1402.1/02085.html), but never been officially patched to kernel. hence don't know for whether it actually works or not.
    Kevin
  • Hi Patrick,

    My situation is similar with http://www.at91.com/discussions/viewtopic.php/t,23523.html

    i used Atmel MACB interface with d83640.c for PHY layer. i can see these out:
    macb f802c000.ethernet (unregistered net_device): invalid hw address, using random
    libphy: MACB_mii_bus: probed
    macb f802c000.ethernet eth0: Cadence rev 0x0001010c
    macb f802c000.ethernet eth0: Cadence MACB at 0xf802c000 irq 28 (ce:a6:e5:67:12:cb)
    macb f802c000.ethernet eth0: attached PHY driver [NatSemi DP83640] (mii_bus:phy_addr=f802c000.etherne:01, irq=-1)

    from above link, it sounds that i am lack of initialization similar with ksz9021_config_init (for ksz9021). do you know any patch that i can apply with dp83640.c to pick up correct configuration?

    Thanks,

    Kevin