netdev - Re: [PATCH net-next 5/5] ice: Print human-friendly PHY types

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220825200344.32cb445f@kernel.org>
Date:   Thu, 25 Aug 2022 20:03:44 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Tony Nguyen <anthony.l.nguyen@...el.com>
Cc:     davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
        Anirudh Venkataramanan <anirudh.venkataramanan@...el.com>,
        netdev@...r.kernel.org, Lukasz Plachno <lukasz.plachno@...el.com>,
        Alexander Lobakin <alexandr.lobakin@...el.com>,
        Gurucharan <gurucharanx.g@...el.com>
Subject: Re: [PATCH net-next 5/5] ice: Print human-friendly PHY types

On Wed, 24 Aug 2022 10:03:40 -0700 Tony Nguyen wrote:
> Old:
> [  286.130405] ice 0000:16:00.0: get phy caps - report_mode = 0x2
> [  286.130409] ice 0000:16:00.0:        phy_type_low = 0x108021020502000
> [  286.130412] ice 0000:16:00.0:        phy_type_high = 0x0
> [  286.130415] ice 0000:16:00.0:        caps = 0xc8
> [  286.130419] ice 0000:16:00.0:        low_power_ctrl_an = 0x4
> [  286.130421] ice 0000:16:00.0:        eee_cap = 0x0
> [  286.130424] ice 0000:16:00.0:        eeer_value = 0x0
> [  286.130427] ice 0000:16:00.0:        link_fec_options = 0xdf
> [  286.130430] ice 0000:16:00.0:        module_compliance_enforcement = 0x0
> [  286.130433] ice 0000:16:00.0:    extended_compliance_code = 0xb
> [  286.130435] ice 0000:16:00.0:    module_type[0] = 0x11
> [  286.130438] ice 0000:16:00.0:    module_type[1] = 0x1
> [  286.130441] ice 0000:16:00.0:    module_type[2] = 0x0
> 
> New:
> [ 1128.297347] ice 0000:16:00.0: get phy caps dump
> [ 1128.297351] ice 0000:16:00.0: phy_caps_active: phy_type_low: 0x0108021020502000
> [ 1128.297355] ice 0000:16:00.0: phy_caps_active:   bit(13): 10G_SFI_DA
> [ 1128.297359] ice 0000:16:00.0: phy_caps_active:   bit(20): 25GBASE_CR
> [ 1128.297362] ice 0000:16:00.0: phy_caps_active:   bit(22): 25GBASE_CR1
> [ 1128.297365] ice 0000:16:00.0: phy_caps_active:   bit(29): 25G_AUI_C2C
> [ 1128.297368] ice 0000:16:00.0: phy_caps_active:   bit(36): 50GBASE_CR2
> [ 1128.297371] ice 0000:16:00.0: phy_caps_active:   bit(41): 50G_LAUI2
> [ 1128.297374] ice 0000:16:00.0: phy_caps_active:   bit(51): 100GBASE_CR4
> [ 1128.297377] ice 0000:16:00.0: phy_caps_active:   bit(56): 100G_CAUI4
> [ 1128.297380] ice 0000:16:00.0: phy_caps_active: phy_type_high: 0x0000000000000000
> [ 1128.297383] ice 0000:16:00.0: phy_caps_active: report_mode = 0x4
> [ 1128.297386] ice 0000:16:00.0: phy_caps_active: caps = 0xc8
> [ 1128.297389] ice 0000:16:00.0: phy_caps_active: low_power_ctrl_an = 0x4
> [ 1128.297392] ice 0000:16:00.0: phy_caps_active: eee_cap = 0x0
> [ 1128.297394] ice 0000:16:00.0: phy_caps_active: eeer_value = 0x0
> [ 1128.297397] ice 0000:16:00.0: phy_caps_active: link_fec_options = 0xdf
> [ 1128.297400] ice 0000:16:00.0: phy_caps_active: module_compliance_enforcement = 0x0
> [ 1128.297402] ice 0000:16:00.0: phy_caps_active: extended_compliance_code = 0xb
> [ 1128.297405] ice 0000:16:00.0: phy_caps_active: module_type[0] = 0x11
> [ 1128.297408] ice 0000:16:00.0: phy_caps_active: module_type[1] = 0x1
> [ 1128.297411] ice 0000:16:00.0: phy_caps_active: module_type[2] = 0x0

Is this not something that can be read via ethtool -m ?