Subject: Re: WD8013 died (SMC howto fix)
To: Chris G Demetriou <Chris_G_Demetriou@UX2.SP.CS.CMU.EDU>
From: William O Ferry <WOFerry+@CMU.EDU>
List: current-users
Date: 03/17/1996 04:36:01
    I'd be willing to give it a shot.  It does sound like it should be
pretty easy.  This would be my first attempt at writing "real" Unix
code, so if somebody would be willing to provide some pointers (on
things like manpage writing, I could probably figure most of the
RAM-poking stuff out from the i386 sources), and if somebody could tell
me just what 1(e) means...  =)

    I'd appreciate any help.  I feel it's about time I start making a
contribution to the project.  Thanks in advance.

                                                    Will Ferry

> > I found this in the news and since I hadn't found the
> > actual solution in the mailing-lists/ (i checked port-i386
> > and current-users and netbsd-help)...
> > 
> > ..and since this works... (I tried it after the bloddy
> > mcd0 driver killed my smc8013ebc (300,dc00,10) card type 0x29)
> > The mcd0 driver succeeded in overwriting my hard-ware-node-address.
> > 
> > I'm posting so it CAN be found in the mailing-lists as everyone
> > is pointing out:
> Since the solution to this simply involves frobbing a few I/O ports,
> it can also be done using NetBSD, if you're willing to get your hands
> dirty and write a little bit of C...
> It'd be nice if:
>         (1) somebody wrote up a little program to do this, probably by
>                 (a) taking (as an option) the ethernet address of the
>                     card, or prompting for it,
>                 (b) taking (as an option) a name that indicates the
>                     board type,
>                 (c) turning (b) into a number (there should be
>                     enough information in dev/isa/if_edreg.h to do
>                     this, i think),
>                 (d) prompting to confirm that it should be done
>                     (prompt should be overridable by a -f flag 8-), and
>                 (e) using the appropriate inb and outb sequence to
>                     DTRT.
>         (2) that program had a nice manual page that explained what it
>             did,
>         (3) that program was shipped as part of the NetBSD/i386
>             distribution, and
>         (4) that program was mentioned in the install notes and FAQ,
>             to help people get around this problem.