Subject: Xircom 10/100 + modem cardbus driver
To: None <port-i386@netbsd.org>
From: Darren Reed <darrenr@telnetmedia.com>
List: port-i386
Date: 04/11/2000 13:30:29
I've got a CBEM56G (10/100 + 56k modem) Xircom card here, for a little
while at least and I was hoping to get it working on NetBSD.
The first point to note is that it is a CardBus card (not PCMCIA) so
the current driver (if_xe.c) cannot be used.
From there, two options seem to be available:
1. try and adapt if_xe.c to become if_xe_cardbus.c
2. use the tulip driver (it has a 21143) for networking only
The catch with (2) appears to be that "com* at cardbus? dev ? function ?"
is currently not valid so a modem driver would still be needed.
The current state of play (using today's -current kernel) is the following
with tlp configured:
IPsec: Initialized Security Association Processing.
tlp0 at cardbus0 dev 0 function 0: Xircom X3201-3 Ethernet, pass 0.3
tlp0: Ethernet address 00:10:a4:07:40:a5
ukphy0 at tlp0 phy 0: Generic IEEE 802.3u media interface
ukphy0: OUI 0x00c039, model 0x0014, rev. 10
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp0: supplying EUI64: 00:10:a4:ff:fe:07:40:a5
Xircom, CardBus Ethernet 10/100 + Modem 56, CBEM56G, 1.03 (manufacturer 0x105, product 0x1000) Xircom product 0x0103 (serial communications, interface 0x02, revision 0x03) at cardbus0 dev 0 function 1 not configured
Incidently, ifconfig'ing tlp0 up does not light up the device and nor does
any network activity appear to happen.
Without the tlp driver, it shows up as:
Xircom, CardBus Ethernet 10/100 + Modem 56, CBEM56G, 1.03 (manufacturer 0x105, product 0x103) Xircom X3201-3 Fast Ethernet Controller (21143) (ethernet network, revision 0x03) at cardbus0 dev 0 function 0 not configured
Xircom, CardBus Ethernet 10/100 + Modem 56, CBEM56G, 1.03 (manufacturer 0x105, product 0x1000) Xircom product 0x0103 (serial communications, interface 0x02, revision 0x03) at cardbus0 dev 0 function 1 not configured
when booting NetBSD.
If (1) would be the best way to go, I'll make a start on doing it but
I don't see how that resolves the com driver issue either.
If someone is willing to provide direction, I'm willing to spend time
hacking on it to get it working.
Darren