**This is an old revision of the document!** ----

====== Michael Decker: Driver Development ====== ==== Week 6 ==== ---- === 2 July === Today, I'll be doing some testing with the eepro100. I've been using one PCI card for testing thus far, so I'll toss in another and run more tests. Testing revealed a problem on the 82559. A series of TX overflows occurred. Testing with the original legacy driver did not show this behavior, so faulty hardware is not likely the root cause. === 3 July === * [[http://git.etherboot.org/?p=people/mdeck/gpxe.git;a=commitdiff;h=e3e6088d3d237676df2be83057ef97ddccffa50a|Ooops where'd the commit title go?]] The open() routine, which performs two commands, ias and config, was modified. It was changed to match the behavior of the legacy driver. That is, the ias command links into the config command, which then suspends the device. One start command is issued which executes both commands in sequence. Additionally, I ensured the configure command is aligned to a physical even address by allocating it through ''malloc_dma()''. The allocation & initialization of the ias command was moved to just precede the configure command, as they are now executed together. Also, I added in the legacy code which tests if the device is plugged in. The result of this test calls either ''netdev_link_up()'' or ''netdev_link_down()''. The 82559 now appears to operate properly under normal conditions. However, I still have a problem if I boot the system with both cards, and the first card fails to boot. The second card causes a triple fault around when the http get is being performed. I haven't tested the legacy driver in such a double-booting situation, so I'm not sure if there are any special hardware issues to consider in this setup.