On January 12, 2020 10:14:35 AM UTC, Baruch Siach <[email protected]> wrote:
>Hi Joel,
>
>Thanks for working on Clearfog hardware support improvements.
Sure - I finally just got tired of not being able to easily use mainline
builds, sat down and figured out the gaps and missing dependencies in order to
support at least my use cases and flexibility in general.
>
>On Sat, Jan 11 2020, Joel Johnson wrote:
>> Add a unique entry for ClearFog Base variant, reflected
>> in the board name and adjusted SerDes topology.
>
>This conflicts with the series I posted adding support for A388 SOM and
>Clearfog Base/Pro carriers EEPROM TLV:
>
> https://patchwork.ozlabs.org/cover/1200324/
>
>The EEPROM TLV is meant to allow run-time detection of the hardware on
>newer hardware revisions that populate the EEPROM. This patch is still
>useful for older SOM and carrier revisions but it might cause confusion
>for users.
>
>Would you mind to rebase your patches on top of my code?
Sure, I hadn't seen this in flight patch series, I'll take a look and
adjust/adapt/drop as needed. I believe that most of my units are older
non-EEPROM variants, but will test with your patches and at least make the
manual vs. dynamic detected config interoperable.
>Nit: help text indentation should be "tab + 2 spaces".
Thanks, I'll update accordingly.
Joel
