#
d6b69283 |
| 19-Nov-2024 |
Mark Johnston <markj@FreeBSD.org> |
mii_fdt: Search for the "ethernet-ports" subnode
This is a more common name for the parent of the port nodes.
PR: 280770 MFC after: 2 weeks Reported by: Mike Belanger <mibelanger@qnx.com>
|
Revision tags: release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0 |
|
#
685dc743 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0 |
|
#
3e38757d |
| 19-Apr-2022 |
John Baldwin <jhb@FreeBSD.org> |
Remove unused miibus_devclass and miibus_fdt_devclass.
|
#
823b5cfb |
| 30-Mar-2022 |
Mitchell Horne <mhorne@FreeBSD.org> |
mii_fdt: fix a set-but-not-used warning
|
#
206dc82b |
| 25-Jan-2022 |
Kornel Duleba <mindal@semihalf.com> |
bus_if: Add a default implementation of get_property
There are multiple buses that pretend to be ofw compatible, e.g ofw_pci, mii_fdt. We now need to provide an implementation of BUS_GET_PROPERTY fo
bus_if: Add a default implementation of get_property
There are multiple buses that pretend to be ofw compatible, e.g ofw_pci, mii_fdt. We now need to provide an implementation of BUS_GET_PROPERTY for every one of them. Instead of modifying them one by one it's better to just provide a default implementation that simply traverses up the device tree. Remove the now unneeded BUS_GET_PROPERTY implementation in mii_fdt.
Reviewed by: andrew, bz Obtained from: Semihalf MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D34031
show more ...
|
Revision tags: release/12.3.0 |
|
#
9174eab4 |
| 15-Nov-2021 |
Kornel Duleba <mindal@semihalf.com> |
miibus: Add support for mapping OFW nodes to PHY devices
Create a new miibus OFW specific layer leveraging miibus_fdt.c code. PHY drivers can than read the properties using device_get_property(9) AP
miibus: Add support for mapping OFW nodes to PHY devices
Create a new miibus OFW specific layer leveraging miibus_fdt.c code. PHY drivers can than read the properties using device_get_property(9) API. Resource(interrupt) allocation is also supported. In order to enable this each NIC/switch driver will have to be modified, because of how miibus is attached to the parent driver.
Obtained from: Semihalf Sponsored by: Alstom Group Differential revision: https://reviews.freebsd.org/D32812
show more ...
|
#
4b843e7f |
| 27-Oct-2021 |
Kornel Duleba <mindal@semihalf.com> |
mii_fdt: Add support for switch PHY node lookup
Previously we would only search for a PHY xref in node of the miibus parent. That didn't work very well with switches. Fix that by searching through "
mii_fdt: Add support for switch PHY node lookup
Previously we would only search for a PHY xref in node of the miibus parent. That didn't work very well with switches. Fix that by searching through "ports" subnode, checking if any of its children have a valid PHY xref. Since switches tend to have multiple ports we also have multiple candidates. Use the PHY address read from mii_attach_args to find the right one.
Obtained from: Semihalf Sponsored by: Alstom Group Reviewed by: mw Differential revision: https://reviews.freebsd.org/D32690
show more ...
|
Revision tags: release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0 |
|
#
4198293b |
| 17-Jun-2017 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r319801 through r320041.
|
#
7f153db8 |
| 11-Jun-2017 |
Ian Lepore <ian@FreeBSD.org> |
Add some utility functions to help a PHY driver on an FDT-configured system retrieve its config data from the fdt data.
The properties that are common to all phys are decoded and returned in a struc
Add some utility functions to help a PHY driver on an FDT-configured system retrieve its config data from the fdt data.
The properties that are common to all phys are decoded and returned in a structure. The fdt node handles for the mac and phy devices are also returned in the config data struct, so a driver can easily obtain additional hardware-specific config values from the fdt data.
show more ...
|