LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andreas Mohr <andim2@users.sourceforge.net>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: andi@lisas.de, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bunk@kernel.org
Subject: Re: [RFC/PATCH] e100 driver didn't support any MII-less PHYs...
Date: Mon, 3 Nov 2008 09:04:30 +0100 [thread overview]
Message-ID: <20081103080430.GA32459@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <47A0A713.7030304@intel.com>
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
next prev parent reply other threads:[~2008-11-03 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 23:51 [RFC/PATCH] e100 driver didn't support any MII-less PHYs Andreas Mohr
2007-12-30 5:54 ` Kok, Auke
2008-01-01 20:09 ` Andreas Mohr
2008-01-29 23:03 ` Andreas Mohr
2008-01-29 23:09 ` Kok, Auke
2008-01-30 6:49 ` Andreas Mohr
2008-01-30 16:34 ` Kok, Auke
2008-11-03 8:04 ` Andreas Mohr [this message]
2008-11-03 9:34 ` Jeff Kirsher
2008-01-01 20:10 ` Andreas Mohr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081103080430.GA32459@rhlx01.hs-esslingen.de \
--to=andim2@users.sourceforge.net \
--cc=andi@lisas.de \
--cc=auke-jan.h.kok@intel.com \
--cc=bunk@kernel.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).