netdev - Re: [patch] NET: remove support for Davicom 9102 from the Tulip driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 9 Apr 2008 09:54:39 -0600
From:	Grant Grundler <grundler@...isc-linux.org>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Grant Grundler <grundler@...isc-linux.org>,
	Jeff Garzik <jeff@...zik.org>, cebbert@...hat.com,
	netdev@...r.kernel.org
Subject: Re: [patch] NET: remove support for Davicom 9102 from the Tulip
	driver

On Mon, Apr 07, 2008 at 05:28:03PM +0300, Meelis Roos wrote:
> > jeff and davem already answered the basic SROM/MAC address issue.
> > Patches to fix this are associated with
> > 	http://bugzilla.kernel.org/show_bug.cgi?id=9106
> 
> > >> I happent to have a Sun Fire V100 with 2 Davicom NICs (1282:9102 (rev 
> > >> 31)).
> > >> tulip driver works for them, dmfe doesn't.
> > 
> > This experience doesn't agree with the bug report.
> > Meelis, can you please take a look at the bug report and add comments?
> 
> Comments added.

thanks!
I saw the comments were added but haven't read them yet.

> > We tried (b) but didn't get it working on V100 previously.
> > Several patches are attached to the bug report.
> 
> There was one patch (for getting the MAC from OpenFirmware) but as 
> people reported that the Tx timeouts still happen, I didn't try it. Any 
> reason to try?

Documenting the configuration that does work is the only reason.
I don't think pursueing dmfe is worthwhile if in general tulip driver
is expected to work.

thanks,
grant

> 
> -- 
> Meelis Roos (mroos@...ux.ee)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html