Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
soc:2010:andreif:journal:week3 [2010/06/12 12:15]
andreif
soc:2010:andreif:journal:week3 [2010/06/13 13:58]
andreif
Line 47: Line 47:
 Anyway, I'm determined to post a patch containing the driver tomorrow, even though it still has problems. I don't expect this to be accepted, Anyway, I'm determined to post a patch containing the driver tomorrow, even though it still has problems. I don't expect this to be accepted,
 the purpose is to expose it to more experienced eyes. Finally, I'll shoot an email to some of the forcedeth driver devs tomorrow regarding the docs. the purpose is to expose it to more experienced eyes. Finally, I'll shoot an email to some of the forcedeth driver devs tomorrow regarding the docs.
 +
 +==== Day 7 [ 13 Jun 2010 ] ====
 +
 +Git commit: [[http://​git.etherboot.org/?​p=people/​andreif/​gpxe.git;​a=commit;​h=5a3434ce23f524788d5eb9959628cfa1789f687b|5a3434ce23f524788d5eb9959628cfa1789f687b]]
 +
 +Well, today was full of gpxe-esque events :). Meteger managed to trace a bug that was causing pxelinux.0 to fail booting an Ubuntu image. I managed to mix the buffer length and the length of the received message so the iobuf didn't get trimmed to the proper size which I suspect
 +caused some bad data to be received.
 +
 +The weekly meeting went well too, and it is a real pleasure to debug stuff together with other people. I have a lot of work to do on my debugging skills but luckily I have awesome people to learn from.
 +
 +Like I've planned, I sent a patch containing the driver. I usually formatted small, one-commit patches, using ''​git-format-patch''​ so I wasn't sure what to do with the driver since it had multiple commits. Stefanha guided me towards ''​git-send-email''​ and ''​git-rebase''​ which successfully got the patch sent. Unfortunately,​ it isn't properly formatted since the diff between the old driver and the new one makes it hard to read. So the patch sending wasn't what I call a successful attempt, but the things that are learned the hard way are best remembered.
 +
 +I've also sent an email to one of the forcedeth driver devs to see if he can part with the documentation. Regardless, I'll start working on the driver since I feel that I have gained a sufficient amount of insight into driver writing to understand the forcedeth driver only from its source code. Tomorrow I'll start working on .probe.
 +

QR Code
QR Code soc:2010:andreif:journal:week3 (generated for current page)