netdev - Re: dmfe/tulip device id overlap

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091129.230703.206229796.davem@davemloft.net>
Date:	Sun, 29 Nov 2009 23:07:03 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	brandon@...p.org
Cc:	grundler@...gle.com, tobias@...gis.se, kyle@...artin.ca,
	netdev@...r.kernel.org, grundler@...isc-linux.org
Subject: Re: dmfe/tulip device id overlap

From: Brandon Philips <brandon@...p.org>
Date: Sun, 29 Nov 2009 22:55:12 -0800

> Thus, the patch only lets tulip handle 0x9100 and 0x9102 if __sparc__.
> 
> Perhaps someone knows if there is a way to tell the PCI card from the
> sparc builtin machine?

We should get both cases working in one of the two drivers,
preferrably Tulip.

That's the outcome I'm trying to say is the only legitimate one.
--
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