> X-Virus-Scanned: by XS4ALL Virus Scanner > Date: Tue, 8 Dec 2015 12:58:22 +0000 > From: Stuart Henderson <st...@openbsd.org> > > On 2015/12/08 21:36, Bryan Linton wrote: > > On 2015-12-08 12:22:56, Steven Chamberlain <ste...@pyro.eu.org> wrote: > > > > > > A question for Fred perhaps -- does the Netra T1 105 also use dc(4) > > > ethernet? Do you know if it's affected by this bug? > > > > > > > I have a Netra T1 105 that's currently in storage awaiting a move to > > a place where I can use it as a router again (they're VERY loud). > > > > I don't have a dmesg handy, but I know for a fact that mine used > > hme(4) as its built-in ethernet connectivity. I can't say if other > > models were shipped with different ethernet cards, but mine at least > > had an hme(4). > > > > I'm not sure if that helps solve your issue, but hopefully it's > > somewhat useful at least. :) > > > > -- > > Bryan > > > > T1 105 is always hme(4) onboard. Someone might have a card with dc(4) > though, for example I think the sun ethernet+SCSI combo PCI card might > have used it.
One problem here is that dc(4) was a very popular design that was replicated by many vendors, Each of them had different bugs and some had additional functionality (that the dc(4) might or might not actually use). So it is important to test this with the Davicom version of the chip. I'm still planning to go through my hardware collection to see if I can find one and plug it into one of my sparc64 machines. I just haven't found the time yet...
