From: Ed Tanous <ed@tanous.net>
To: khader basha shaik <shaikkhaderbasha601@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: How to integrate new libraray in openbmc
Date: Thu, 5 Nov 2020 08:45:59 -0800 [thread overview]
Message-ID: <CACWQX83iRY7g10aS2p6ioO0S9ubH+91e8tc+GhuWbFjo+NDCvQ@mail.gmail.com> (raw)
In-Reply-To: <CAD+gp9B3q6A4Hp4N7f_T8CJuw0n1sk=vkCHWebx0seyuxJjx_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Thu, Nov 5, 2020 at 2:49 AM khader basha shaik <
shaikkhaderbasha601@gmail.com> wrote:
> Hi Team,
>
> I have a custom library and need to integrate it with openbmc.The library
> provides various output related to system information.
> I need this information to show up in phosphor-webUI.
>
In my understanding we need to register it with dbus interface.
> So I need to integrate my custom library with dbus.
>
> But I do not have much information about where to start?
>
>
> Any help or information on this would be really helpful.
>
>
>
If you point us to the code for the library you're wanting to integrate, as
well as what you're hoping to see as a result we can probably give you
better advice. As is, your request is quite vague, and I'm personally
finding it very hard to answer with non-generic advice. The openbmc
documentation is a pretty good place to start in your case. Once you have
some handle on it, put the code up somewhere that we can see it, and we'll
be able to give you more specific advice on where to go from there.
-Ed
[-- Attachment #2: Type: text/html, Size: 2592 bytes --]
next prev parent reply other threads:[~2020-11-05 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:47 How to integrate new libraray in openbmc khader basha shaik
2020-11-05 16:45 ` Ed Tanous [this message]
2020-11-05 23:00 ` Joseph Reynolds
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=CACWQX83iRY7g10aS2p6ioO0S9ubH+91e8tc+GhuWbFjo+NDCvQ@mail.gmail.com \
--to=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=shaikkhaderbasha601@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 NNTP newsgroup(s).