From: Jochen Henneberg <jh@henneberg-systemdesign.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] issue with kernel patch 2a3cdead8b408351fa1e3079b220fa331480ffbc
Date: Mon, 25 Apr 2016 18:00:45 +0200 [thread overview]
Message-ID: <1461600045.21920.10.camel@maxwell> (raw)
In-Reply-To: <1768814989.41697.1461598056358.JavaMail.zimbra@xes-inc.com>
Hi Aaron,
On Mo, 2016-04-25 at 10:27 -0500, Aaron Sierra wrote:
> Jochen,
> I have similar hardware to you. What PHY ID are you finding?
The chip is WTI210IT from Intel, I am currently not in the office but I
will provide the PHY ID tomorrow. However, the chip datasheet
(http://www.intel.de/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-datasheet.pdf)
8.27.3.3/8.27.3.4 says that the PHY IDs are fixed (RO), but the values
read from the chip are different from what is defined in the datasheet
and I wonder if this is related to the modified register read/write
after the patch.
However, the patch works fine with the BYT embedded network controller.
Jochen
>
> -Aaron
>
--
Henneberg - Systemdesign
Jochen Henneberg
Loehnfeld 26
21423 Winsen (Luhe)
--
Fon: +49 4174 668 773
Mobile: +49 172 160 14 69
Fax: +49 321 210 761 64
www: www.henneberg-systemdesign.com
next prev parent reply other threads:[~2016-04-25 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461577586.24438.14.camel@maxwell>
[not found] ` <9BBC4E0CF881AA4299206E2E1412B626501BC575@ORSMSX102.amr.corp.intel.com>
2016-04-25 15:07 ` [Intel-wired-lan] issue with kernel patch 2a3cdead8b408351fa1e3079b220fa331480ffbc Fujinaka, Todd
2016-04-25 15:27 ` Aaron Sierra
2016-04-25 16:00 ` Jochen Henneberg [this message]
2016-04-25 17:35 ` Aaron Sierra
2016-04-26 8:02 ` Jochen Henneberg
2016-04-26 14:47 ` Fujinaka, Todd
2016-04-27 11:55 ` Jochen Henneberg
2016-04-26 15:52 ` Aaron Sierra
2016-04-27 12:08 ` Jochen Henneberg
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=1461600045.21920.10.camel@maxwell \
--to=jh@henneberg-systemdesign.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 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.