Re: how to identify a PHY?
0n Mon, May 12, 2008 at 01:19:58PM +0200, Marius Strobl wrote: If the system is running the simplest thing in order to identifiy the PHYs is to check the oui= and model= output of `devinfo -v`. Otherwise boot verbose and check the OUI and model output of ukphy(4). Curious, once we have the hex codes for the oui and model e.g. brgphy0 pnpinfo oui=0x818 model=0x1a rev=0x2 at phyno=1 How do we then determine what 0x818 and 0x1a refer to ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
how to identify a PHY?
Hi! From the bugbusting front, I'm often seeing network related issues with unknown (new) PHYs. Can please somebody explain me how one is able to identify what kind of PHY interface is build into a system? Does pciconf output provide some piece of information which leads into getting PHY information? I need to know that to work with the submitter and get their interfaces running (or retrieve information for you to work on). Thanks! Volker ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to identify a PHY?
On Mon, May 12, 2008 at 12:35:59PM +0200, Volker wrote: Hi! From the bugbusting front, I'm often seeing network related issues with unknown (new) PHYs. Can please somebody explain me how one is able to identify what kind of PHY interface is build into a system? Does pciconf output provide some piece of information which leads into getting PHY information? I need to know that to work with the submitter and get their interfaces running (or retrieve information for you to work on). If the system is running the simplest thing in order to identifiy the PHYs is to check the oui= and model= output of `devinfo -v`. Otherwise boot verbose and check the OUI and model output of ukphy(4). Marius ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to identify a PHY?
On 05/12/08 13:19, Marius Strobl wrote: On Mon, May 12, 2008 at 12:35:59PM +0200, Volker wrote: Hi! From the bugbusting front, I'm often seeing network related issues with unknown (new) PHYs. Can please somebody explain me how one is able to identify what kind of PHY interface is build into a system? Does pciconf output provide some piece of information which leads into getting PHY information? I need to know that to work with the submitter and get their interfaces running (or retrieve information for you to work on). If the system is running the simplest thing in order to identifiy the PHYs is to check the oui= and model= output of `devinfo -v`. Otherwise boot verbose and check the OUI and model output of ukphy(4). Marius, thanks for your answer. As far as I understand, the devinfo output will only contain useful information if a driver attaches to the phy. Sometimes a new mainboard hits the market and the ID of the phy's chip is unknown the FreeBSD. If a submitter files a PR and no phy driver attaches, I would like to check if the chip ID is currently known to the system. So I need to know a way to check the ID of a chip without a driver being attached. In short my original question better reads as how do I know the kind of phy if no driver has been attached. Can one retrieve that information out of a verbose boot dmesg (from probing messages)? I would like to first check if a PR might be related to a phy problem at all and if it's just coming with an ID currently unknown to FreeBSD to prepare the PR into a state containing every piece of information needed to have the net-team working easily on it. Thanks Volker ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to identify a PHY?
Marius Strobl wrote: If the system is running the simplest thing in order to identifiy the PHYs is to check the oui= and model= output of `devinfo -v`. Otherwise boot verbose and check the OUI and model output of ukphy(4). There's a project for someone in there I'm sure. Linux has mii-tool and mii-diag. Whilst we generally don't need all of the knobs, sometimes it can be useful to dump and poke PHY registers on the MII. src/sys/dev/mii/miibus_if.m contains the newbus interface definition for miibus which would be a place to start. cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to identify a PHY?
Volker wrote: ... In short my original question better reads as how do I know the kind of phy if no driver has been attached. Can one retrieve that information out of a verbose boot dmesg (from probing messages)? You can't determine which PHY is in use unless a driver is attached, because it's necessary to attach a driver in order to access the card's MII registers. Same with any other OS. If no PHY driver attached, but a NIC driver attached, you should see this message: device_printf(dev, MII without any PHY!\n); It sounds like someone needs to instrument the code path mii_phy_probe() to print useful information in the situation you describe. cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to identify a PHY?
On Mon, May 12, 2008 at 01:55:34PM +0200, Volker wrote: On 05/12/08 13:19, Marius Strobl wrote: On Mon, May 12, 2008 at 12:35:59PM +0200, Volker wrote: Hi! From the bugbusting front, I'm often seeing network related issues with unknown (new) PHYs. Can please somebody explain me how one is able to identify what kind of PHY interface is build into a system? Does pciconf output provide some piece of information which leads into getting PHY information? I need to know that to work with the submitter and get their interfaces running (or retrieve information for you to work on). If the system is running the simplest thing in order to identifiy the PHYs is to check the oui= and model= output of `devinfo -v`. Otherwise boot verbose and check the OUI and model output of ukphy(4). Marius, thanks for your answer. As far as I understand, the devinfo output will only contain useful information if a driver attaches to the phy. Sometimes a new mainboard hits the market and the ID of the phy's chip is unknown the FreeBSD. If a submitter files a PR and no phy driver attaches, I would like to check if the chip ID is currently known to the system. So I need to know a way to check the ID of a chip without a driver being attached. In short my original question better reads as how do I know the kind of phy if no driver has been attached. Can one retrieve that information out of a verbose boot dmesg (from probing messages)? I would like to first check if a PR might be related to a phy problem at all and if it's just coming with an ID currently unknown to FreeBSD to prepare the PR into a state containing every piece of information needed to have the net-team working easily on it. For NIC drivers interfacing with miibus(4) the ukphy(4) driver always matches as a last resort. If even ukphy(4) doesn't attach this means there's a more fundamental problem of some sort with the NIC driver communicating with the MII bus. In that case there's no way to identify which PHYs are on the MII bus (it even doesn't necessarily mean they are unknown to the system.) Marius ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]
