PCI Bus haze

01000101 · Post by **01000101** » Wed Aug 01, 2007 12:56 am

I just finished writing a successful PCI device enumerator with a working byte/word/dword configuration space reader.

I also have the prototypes for the configuration space writer, but I'm at a point where I have no clue what to do TO the config space. I guess I am just generally confused from the PCIbus->PCIdevice concept.

If someone could point me in the right direction for reading or give me a basic rundown of what to do next to aid me in the process of communicating with my network controller, that would be much appreciated.

oh, also, come to think about it, that is the one thing that my OS wont detect on the PCIbus. It reads me Nvidia card and my normal ISA controller and such, but not my ethernet card.

Brynet-Inc · Post by **Brynet-Inc** » Wed Aug 01, 2007 2:58 am

Perhaps you have more then one PCI bus

01000101 · Post by **01000101** » Thu Aug 02, 2007 9:35 pm

I have come to the conclusion that the PCI ethernet cards can only be detected (for me atleast) if they have an rj-45 connected to them on system bootup. Strange, but after I plugged the eth-line into the card, rebooted, and my os detected the card right off.

pcmattman · Post by **pcmattman** » Fri Aug 03, 2007 12:03 am

I found the same thing with my NE2000 card... I wonder why this is so?

Dex · Post by **Dex** » Fri Aug 03, 2007 10:01 am

I have never had this problem, and are detected with or without rj-45 plug in.
Are you scaning for device types (class etc ) or are you testing for Vendor/device ID ?.

01000101 · Post by **01000101** » Fri Aug 03, 2007 1:18 pm

eureka.
that was it.
I scanned for the maj/min id instead of the returned class codes and was able to find the eth cards in my device list. The class codes only returned a successful byte when the rj-45 was connected, but the id returned successful either way.