LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Eric Piel" <Eric.Piel@tremplin-utc.net>
Cc: "Adrian Bunk" <bunk@stusta.de>,
	jgarzik@pobox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, saw@saw.sw.com.sg, "Kok,
	Auke-jan H" <auke-jan.h.kok@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [2.6 patch] the scheduled eepro100 removal
Date: Wed, 3 Jan 2007 14:14:36 -0800	[thread overview]
Message-ID: <4807377b0701031414o3eb8da81wededa7b7f6b26898@mail.gmail.com> (raw)
In-Reply-To: <459AF3DC.1040305@tremplin-utc.net>

On 1/2/07, Eric Piel <Eric.Piel@tremplin-utc.net> wrote:
> Hi, I've been using e100 for years with no problem, however more by
> curiosity than necessity I'd like to know how will be handled the
> devices which are (supposedly) supported by eepro100 and not by e100?
>
> According to "modinfo eepro100" and "modinfo e100" those devices IDs are
> only matched by eepro100:
> +alias:          pci:v00008086d00001035sv
> +alias:          pci:v00008086d00001036sv
> +alias:          pci:v00008086d00001037sv
These are phoneline (RJ-11) adapters, I doubt it would work with e100
or eepro100

> +alias:          pci:v00008086d00001227sv
1227 doesn't exist as a pro/100 in our database, typo maybe?

> +alias:          pci:v00008086d00005200sv
doesn't exist in our database

> +alias:          pci:v00008086d00005201sv
This was the pro/100 intelligent server adapter with a pro/100 behind
a 960.  There aren't too many of these out there, and they usually
require some special configuration (although they can work as a dumb
nic, but why would you want a full length pro/100 card?)

> Are they matched by some joker rule that I haven't noticed in e100, or
> is support for them really going to disappear?

I think support for these devices can disappear (as I don't think they
will work anyway) but if someone complains we can take into account
what eepro100 did to support it (if anything) and enable it in e100.

Jesse (e100 maintainer)

  reply	other threads:[~2007-01-03 22:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 21:57 Adrian Bunk
2007-01-03  0:07 ` Eric Piel
2007-01-03 22:14   ` Jesse Brandeburg [this message]
2007-01-03  9:10 ` Jan Kiszka
2007-02-20  0:06 Adrian Bunk
2007-03-25 14:58 Adrian Bunk
2007-03-28 22:17 ` Bill Davidsen
2007-03-28 22:26   ` Kok, Auke
2007-03-28 22:42     ` Jeff Garzik
2007-03-29  5:08       ` Yinghai Lu
2007-03-29  8:19         ` Roberto Nibali
2007-03-29 16:22           ` Brandeburg, Jesse
2007-03-30 16:40             ` Bill Davidsen

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=4807377b0701031414o3eb8da81wededa7b7f6b26898@mail.gmail.com \
    --to=jesse.brandeburg@gmail.com \
    --cc=Eric.Piel@tremplin-utc.net \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --subject='Re: [2.6 patch] the scheduled eepro100 removal' \
    /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

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).