1) April 18, 2013  2) 3 days 3) MC3190 4) WM6.5 BSP41 and 37 5) Case #2822818

we received the following request from TA , any comments why the bahvior was changed with latest new chip ethernet cradles drivers ? ------------------------------ Dear Emaea Tech Team,

I am facing an issue with our MC3190Z, here first are some facts:

End customer              C&A Germany partner & integrator     Checkpoint Systems product                        MC3190Z, WM 6.5 OS 04.41.0004 (Sony Display Release) cradle                          PortSmith Single Slot Ethernet Cradle

The customer is using Cisco series 2960 LAN switches and is allowing a MTU size of 1500 bytes.

The PortSmith single slot ethernet cradle is using the same SMSC9500 chip we are using in our new 4 slot ethernet cradles.

Scenario 1 -               MC3190Z with PortSmith cradle -               no additional SMSC9500 driver, so using the builtin driver of the OS -             no Jumbo/Giant Ethernet packets above the MTU of 1500 bytes are seen on their LAN

Scenario 2 -               MC3190Z with PortSmith cradle -               additional Motorola Universal SMSC9500 driver via CAB installed -              Jumbo/Giant Ethernet packets above the MTU of 1500 bytes are seen on their LAN

Scenario 3 -               MC3190Z with PortSmith cradle -               additional Motorola Universal SMSC9500 driver via CAB installed -               configuring max MTU size of 1500 in the MC3190Z WM OS via registry

[HKEY_LOCAL_MACHINE\Comm\SMSC95001\Parms\TcpIp] "MTU"=dword:000005DC

-             no Jumbo/Giant Ethernet packets above the MTU of 1500 bytes are seen on their LAN

I did not find any (documented) entry in the REG file of our SMSC9500 driver to suppress using Jumbo/Giant packets. It looks like our driver version is activating this feature in combination with the SMSC in the PortSmith cradle by default. The older driver version in our 04.41.0004 is not activating (or not supporting) this feature by default.

I did found new registry entries in the live registry of the device, when the driver was loaded and the SMSC hardware was active:

[HKEY_LOCAL_MACHINE\Comm\SMSC95001\Parms] "PriorityVlanTag"=dword:00000000 "VlanID"=dword:00000000 "RxBurstCap"=dword:00002000 "RxBurstMax"=dword:00002000 "LowWatermarkRCBs"=dword:00000002 "MaxRCBs"=dword:00000004 "TxBurstMax"=dword:00002000 "MaxTCBs"=dword:00000004 "FlowControl"=dword:00000001 "CustomCapa"=dword:000001E0 "MediaType"=dword:00000000 "PhyAddress"=dword:00000001 "BusType"=dword:00000000 "BusNumber"=dword:00000000

For my customer I did now find a workaround, but we should be very careful about the different behavior of the driver versions.

My question is now: Can we get an information and a registry key from SMSC on how to have the Jumbo/Giant Ethernet package support disabled? Jurgen ----------------------- Many thanks Riad