#tyndur · 2009-11-03
65 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen
- pcmattmankwolf: ping
- kwolfpcmattman: pong
- pcmattmanI'm looking at the CDI e1000 driver at the moment, as it doesn't initialise properly on non-QEMU hosts
- pcmattmanDoes the driver work on anything other than QEMU in tyndur? Should I look at Pedigree's code or the driver code to try and fix it?
- kwolfIt's probably a driver issue
- kwolfI think it was reported to work in some other emulator, but never on real hardware
- kwolfI don't even have one in hardware, unfortunately
- pcmattmanOk, I'll see what I can do in the driver then
- kwolfAre you testing on real hardware?
- pcmattmanNot quite. Trying it in VirtualBox
- kwolfOk
- kwolfSo I should be able to reproduce it
- pcmattmanHopefully, yes
- kwolfMaybe you can tell me your finding before you leave tonight so I can have a look later
- pcmattmanIt actually appears to be a simple fix
- kwolfOh, already found it?
- pcmattmanhttp://slexy.org/view/s214Dqk530
- pcmattmanThat's the modified e1000_eeprom_read that is quite successful
- pcmattmanWith that modification I now successfully browse to Google using the driver
- kwolfHm... So you're actually failing the read or is it the sleep that makes it work?
- pcmattmanThe original code ran this in a tight loop
- kwolfI saw that, yes
- pcmattmanTo my understanding the 50 ms delay is enough for the card to complete the command
- kwolfStill don't understand why it wouldn't complete the command in a tight loop
- pcmattmanIt may well be that it's actually breaking out of the loop
- pcmattmanWhich would make sense, if it's persistently failing, it'll break out
- kwolfWhich means that you would return 0 instead of the right value
- pcmattmanBack to the drawing board :)
- pcmattmanYup
- kwolfThere is even the right printf in your code to check what happens
- pcmattmanIt looks like it's returning 0
- kwolfHm, 00:00:00:00:00:00 isn't really a desirable MAC address...
- pcmattmanYup
- pcmattmanIt seems other drivers attempt the EERD read and then if that fails attempt what looks like a "uwire" read
- kwolfMaybe the VBox e1000 doesn't even support this EEPROM interface? I think there is a second one
- kwolfA more complicated one which doesn't just involve reading out a register
- pcmattmanYup
- pcmattmanI'm going to try and obtain the specification and try and make sense of some driver code and see if I can port it across
- kwolfWhich is why I didn't bother to implement it ;-)
- kwolfThe e1000 sourceforge project has the spec, iirc
- pcmattmanThe question is though, which spec? :)
- kwolfIf in doubt, take the right one :-)
- pcmattmanComplex protocol
- kwolfFor EEPROM access?
- pcmattmanEERD (which is what the current driver uses) is dead easy
- pcmattmanThe 4-wire interface is a whole new story
- pcmattmanI'll be sure to submit a patch when I'm done :)
- kwolfGuess why I did it the EERD way...
- pcmattmanI do have e1000 driver code to refer to, thankfully
- kwolfAppropriately licensed code, I hope?
- pcmattmanYup, although the key word is "refer"
- pcmattmanAs far as I know the algorithm can't be protected by a license because it's a driver: the algorithm is defined by the specification
- kwolfI'm actually careful with even looking at Linux code
- kwolfSure
- kwolfafk lunch
- kwolfback
- pcmattmanWelcome back
- kwolfThanks
- kwolfWhat's the EEPROM doing?
- pcmattmanStill perusing code and the specification
- kwolfStill? This method sounds really tedious
- pcmattmanI just want to make sure I understand what I'm doing
- kwolfRight, it helps sometimes
- pcmattmanNight
- kwolfNight pc[away]