*BSD News Article 86211


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!uunet!in2.uu.net!194.87.0.28!demos!news-out.communique.net!not-for-mail
From: "Raul Zighelboim" <mango@communique.,net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Problem with new SMC9332 with 21140A
Date: 5 Jan 1997 04:15:06 GMT
Organization: Communique Inc.
Lines: 47
Message-ID: <01bbfabe$66840940$667d1bcc@rodia>
References: <32CB883F.297@zow.desy.de>
NNTP-Posting-Host: rodia.communique.net
X-Newsreader: Microsoft Internet News 4.70.1155
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33633


Someone posted a patch for the if_de.c driver for this card (sorry; I do
have the name at hand).

I think the patch was as follow (and worked for me on 2.1.6R :-)
It goes like this:

-------cut here-----
if_de.c:

      TULIP_DC21140_DEC_DE500,      /* Digital DE500-?? 10/100 */
      TULIP_DC21140_SMC_9332,       /* SMC 9332 */
+     TULIP_DC21140A_SMC_9332BDT,       /* SMC 9332BDT  with 21140A */
      TULIP_DC21140_COGENT_EM100,       /* Cogent EM100 100 only */
      TULIP_DC21140_ZNYX_ZX34X,     /* ZNYX ZX342 10/100 */

+ static const tulip_boardsw_t tulip_dc21140A_smc9332bdt_boardsw = {
+     TULIP_DC21140A_SMC_9332BDT,
+     "SMC 9332BDT ",
+     tulip_dc21140_smc9332_media_probe,
+     tulip_dc21140_mii_media_preset,
+     tulip_dc21140_mii_probe,
+ };

    sc->tulip_boardsw = &tulip_dc21140_smc9332_boardsw;
    return;
      }
+     if (sc->tulip_chipid == TULIP_DC21140A) {
+   sc->tulip_boardsw = &tulip_dc21140A_smc9332bdt_boardsw;
+   return;
+     }
      id1 = sc->tulip_rombuf[0x60] | (sc->tulip_rombuf[0x61] << 8);
      id2 = sc->tulip_rombuf[0x62] | (sc->tulip_rombuf[0x63] << 8);
-----cut here------

Olaf Manczak <Olaf.Manczak@zow.desy.de> wrote in article
<32CB883F.297@zow.desy.de>...
> Dear All,
> 
> Does anybody has a fix for the de driver to support new SMC9332 PCI
> 10/100 Mbps ethernet cards with the 21140-AC chip (DC1036DA) instead of
> the plain 21140 ?
> 
> Simple fix to the source to check for one more chipid doesn't help...
> 
> -- Olaf Manczak
>