On Tue, Mar 20, 2018 at 10:59 AM, James Courtier-Dutton <james.dut...@gmail.com> wrote: > On Mon, 19 Mar 2018, 21:11 Ran Shalit, <ransha...@gmail.com> wrote: >> >> On Mon, Mar 19, 2018 at 10:23 PM, Alexander Duyck >> <alexander.du...@gmail.com> wrote: >> > On Mon, Mar 19, 2018 at 12:31 PM, Ran Shalit <ransha...@gmail.com> >> > wrote: >> >> On Mon, Mar 19, 2018 at 6:27 PM, Alexander Duyck >> >> <alexander.du...@gmail.com> wrote: >> >>> On Mon, Mar 19, 2018 at 9:07 AM, Ran Shalit <ransha...@gmail.com> >> >>> wrote: >> >>>> Hello, >> >>>> >> >> >> I tried many trials, but I always got the phy led turned off, and then >> turned on, no matter what I did. >> I would also add that my actual goal is to minimize the initialization >> time of the igb, because we need fast boot time. >> >> > Hi, > > You will find that the NIC is initialized quite late in the boot process. > I think that is likely to be the problem here. > If you enable the NIC with netconsole, it will initialize much earlier in > the boot process. > You could give that a try, if it solves the boot time problem, you can then > look at how netconsole works, and just implement the initialization of the > NIC card, without sending console messages to the network. > > Kind Regards > > James > > >
I will try that. Yet, I just tried now to disable again reset phy in igb_main.c: igb_power_up_link -> comment out igb_reset_phy and in e1000_phy,.c retun from igb_phy_sw_reset and also from igb_phy_hw_reset. Yet, it still reset phy.... Is there any idea why ? Thank you, ran ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
