Help - Search - Members - Calendar
Full Version: Marvell 8040 has two DeviceID???
Project OS X Forums > Previous Releases > Mac OS X Leopard 10.5 > OS X 10.5 (Leopard) > Hardware Discussion > Network
Slice
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.
Krazubu
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
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.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.