ethernet.txt 2.1 KB

1234567891011121314151617181920212223242526272829303132333435
  1. The following properties are common to the Ethernet controllers:
  2. - local-mac-address: array of 6 bytes, specifies the MAC address that was
  3. assigned to the network device;
  4. - mac-address: array of 6 bytes, specifies the MAC address that was last used by
  5. the boot program; should be used in cases where the MAC address assigned to
  6. the device by the boot program is different from the "local-mac-address"
  7. property;
  8. - max-speed: number, specifies maximum speed in Mbit/s supported by the device;
  9. - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than
  10. the maximum frame size (there's contradiction in ePAPR).
  11. - phy-mode: string, operation mode of the PHY interface; supported values are
  12. "mii", "gmii", "sgmii", "qsgmii", "tbi", "rev-mii", "rmii", "rgmii", "rgmii-id",
  13. "rgmii-rxid", "rgmii-txid", "rtbi", "smii", "xgmii"; this is now a de-facto
  14. standard property;
  15. - phy-connection-type: the same as "phy-mode" property but described in ePAPR;
  16. - phy-handle: phandle, specifies a reference to a node representing a PHY
  17. device; this property is described in ePAPR and so preferred;
  18. - phy: the same as "phy-handle" property, not recommended for new bindings.
  19. - phy-device: the same as "phy-handle" property, not recommended for new
  20. bindings.
  21. - rx-fifo-depth: the size of the controller's receive fifo in bytes. This
  22. is used for components that can have configurable receive fifo sizes,
  23. and is useful for determining certain configuration settings such as
  24. flow control thresholds.
  25. - tx-fifo-depth: the size of the controller's transmit fifo in bytes. This
  26. is used for components that can have configurable fifo sizes.
  27. - managed: string, specifies the PHY management type. Supported values are:
  28. "auto", "in-band-status". "auto" is the default, it usess MDIO for
  29. management if fixed-link is not specified.
  30. Child nodes of the Ethernet controller are typically the individual PHY devices
  31. connected via the MDIO bus (sometimes the MDIO bus controller is separate).
  32. They are described in the phy.txt file in this same directory.
  33. For non-MDIO PHY management see fixed-link.txt.