----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/1586/#review3749 -----------------------------------------------------------
src/dev/ns_gige.cc <http://reviews.gem5.org/r/1586/#comment3669> I don't think this is the right answer. If you want to get rid of the zero clock (which disables clocking), add a flag to disable clocking and make it the default. - Nathan Binkert On Dec. 6, 2012, 8:26 p.m., Andreas Hansson wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1586/ > ----------------------------------------------------------- > > (Updated Dec. 6, 2012, 8:26 p.m.) > > > Review request for Default. > > > Description > ------- > > Changeset 9387:9d75feaa7b50 > --------------------------- > dev: Make the ethernet devices use a non-zero clock > > This patch changes the NS gige controller to have a non-clock, and > sets the default to 500 MHz. The blocks that could prevoiusly be > by-passed with a zero clock are now always present, and the user is > left with the option of setting a very high clock frequency to achieve > a similar performance. > > > Diffs > ----- > > src/dev/Ethernet.py 844f9e724343 > src/dev/ns_gige.cc 844f9e724343 > src/dev/sinic.cc 844f9e724343 > > Diff: http://reviews.gem5.org/r/1586/diff/ > > > Testing > ------- > > util/regress all passing (disregarding t1000 and eio) > > > Thanks, > > Andreas Hansson > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
