Re: [PATCH] igb: Explicitly select page 0 at initialization

2016-11-24 Thread Sergei Shtylyov
Hello. On 11/24/2016 1:32 PM, Matwey V. Kornilov wrote: The functions igb_read_phy_reg_gs40g/igb_write_phy_reg_gs40g (which were removed in 2a3cdea) explicitly selected the required page at every phy_reg This is not the way to cite a commit -- you need to specify at least 12 digits and

Re: [PATCH] igb: Explicitly select page 0 at initialization

2016-11-24 Thread Sergei Shtylyov
Hello. On 11/24/2016 1:32 PM, Matwey V. Kornilov wrote: The functions igb_read_phy_reg_gs40g/igb_write_phy_reg_gs40g (which were removed in 2a3cdea) explicitly selected the required page at every phy_reg This is not the way to cite a commit -- you need to specify at least 12 digits and

[PATCH] igb: Explicitly select page 0 at initialization

2016-11-24 Thread Matwey V. Kornilov
The functions igb_read_phy_reg_gs40g/igb_write_phy_reg_gs40g (which were removed in 2a3cdea) explicitly selected the required page at every phy_reg access. Currently, igb_get_phy_id_82575 relays on the fact that page 0 is already selected. The assumption is not fulfilled for my Lex 3I380CW

[PATCH] igb: Explicitly select page 0 at initialization

2016-11-24 Thread Matwey V. Kornilov
The functions igb_read_phy_reg_gs40g/igb_write_phy_reg_gs40g (which were removed in 2a3cdea) explicitly selected the required page at every phy_reg access. Currently, igb_get_phy_id_82575 relays on the fact that page 0 is already selected. The assumption is not fulfilled for my Lex 3I380CW