From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jeff Daly <jeffd@silicom-usa.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Skajewski, PiotrX" <piotrx.skajewski@intel.com>
Cc: "open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH] ixgbe: Manual AN-37 for troublesome link partners for X550 SFI
Date: Wed, 20 Jul 2022 14:39:42 -0700 [thread overview]
Message-ID: <04864247-0e37-6294-9ff8-4c7e9d7a830a@intel.com> (raw)
In-Reply-To: <VI1PR0402MB35172FB699C5CF918C65D3DCEA8F9@VI1PR0402MB3517.eurprd04.prod.outlook.com>
On 7/19/2022 6:30 AM, Jeff Daly wrote:
> I can't replace the hardcoded values with meaningful assignments because I don't know what the bit names are. This was originally a patch that Intel worked on for Silicom. I suspect they are all DFT bits and as such are probably not going to be disclosed.
Could you re-send the patch? It's many pages back now and, likely,
easier if you could re-send it.
Thanks,
Tony
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-07-20 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 19:27 [Intel-wired-lan] [PATCH] ixgbe: Manual AN-37 for troublesome link partners for X550 SFI Jeff Daly
2022-03-18 23:47 ` Tony Nguyen
2022-05-12 17:09 ` Tony Nguyen
2022-07-19 13:30 ` Jeff Daly
2022-07-20 21:39 ` Tony Nguyen [this message]
2022-05-11 8:26 ` Piotr Skajewski
-- strict thread matches above, loose matches on Subject: below --
2024-09-06 10:41 Jeff Daly
2024-09-06 15:54 ` Andrew Lunn
2024-09-06 20:49 ` Jeff Daly
2024-09-06 21:16 ` Andrew Lunn
2024-09-09 15:46 ` Jeff Daly
2024-09-09 19:35 ` Andrew Lunn
2024-09-10 17:51 ` Jeff Daly
2022-05-10 10:55 Skajewski, PiotrX
2022-03-16 19:24 Jeff Daly
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=04864247-0e37-6294-9ff8-4c7e9d7a830a@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffd@silicom-usa.com \
--cc=netdev@vger.kernel.org \
--cc=piotrx.skajewski@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox