ProjectOSX

Welcome Guest!

Returning User? Login here.

Want membership privileges? Register here.

 
Start a new topic Add Reply
> Marvell 8040 has two DeviceID???
Slice
post Aug 21 2009, 11:16 AM
Post #1
In different changes of my /S/L/E I got different rezults about my Marvell 8040
CODE
| | | +-o GIGE@0 <class IOPCIDevice, registered, matched, active, busy 0, retain 10>
| | | | {
| | | | "IOPCIResourced" = Yes
| | | | "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController")
| | | | "IOName" = "ethernet"
| | | | "subsystem-id" = <2f020000>
| | | | "IODeviceMemory" = (({"address"=18446744073685417984,"length"=16384}),{"parent"=({"address"=0,"length"=65536}),"offset"=56832,"length"=256})
| | | | "class-code" = <00000200>
| | | | "revision-id" = <12000000>
| | | | "model" = "Marvell Yukon Gigabit Adapter 88E804Z Singleport Copper SA"
| | | | "built-in" = <00>
| | | | "assigned-addresses" = <100009820000000000c08ffe0000000000400000180009810000000000de00000000000000010
000>
| | | | "acpi-device" = "IOACPIPlatformDevice is not serializable"
| | | | "IOChildIndex" = 1
| | | | "name" = "ethernet"
| | | | "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/RP01@1c0000/GIGE@0"
| | | | "subsystem-vendor-id" = <28100000>
| | | | "reg" = <00000900000000000000000000000000000000001000090200000000000000000000000000400
0001800090100000000000000000000000000010000>
| | | | "compatible" = <"pci1028,22f","pci11ab,4354","pciclass,020000">
| | | | "IOPCIExpressLinkCapabilities" = 502801
| | | | "AAPL,slot-name" = <"PCMCIA 0">
| | | | "IOPowerManagement" = {"ChildrenPowerState"=2,"CurrentPowerState"=2}
| | | | "IOInterruptSpecifiers" = (<1000000007000000>,<0800000000000100>)
| | | | "IOPCIMSIMode" = Yes
| | | | "device-id" = <54430000>
| | | | "vendor-id" = <ab110000>
| | | | "IOPCIExpressLinkStatus" = 4113
| | | | "IOPCIExpressASPMDefault" = 1
| | | | }

And sometimes
CODE
| | | +-o GIGE@0 <class IOPCIDevice, registered, matched, active, busy 0, retain 10>
| | | | {
| | | | "IOPCIResourced" = Yes
| | | | "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController")
| | | | "IOName" = "ethernet"
| | | | "subsystem-id" = <ba000000>
| | | | "IODeviceMemory" = (({"address"=18446744073685417984,"length"=16384}),{"parent"=({"address"=0,"length"=65536}),"offset"=56832,"length"=256})
| | | | "class-code" = <00000200>
| | | | "revision-id" = <12000000>
| | | | "model" = "Marvell Yukon Gigabit Adapter 88E804Y Singleport Copper SA"
| | | | "built-in" = <00>
| | | | "assigned-addresses" = <100009820000000000c08ffe0000000000400000180009810000000000de00000000000000010
000>
| | | | "acpi-device" = "IOACPIPlatformDevice is not serializable"
| | | | "IOChildIndex" = 1
| | | | "name" = "ethernet"
| | | | "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/RP01@1c0000/GIGE@0"
| | | | "subsystem-vendor-id" = <ab110000>
| | | | "reg" = <00000900000000000000000000000000000000001000090200000000000000000000000000400
0001800090100000000000000000000000000010000>
| | | | "compatible" = <"pci11ab,ba","pci11ab,435a","pciclass,020000">
| | | | "IOPCIExpressLinkCapabilities" = 502801
| | | | "AAPL,slot-name" = <"PCMCIA 0">
| | | | "IOPowerManagement" = {"ChildrenPowerState"=2,"CurrentPowerState"=2}
| | | | "IOInterruptSpecifiers" = (<1000000007000000>,<0800000000000100>)
| | | | "IOPCIMSIMode" = Yes
| | | | "device-id" = <5a430000>
| | | | "vendor-id" = <ab110000>
| | | | "IOPCIExpressLinkStatus" = 4113
| | | | "IOPCIExpressASPMDefault" = 3
| | | | }
| | | |

In both cases adapter works fine.
i3-2120 GA-H61M-S1 UEFI, Radeon HD6670-UEFI, ALC887(VoodooHDA 2.8.6), OS⌘10.9.4, OS⌘ 10.7.5 Clover FakeSMC_plugins_3.3.1 Realtek LAN v3.1.2
Krazubu
post Jan 5 2010, 10:27 AM
Post #2
Rather old post but I just saw it.
That device ID is just an hardcoded string telling the model name, which is not necessarily the right one but just what the driver "believes". So maybe each kext detects it as a different subversion with minor changes of the device, both working the same way.
Slice
post Jan 5 2010, 02:11 PM
Post #3
QUOTE (Krazubu @ Jan 5 2010, 02:27 PM) *
Rather old post but I just saw it.
That device ID is just an hardcoded string telling the model name, which is not necessarily the right one but just what the driver "believes". So maybe each kext detects it as a different subversion with minor changes of the device, both working the same way.

The kext is the same in both cases. I found that when LAN is connected then DeviceID=435a, if not connected then DeviceID=4354. It is strange but not terrible.
i3-2120 GA-H61M-S1 UEFI, Radeon HD6670-UEFI, ALC887(VoodooHDA 2.8.6), OS⌘10.9.4, OS⌘ 10.7.5 Clover FakeSMC_plugins_3.3.1 Realtek LAN v3.1.2

Add Reply Start a new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: