====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
soc:2011:meteger:journal:week3 [2011/06/06 11:59]
meteger created 		soc:2011:meteger:journal:week3 [2011/06/12 08:01] (current)
meteger
Line 5: Line 5:
 Some initialization for LED control was removed, while other parts were only adapted to work with gPXE instead of linux API functions. Some initialization for LED control was removed, while other parts were only adapted to work with gPXE instead of linux API functions.
 There is still some work to do to get tg3_init_one() finished but hopefully it won't take too long. There is still some work to do to get tg3_init_one() finished but hopefully it won't take too long.
 +
 +====== Day 2 ( June 7 ) ======
 +
 +Continued porting with some PHY init functions, including functions to access the PHY register, to probe the PHY and to detect the PHY ID.
 +
 +====== Day 3 ( June 8 ) ======
 +
 +Added the rest of the PHY functions. Hopefully we can reduce the code for the PHY init. Might have a look at the freebsd driver again, which seems to achieve the same thing with much fewer code.
 +
 +====== Day 4 ( June 9 ) ======
 +
 +Ported the nvram access, chip reset, firmware communication,​ mac address reading/​programming and all the other functions that were missing for tg3_init_one().
 +This is the first version that compiles without any errors and the first version that can be sensible tested on real hardware. After a small fixup of the PHY probe/init functions the driver succeeded in reading the MAC address and registering the network device.
 +
 +====== Day 5 ( June 10 ) ======
 +
 +Started porting the hardware reset/init functions that we will need in tg3_open().
 +Hopefully tg3_reset_hw() doesn'​t turn out to be too long in gPXE, as the linux function is almost 1000 LoC.
 +

Trace:

QR Code
QR Code soc:2011:meteger:journal:week3 (generated for current page)