On 23-Jun-98 Jonathan Stone spoke unto us all:
# 
# >Don't worry, Tim. I'd probably dismember anyone attempting to do so.
# 
# I just tried the following with -current on a machine with an
# SMC card:
#       we1 at isa0 port 0x300-0x31f iomem 0xcc000-0xcffff irq 10
#       we1: SMC8216/SMC8216C Ethernet (16-bit)
#       we1: Ethernet address 00:00:c0:6d:bd:7e
# 
# When the mcd driver didnt have port accounting and had an overly-keen
# match routine, sure, it was busted. But after the above, I see no
# cause for especial concern, certainly not for SMC cards.
# Am I missing something?

This really scares the crap outta me..  But this is my card (see bottom for one
of them).  This particular one is set to irq3 for a variety of odd reasons..
(dont ask)  The point is..  it is different from the one you have, and as far
as I know, this version was the only one that graciously allowed itself to be
reporgrammed. (Along with the ultra.. though I am not sure about that one.) 
I'll be totally honest.. I don't remeber what was wiping my card out.. but I
think it was the mcd driver..  But it *really* drove me nuts.  I avoided 1.1
and 1.2 for the longest time because of this, and upgraded alot of machines
from 1.0 to 1.3 directly.

All I can say is.. if we re-enable that driver.. we had better be sure we
aren't screwing anybody's hardware up this time.. because If I wasn't such a
big netbsd devotee, and a piece of software did what SMC tech support referred
to as "irrepariable damage" to my card...  I would never use that software
again.  People don't take kindly to hardware damage.. And if a kind soul didn't
walk me through the math and assist me in fixing mine, I'd be using something
else today...  One has to wonder how many SMC Elite users we lost between 1.1
and 1.2.....

we0: overriding IRQ 9 to 3
we0 at isa0 port 0x280-0x29f iomem 0xd0000-0xd3fff irq 3
we0: WD8013WC Ethernet (16-bit)
we0: Ethernet address 00:00:c0:ee:b5:57


---
Tim Rightnour    -  root@garbled.net
http://www.zynetwc.com/~garbled/garbled.html