-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Edgecore][as9516-32d] Access BMC by using libcurl #941
base: master
Are you sure you want to change the base?
[Edgecore][as9516-32d] Access BMC by using libcurl #941
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution.
Please fix the typos and formatting of the merge/pull request description. Please also describe the goal. Where is OpenBMCv1 installed on?
@@ -29,14 +29,14 @@ Multistrap: | |||
|
|||
Debian: | |||
packages: *Packages | |||
source: http://${DEBIAN_MIRROR} | |||
source: http://archive.debian.org/debian/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks unrelated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We git clone the codebase from community and build it. The building result is failed.
We reference the this modification to make sure the success building.
https://github.com/opencomputeproject/OpenNetworkLinux/pull/933/files
Although this modification actually is unrelated for as9516-32d platform, the ONL installer need to build successfully.
We can close this PR and send the two PR(one for building, one for as9516-32d) if need be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We git clone the codebase from community and build it. The building result is failed.
We reference the this modification to make sure the success building. https://github.com/opencomputeproject/OpenNetworkLinux/pull/933/files
You should then merge that branch, so the relationship is clear.
We can close this PR and send the two PR(one for building, one for as9516-32d) if need be.
No need to close this one. Just “force-push” your amended commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We git clone the codebase from community and build it. The building result is failed.
We reference the this modification to make sure the success building. https://github.com/opencomputeproject/OpenNetworkLinux/pull/933/filesYou should then merge that branch, so the relationship is clear.
We can close this PR and send the two PR(one for building, one for as9516-32d) if need be.
No need to close this one. Just “force-push” your amended commits.
This PR is related jessie and wheezy, not include stretch. And this PR provider is not us.
https://github.com/opencomputeproject/OpenNetworkLinux/pull/933/files
For the clear relationship, should we send a new PR for stretch ?
And then remove this stretch modification from this PR ?
Thank you for your suggestion. |
In my opinion the branch name is less important than the lost discussion/comments of the merge/pull request. Should you change it, please spell curl correctly. ;-) |
Sorry about wrong branch name. |
1. Modify kernel config for using usb0 interface 2. Implement the BMC curl accessing for ONL 3. Fix the issus that failed building with stretch Signed-off-by: Willy Liu <[email protected]>
95be6f8
to
5993f24
Compare
OK, we already modify it. Best regards |
Thank you for the improvements. Still some requests:
|
Thanks for your suggestion. |
Hi,
|
Hi Best regards, |
Hi WillyLiu, I downloaded the repo and patched but I get the same failure.. are you running "make docker" after you clone and patch? |
Our building process
|
Hello,
So the issue is that we can't merge anything that breaks the general build,
hence the "make docker" test which is the first way we check PRs.
…On Mon, Sep 11, 2023, 6:49 PM WillyLiu-EC ***@***.***> wrote:
Hi WillyLiu,
I downloaded the repo and patched but I get the same failure.. are you
running "make docker" after you clone and patch?
Our building process
1. docker/tools/onlbuilder -9
2. source setup.env
3. make amd64
4.
—
Reply to this email directly, view it on GitHub
<#941 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP5WH443RX3X6BJ2VJBGYDXZ65SLANCNFSM6AAAAAAYUXPPTU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
New mail: [email protected] |
[Edgecore][as9516-32d] Access BMC by using libcurl
This modification is for creating usb0 interface.
And then, it can access BMC through usb0
To make sure BMC response, it uses libcurl to access BMC.
It can not build ONL for master. Need to modify the debian path for stretch.