SMC1244 and SMC1255 NIC on 6.2

Hi, has anyone used these two NICs before? Are they supported in 6.2?

When I run pci -v on SMC1244, it shows:
Class = Network (Ethernet)
Vendor ID = 1317h, Admtek Inc
Device ID = 985h, ADM983 fast ethernet
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 1113h
Subsystem ID = ec02h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

When I run pci -v on SMC1255, it shows:
Class = Network (Ethernet)
Vendor ID = 1113h, Accton Technology Corporation
Device ID = 1216h, EN2242 Accton EN2242 PCI LAN
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 10b8h
Subsystem ID = 1255h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

QNX seems to recognize SMC1244 because the io-net is automatically started
with devn-tulip, but I could not ping to any host. For SMC1255, the QNX does
not even recognize it.

We have the docs to update the tulip driver for both of these chipsets,
but it has not yet been done.

Previously, JS wrote in qdn.public.qnxrtp.installation:

Hi, has anyone used these two NICs before? Are they supported in 6.2?

When I run pci -v on SMC1244, it shows:
Class = Network (Ethernet)
Vendor ID = 1317h, Admtek Inc
Device ID = 985h, ADM983 fast ethernet
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 1113h
Subsystem ID = ec02h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

When I run pci -v on SMC1255, it shows:
Class = Network (Ethernet)
Vendor ID = 1113h, Accton Technology Corporation
Device ID = 1216h, EN2242 Accton EN2242 PCI LAN
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 10b8h
Subsystem ID = 1255h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

QNX seems to recognize SMC1244 because the io-net is automatically started
with devn-tulip, but I could not ping to any host. For SMC1255, the QNX does
not even recognize it.
\

Thanks. Any idea when it will be beta release? Is it in the range of week or
month?

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.030411124914.10475H@node90.ott.qnx.com

We have the docs to update the tulip driver for both of these chipsets,
but it has not yet been done.

Previously, JS wrote in qdn.public.qnxrtp.installation:
Hi, has anyone used these two NICs before? Are they supported in 6.2?

When I run pci -v on SMC1244, it shows:
Class = Network (Ethernet)
Vendor ID = 1317h, Admtek Inc
Device ID = 985h, ADM983 fast ethernet
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 1113h
Subsystem ID = ec02h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

When I run pci -v on SMC1255, it shows:
Class = Network (Ethernet)
Vendor ID = 1113h, Accton Technology Corporation
Device ID = 1216h, EN2242 Accton EN2242 PCI LAN
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 10b8h
Subsystem ID = 1255h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

QNX seems to recognize SMC1244 because the io-net is automatically
started
with devn-tulip, but I could not ping to any host. For SMC1255, the QNX
does
not even recognize it.

\

Previously, JS wrote in qdn.public.qnxrtp.installation:

Thanks. Any idea when it will be beta release? Is it in the range of week or
month?

I can’t say definitely - it all depends on when I can schedule the time
to do it! More like a month, but that could change! :slight_smile:

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.030411124914.10475H@node90.ott.qnx.com> …
We have the docs to update the tulip driver for both of these chipsets,
but it has not yet been done.

Previously, JS wrote in qdn.public.qnxrtp.installation:
Hi, has anyone used these two NICs before? Are they supported in 6.2?

When I run pci -v on SMC1244, it shows:
Class = Network (Ethernet)
Vendor ID = 1317h, Admtek Inc
Device ID = 985h, ADM983 fast ethernet
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 1113h
Subsystem ID = ec02h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

When I run pci -v on SMC1255, it shows:
Class = Network (Ethernet)
Vendor ID = 1113h, Accton Technology Corporation
Device ID = 1216h, EN2242 Accton EN2242 PCI LAN
PCI Index = 0h
Class Codes = 020000h
Revision ID = 11h
Bus number = 0
Device number = 6
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header Type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = fedffc00h 32bit length 1024 enabled
Sybsystem Vendor ID = 10b8h
Subsystem ID = 1255h
Max Lat = 255ns
Min Gnt = 255ns
PCI Int Pin = INT A
Interrupt Line = 9
Capabilities Pointer = c0h
Capability ID = 1h
Capabilities = fe82h - 0h

QNX seems to recognize SMC1244 because the io-net is automatically
started
with devn-tulip, but I could not ping to any host. For SMC1255, the QNX
does
not even recognize it.




\