Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2006 18:14:00 -0400
From:      Park Foreman <livefreebsd@mac.com>
To:        Andre Guibert de Bruet <andy@siliconlandmark.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: cPCI Hotplug support
Message-ID:  <E3F46CAC-F86F-4B25-A790-931EB114BA56@mac.com>
In-Reply-To: <4621CB9B-0ECC-48D2-93ED-E7480255C20C@siliconlandmark.com>
References:  <F8B081A0-0288-4203-ADCD-DD304561FFB6@mac.com> <4621CB9B-0ECC-48D2-93ED-E7480255C20C@siliconlandmark.com>

next in thread | previous in thread | raw e-mail | index | archive | help
System: Nokia IP330 using AMD K6 processor
Card: Zynx ZX412 dual 10/100 card and DEC/Intel 21143 chipset

ifconfig:
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=8<VLAN_MTU>
         inet 172.21.1.1 netmask 0xffff0000 broadcast 172.21.255.255
         inet6 fe80::2c0:95ff:fee5:7d8c%dc0 prefixlen 64 scopeid 0x4
         ether 00:c0:95:e5:12:ab
         media: Ethernet autoselect (none)
         status: no carrier
dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=8<VLAN_MTU>
         inet 172.21.2.1 netmask 0xffff0000 broadcast 172.21.255.255
         inet6 fe80::2c0:95ff:fee5:7d8d%dc1 prefixlen 64 scopeid 0x5
         ether 00:c0:95:e5:23:cd
         media: Ethernet autoselect (none)
         status: no carrier

dmesg:
pci1: <PCI bus> on pcib1
dc0: <Intel 21143 10/100BaseTX> port 0xe000-0xe07f mem  
0xd8000000-0xd80003ff irq 10 at device 5.0 on pci1
miibus3: <MII bus> on dc0
dcphy0: <Intel 21143 NWAY media interface> on miibus3
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: Ethernet address: 00:c0:95:e5:7d:8c
dc0: [GIANT-LOCKED]
dc1: <Intel 21143 10/100BaseTX> port 0xe400-0xe47f mem  
0xd8001000-0xd80013ff irq 12 at device 6.0 on pci1
miibus4: <MII bus> on dc1
dcphy1: <Intel 21143 NWAY media interface> on miibus4
dcphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc1: Ethernet address: 00:c0:95:e5:7d:8d
dc1: [GIANT-LOCKED]

pciconf -vl:

pcib1@pci0:16:0:        class=0x060400 card=0x000000dc  
chip=0x00241011 rev=0x03 hdr=0x01
     vendor   = 'Digital Equipment Corporation'
     device   = '21151/2 PCI to PCI Bridge'
     class    = bridge
     subclass = PCI-PCI
dc0@pci1:5:0:   class=0x020000 card=0x0019110d chip=0x00191011  
rev=0x41 hdr=0x00
     vendor   = 'Digital Equipment Corporation'
     device   = 'DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr'
     class    = network
     subclass = ethernet
dc1@pci1:6:0:   class=0x020000 card=0x0019110d chip=0x00191011  
rev=0x41 hdr=0x00
     vendor   = 'Digital Equipment Corporation'
     device   = 'DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr'
     class    = network
     subclass = ethernet

I have been advised to look at http://cvstrac.pfsense.com/chngview? 
cn=4643
But, I am not using pfSense. Just 6.0 release.

I have also looked at http://www.znyx.com/support/drivers/ 
ZX412_drivers.htm

But these drivers don't work for me. If they can be made to work,  
could they be built into the next release or adapt the existing drivers?

Typically, I would say why bother with such old equipment but there  
are a lot of companies trying to breath new life into these old  
firewalls.

Park


On Apr 19, 2006, at 10:03 AM, Andre Guibert de Bruet wrote:

> On Apr 16, 2006, at 1:12 PM, livefreebsd@mac.com wrote:
>
>> Does 6.0 not support hot-swap Compact PCI?
>>
>> With an ethernet  card in this slot, O/S sees dc0 and dc1 but  
>> power to the actual tranceivers does not occur.
>>
>> i.e. FreeBSD sees the chipset and let me ifconfig anything. But,  
>> activity lights never works. This works with Linux.
>>
>> Can we port the code for this from Linux?
>
> This report is void of any relevant information and is therefore  
> useless for a variety of reasons:
>
> - What is the make of the ethernet card?
> - Could we get the appropriate pciconf -vl output?
> - What does the dmesg output look like for the card?
> - What model laptop is this being used in?
> - What CPU? AMD64 or I386?
>
> Why should we port a driver for a NIC that appears to be almost  
> working? It is way more efficient to make the relevant changes to  
> get the card working in the present driver. This of course,  
> requires that we know what devices you are trying to make  
> interoperate...
>
> Cheers,
> Andy
>
> /*  Andre Guibert de Bruet  * 6f43 6564 7020 656f 2e74 4220 7469  
> 6a20 */
> /*   Code poet / Sysadmin   * 636f 656b 2e79 5320 7379 6461 696d  
> 2e6e */
> /*   GSM: +1 734 846 8758   * 5520 494e 2058 6c73 7565 6874 002e  
> 0000 */
> /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML,  
> XML */
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E3F46CAC-F86F-4B25-A790-931EB114BA56>