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]
Date:	Mon, 3 Nov 2008 09:04:30 +0100
From:	Andreas Mohr <andim2@...rs.sourceforge.net>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
Cc:	andi@...as.de, e1000-devel@...ts.sourceforge.net,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	bunk@...nel.org
Subject: Re: [RFC/PATCH] e100 driver didn't support any MII-less PHYs...

Hi,

On Wed, Jan 30, 2008 at 08:34:27AM -0800, Kok, Auke wrote:
> Andreas Mohr wrote:
> > Hi,
> > 
> > On Tue, Jan 29, 2008 at 03:09:25PM -0800, Kok, Auke wrote:
> >> Andreas Mohr wrote:
> >>> Perhaps it's useful to file a bug/patch
> >>> on http://sourceforge.net/projects/e1000/ ? Perhaps -mm testing?
> >> I wanted to push this though our testing labs first which has not happened due to
> >> time constraints - that should quickly at least confirm that the most common nics
> >> work OK after the change with your patch. I'll try and see if we can get this
> >> testing done soon.
> > 
> > Oh, full-scale regression testing even? Nice idea...
> > Would optionally be even better if during hardware tests one could also
> > dig out some i82503-based card (or additional MII-less cards?)
> > since I didn't really make any effort yet to try to make them all
> > recognized/supported by my patch already (would have been out of scope anyway
> > since I have this single card only).
> 
> the problem is that I think that most of those (mii-less cards) are customly
> designed by OEM's that buy the silicon and glue on a different interface and we
> usually do not carry those designs in our labs apart from a few exceptions. So, I
> can at least touch the common hardware in testing, but not the exotic stuff.

Any update on how to get this support in? (it's not available in 2.6.28-rc2)

As it stands, I'm not the only one who would need this...

Thanks!

Andreas Mohr
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ