Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Missing device ids in e100.c?
Date: Thu, 18 Jan 2018 14:17:52 -0800	[thread overview]
Message-ID: <20180118141752.00007188@intel.com> (raw)
In-Reply-To: <d1ee433614608c72175747c2767bf20a.squirrel@mx.sdf.org>

On Wed, 17 Jan 2018 23:45:47 +0000 <sethsimon@sdf.org> wrote:

> Hi,
> I think I found an oversight in e100.c: The DOS packet driver
> based on the same chipset includes 3 additional PCI device ids
> (1035, 1036, and 1037 (all ICH 3)) that aren't in e100.c. See
> il.asm:207 in http://www.crynwr.com/drivers/e100b11b.zip.

Hi, thanks for your feedback. I investigated a bit for you.

I don't think the e100.c driver will support these without being
changed in the actual code.  They are all for the Home PNA (Phoneline
Network Adapter) products which are all end of life (not maintained or
sold).

1035 is the 82562EH based Phoneline Network Connection
1036 is the 82562EH based Phoneline Network Connection
1037 is also from the 82562 family

I recommend you don't worry about the missing IDs, unless you actually
have one of these devices and can get it to work (yourself) with the
e100.c driver, then we would review your patch.

Sorry to not be more help, but we generally don't do any development on
end of lifed products.

Jesse

      reply	other threads:[~2018-01-18 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 23:45 [Intel-wired-lan] Missing device ids in e100.c? sethsimon
2018-01-18 22:17 ` Jesse Brandeburg [this message]

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=20180118141752.00007188@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=intel-wired-lan@osuosl.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