I've been given a webpage to help add some more up-to-date information. I decided to check it out, since it's usually a good idea to know what you'll have to work with.

The page is so horribly broken it's not just an Explorer-specific page, it's an IE5-specific page. It looks very weird under Firefox, so I decided to use IE on the other computer to check what it's actually supposed to look like. Oh, the horror!

On IE6, the different parts of the page are on top of each other, and the footer's in there mangling up all the actual information. There's no way to get anything useful out of it.

I'm not going to rest easy until I manage to get this in working order, but I've never been good with webpages, specially the design part. I suppose a working page would be better than this, even if it doesn't look as good (as the other is does under IE5).

At least a bit, anyway. Thanks to a combination of ndiswrapper, qemu, pciproxy and sigirq, I now have a log of the conversation between the driver and the device. I have come to the conclusion that the driver is crazy. There are double reads and writes everywhere.

I think in a couple of days I'll be able to get the MAC address off the device in a few reads. Right now I'm doing many more than I need to, because I'm doing what the Windows driver does.

I tried putting debug statements on the WRITE_REGISTER_ULONG() and friends functions in ndisrapper, but as it turns out, the amd64 driver only uses MMIO, so those functions are never called. The problem is that ndiswrapper can't properly configure the device from inside qemu, so I can't do a proper reverse-engineer that way. I'll have to think some other way.