From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: andi@lisas.de
Cc: 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: Wed, 30 Jan 2008 08:34:27 -0800 [thread overview]
Message-ID: <47A0A713.7030304@intel.com> (raw)
In-Reply-To: <20080130064909.GA19793@rhlx01.hs-esslingen.de>
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.
Auke
next prev parent reply other threads:[~2008-01-30 16:35 UTC|newest]
Thread overview: 12+ 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
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 [this message]
2008-11-03 8:04 ` Andreas Mohr
2008-11-03 9:34 ` Jeff Kirsher
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=47A0A713.7030304@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=andi@lisas.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.