LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, saw@saw.sw.com.sg
Subject: Re: [2.6 patch] the scheduled eepro100 removal
Date: Wed, 03 Jan 2007 01:07:56 +0100	[thread overview]
Message-ID: <459AF3DC.1040305@tremplin-utc.net> (raw)
In-Reply-To: <20070102215726.GC20714@stusta.de>

02.01.2007 22:57, Adrian Bunk wrote/a écrit:
> This patch contains the scheduled removal of the eepro100 driver.

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
+alias:          pci:v00008086d00001227sv
+alias:          pci:v00008086d00005200sv
+alias:          pci:v00008086d00005201sv

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

See you,
Eric

  reply	other threads:[~2007-01-03  0:10 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 [this message]
2007-01-03 22:14   ` Jesse Brandeburg
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=459AF3DC.1040305@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=bunk@stusta.de \
    --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).