Subject: Re: Davicom DM9102AF pci ethernet card?
To: None <tech-net@NetBSD.org>
From: Gene ENonymous <firstname.lastname@example.org>
Date: 01/09/2005 21:32:28
> To: tech-net@NetBSD.org
> From: email@example.com (Christos Zoulas)
> Subject: Re: Davicom DM9102AF pci ethernet card?
> Date: Sun, 9 Jan 2005 04:32:32 +0000 (UTC)
> In article <200501090320.j093KYfB016948@sdf.lonestar.org>,
> Gene ENonymous <firstname.lastname@example.org> wrote:
> >I just got a pair of Davicom pci ethernet cards I'd like to be
> >able to use under
> >NetBSD 2.0 i386.
> >With dmesg I get the following line with reference the card:
> > Davicom Semiconductor product 0x9009 (ethernet network,
> > revision 0x31) at pci0 dev 20 function 0 not configure
> >I'm hoping this is compatible with the one of the Davicom drivers built in
> >and there might be a low pain way to trick the kernel into thinking this
> >card is one of them...
> >If so, could you suggest which files to hack? (I already have /usr/src/sys...)
> >After searching around I found the following line in
> >pcidevs:product DAVICOM DM9102 0x9102 Davicom DM9102 10/100 Ethernet
> >Can I infer that the pci identifier of the new chip is 0x9009 and add a
> >line like:
> >pcidevs:product DAVICOM DM9102AF 0x9009 Davicom DM9102AF 10/100 Ethernet
> >If so, then what?
> Look in if_tlp_pci.c and add the necessary glue if that indeed is a tulip
> clone. You can look at the other opensource OS's for hints on how to make
> that chip work.
Thanks! This appears to be working. Now I just need to pull the orriginal
files back in, diff and post.
For the impatient I just pointed the DM9102AF to the same place as DM9102A
in if_tlp_pci.c (in addition to the above mentioned hack to pcidevs and
the commands mentioned in the top of that file...).