From: Patrick Williams <patrick@stwcx.xyz>
To: Neil Bradley <Neil_Bradley@phoenix.com>
Cc: Amithash Prasad <amithash@fb.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Vijay Khemka <vijaykhemka@fb.com>,
Bruce Mitchell <Bruce_Mitchell@phoenix.com>
Subject: Re: Tioga Pass OpenBMC 2.8
Date: Fri, 28 Aug 2020 07:44:33 -0500 [thread overview]
Message-ID: <20200828124433.GO3532@heinlein> (raw)
In-Reply-To: <75b5584cca72489f95c2d22c129a754f@SCL-EXCHMB-13.phoenix.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On Wed, Aug 26, 2020 at 09:38:55PM +0000, Neil Bradley wrote:
> Thank you Patrick! Yes, indeed on Tioga Pass the RGMII (second interface) goes to the i210. Odd that it'd get added but no one uses it?
Facebook designed the Tioga Pass server and we use the NC-SI path on
that server. Since the server was designed for OCP, we recognize NC-SI
isn't always the preferred path for everyone, so we included the other
interface even thought we don't use it ourselves.
There was work at one point to qualify the second interface, but that
work was done on an old kernel branch and never sent upstream. Since the
faraday driver had a large rewrite, I would be surprised if this patch
applies cleanly to the 5.x series, but here it is:
https://github.com/facebook/openbmc-linux/commit/eae4bbfbcb8faa091c089f9a367964b0eacd9ba1#diff-157e77f59ffce03237d949d9318dbff4
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-28 12:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 1:36 Tioga Pass OpenBMC 2.8 Neil Bradley
2020-08-24 17:07 ` Bruce Mitchell
2020-08-24 22:52 ` Vijay Khemka
2020-08-24 21:05 ` Vijay Khemka
2020-08-24 21:17 ` Neil Bradley
2020-08-24 21:32 ` Neil Bradley
2020-08-24 23:02 ` Vijay Khemka
2020-08-24 23:34 ` Neil Bradley
2020-08-25 0:00 ` Vijay Khemka
2020-08-25 1:35 ` Neil Bradley
2020-08-25 14:25 ` Patrick Williams
2020-08-26 21:38 ` Neil Bradley
2020-08-28 12:44 ` Patrick Williams [this message]
2020-08-25 22:22 ` Neil Bradley
2020-08-26 16:46 ` Vijay Khemka
2020-08-26 16:48 ` Neil Bradley
2020-08-26 16:53 ` Vijay Khemka
2020-08-26 18:43 ` Neil Bradley
2020-08-26 21:52 ` Neil Bradley
2020-08-27 5:27 ` Vijay Khemka
2020-09-09 23:12 ` Patrick Voelker
2020-09-10 21:13 ` Vijay Khemka
2020-09-10 21:40 ` Patrick Voelker
2020-09-11 19:47 ` Vijay Khemka
2020-09-11 19:54 ` Vijay Khemka
2020-09-14 17:30 ` Patrick Voelker
2020-09-15 17:19 ` Patrick Voelker
2020-09-15 19:12 ` Vijay Khemka
2020-09-15 19:07 ` Vijay Khemka
2020-09-15 19:42 ` Patrick Voelker
2020-08-27 5:39 ` Vijay Khemka
2020-08-27 6:29 ` Neil Bradley
2020-08-27 6:44 ` Vijay Khemka
2020-08-27 17:19 ` Neil Bradley
2020-08-27 18:42 ` Vijay Khemka
2020-08-27 21:59 ` Neil Bradley
2020-08-28 16:25 ` Vijay Khemka
2020-08-28 16:33 ` Neil Bradley
2020-08-28 20:43 ` Vijay Khemka
2020-08-24 22:58 ` Vijay Khemka
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=20200828124433.GO3532@heinlein \
--to=patrick@stwcx.xyz \
--cc=Bruce_Mitchell@phoenix.com \
--cc=Neil_Bradley@phoenix.com \
--cc=amithash@fb.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vijaykhemka@fb.com \
/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.