sonic-linux-kernel icon indicating copy to clipboard operation
sonic-linux-kernel copied to clipboard

Supermicro_arm64_1G_Switch_G3748_Added: Patch of dts file to support …

Open SelvaSupermicro opened this issue 1 year ago • 7 comments

This patch is to support new platform, Supermicro 1G arm64 switch G3748 which uses marvel AC5X ASIC. This patch is applied for all arm64 builds and will be effective only for this new platform.

Testing:

  1. Tested running M0/PTF32 test suites for this new platform.
  2. Verified image partitions
  3. Verified uboot and sonic platform functionalities

SelvaSupermicro avatar Jan 08 '24 23:01 SelvaSupermicro

Has/will this been upstreamed?

saiarcot895 avatar Jan 12 '24 01:01 saiarcot895

Hello Saikrishna Yes, once the PR is reviewed and approved it should automatically get merged to master (upstream) I am sure you know that process.So I really don’t completely understand your question. Please help me understand I would be glad to respond.

SelvaSupermicro avatar Jan 12 '24 05:01 SelvaSupermicro

Yes, once the PR is reviewed and approved it should automatically get merged to master (upstream) I am sure you know that process.So I really don’t completely understand your question. Please help me understand I would be glad to respond.

Hi @SelvaSupermicro,

By upstream, I mean submitting this change into the main Linux kernel. See their contribution page for more details.

saiarcot895 avatar Jan 12 '24 18:01 saiarcot895

Yes, once the PR is reviewed and approved it should automatically get merged to master (upstream) I am sure you know that process.So I really don’t completely understand your question. Please help me understand I would be glad to respond.

Hi @SelvaSupermicro,

By upstream, I mean submitting this change into the main Linux kernel. See their contribution page for more details.

Thanks for the clarifications. These code changes are applicable only for SONiC. Hence we dont want to upstream to main Linux kernel.

SelvaSupermicro avatar Jan 18 '24 00:01 SelvaSupermicro

From your commit message:

hence will not be upstreamed to main ONL repo

SONiC and ONL are two separate projects for a network operating system. No idea, why you reference ONL.

To ease maintenance of the SONiC Linux kernel repository, you have to sent these patches upstream. Often upstream is also giving you a high quality review, that the SONiC developers/maintainers are not capable of.

Also the devicetree has a lot of commented out lines, that also need to be cleaned up.

paulmenzel avatar Feb 12 '24 08:02 paulmenzel

From your commit message:

hence will not be upstreamed to main ONL repo

SONiC and ONL are two separate projects for a network operating system. No idea, why you reference ONL.

To ease maintenance of the SONiC Linux kernel repository, you have to sent these patches upstream. Often upstream is also giving you a high quality review, that the SONiC developers/maintainers are not capable of.

Also the devicetree has a lot of commented out lines, that also need to be cleaned up.

From your commit message:

hence will not be upstreamed to main ONL repo

SONiC and ONL are two separate projects for a network operating system. No idea, why you reference ONL.

To ease maintenance of the SONiC Linux kernel repository, you have to sent these patches upstream. Often upstream is also giving you a high quality review, that the SONiC developers/maintainers are not capable of.

Also the devicetree has a lot of commented out lines, that also need to be cleaned up.

Sorry for the ONL reference. I meant to say Linux. Anyway, I have cleaned up the patch to include file that was already committed instead creating new.. Why I don't want to upstream to Linux repo,

  1. As you can see this patch file depends on many other patches. The other patch files all are in SONiC repo and not in main Linux repo. So they cant apply my patch as it is invalid in that repo.
  2. Our patch is applicable only for our switch platform running SONiC. So it applicable only for SONiC. It has no value in main Linux.

SelvaSupermicro avatar Feb 16 '24 02:02 SelvaSupermicro

@SelvaSupermicro please resolve the conflict

prgeor avatar Mar 22 '24 22:03 prgeor

Sorry for the delay here, could you rebase your changes on top of the master branch, or merge in the current master branch into your branch? This is to resolve the patch conflict in patch/series.

saiarcot895 avatar Apr 22 '24 05:04 saiarcot895

Sorry for the delay here, could you rebase your changes on top of the master branch, or merge in the current master branch into your branch? This is to resolve the patch conflict in patch/series.

Hi Saikrishna, Thanks for the comment. Now, I have updated patch so that it can be merged with the latest master. Let me know if that is all good!

SelvaSupermicro avatar Apr 30 '24 21:04 SelvaSupermicro

Please improve the merge/pull request summary/title.

paulmenzel avatar May 01 '24 04:05 paulmenzel

Hello SaiKrishna, We may need your approve on @SelvaSupermicro new update here? https://github.com/sonic-net/sonic-linux-kernel/pull/373/commits/4aadc9131e6260c2c200b9be5f528a8b41bdb901

ErichYen avatar May 07 '24 22:05 ErichYen

Looks like there's one conflict somehow?

saiarcot895 avatar May 08 '24 16:05 saiarcot895

Please improve the merge/pull request summary/title.

Echoing this, particularly the title.

saiarcot895 avatar May 08 '24 16:05 saiarcot895