From: manojkiran.eda@gmail.com
To: Swetha Nagapuri <swethuu.n@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: Queries reg OpenBMC contribution
Date: Wed, 21 Feb 2024 10:56:56 +0530 [thread overview]
Message-ID: <6e03e9e5-f02e-480c-a4ea-3dd72d645766@Spark> (raw)
In-Reply-To: <CAKHO_vLYUYfW=sZ-j8iWgfrRpcBSeji5OmnMwWWH5VEfFnH_xA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Hi Swetha,
> Hi Manojkiran,
>
> Nice to connect with you over email. I am Swetha Nagapuri currently exploring OpenBMC mctp and PLDM stacks. I am planning to contribute to OpenBMC mctp and pldm code bases but have below queries.
>
> 1. How can I contribute to OpenBMC? Please let me know the steps if you have.
https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md should help you with the steps to contribute to openbmc.
> 2 I can't see any source code for mctp over smbus. Can you please help me to understand why this is not part of openbmc yet? I am planning to raise a couple of gerrits to support this. How can I do that?
Specs like MCTP and PLDM e.t.c are not openbmc specific, they are generic protocols which can be used as a communication means between embedded systems, There is no need to have mctp/pldm in openbmc. But with that said i believe there is support for MCTP over i2c. Look at https://codeconstruct.com.au/docs/mctp-on-linux-introduction/ for more information on what's being supported.
> 3. In PLDM code, I am planning to read sensor data from sysfs nodes directly instead of some dbus methods. Can I proceed with this approach?
>
This question is very vague, and cannot be answered without details. Feel free to come up with a design document capturing what you are planning to do or pitch it in #pmci discord channel for quick feedback from the community.
> Any response would be appreciated
Please send emails to the community mailing list openbmc@lists.ozlabs.org rather than send them personally, questions like these could help others too.
> Thanks,
> Swetha
Thanks,
Manoj
[-- Attachment #2: Type: text/html, Size: 2610 bytes --]
parent reply other threads:[~2024-02-21 5:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAKHO_vLYUYfW=sZ-j8iWgfrRpcBSeji5OmnMwWWH5VEfFnH_xA@mail.gmail.com>]
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=6e03e9e5-f02e-480c-a4ea-3dd72d645766@Spark \
--to=manojkiran.eda@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=swethuu.n@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).