#tyndur · 2010-03-10
25 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen
- kwolfHey pcmattman
- kwolfYou got e1000 to work in VBox now? :-)
- pcmattmanSeems to work
- pcmattmanPatches coming your way either tonight or tomorrow night
- kwolfSounds good
- pcmattmanI'm just trying to get VMWare working so I can test it in another high quality emulator
- kwolfSo what did you change? Completely new EEPROM code?
- pcmattmanPedigree's ATA driver doesn't work properly in it, see
- pcmattmanBasically added the microwire interface for the e1000 and used it as a fallback when the EERD method fails
- kwolfCan you detect EERD failure or do we need to decide using the revision ID or something like that?
- kwolfHm, ATA drivers... Ours causes an assert() to fail in VBox...
- pcmattmanBasically, I try to read the EERD 100 times, and if that fails it gets flagged as unavailable
- pcmattmanThere are some E1000 cards which don't actually support the EERD interface, but the driver itself isn't aware of the numerous different e1000 chips so I thought I'd leave that out for now
- kwolfI'll look up the details in the code then
- kwolfYes, we would need huge tables to make it aware of them. Not sure if it's worth it if it's only about the EEPROM for now
- pcmattmanWell, I do have a "TODO: be chipset aware" as one part of my code is only valid on post-82544 chips
- pcmattmanI don't feel like making the driver multi-chip aware yet though
- pcmattmanI'd like to get pcnet working nicely in VBox and VMWare before I even think about doing such a thing
- kwolfThe pcnet driver is a bit... different anyway
- kwolfWould be nice if it could be made to look more like the other drivers in the process
- kwolfI noticed that each time when I had to do some refactoring after interface changes. Almost all drivers were straightforward to change, but not pcnet.
- pcmattmanI haven't seen the code for pcnet at all yet
- pcmattmanI'm fearful now :)
- kwolf_pcmattman: It's what happens when you give commit rights to bluecode ;-)
- pcmattmanHahaha