All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brenden Lai <Brenden_Lai@jabil.com>
To: Nancy Yuen <yuenn@google.com>, John Wang <wangzqbj@inspur.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: couple questions for OpenBMC
Date: Fri, 18 Jan 2019 01:55:23 +0000	[thread overview]
Message-ID: <SN6PR02MB569328246D6D9163D1A93850969C0@SN6PR02MB5693.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CADfYTpE2fxL7KNZp7AvW9wh2hzHp9wHzXORLRg8jnj-6_BcbPA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3084 bytes --]

Thanks Nancy .

From: Nancy Yuen <yuenn@google.com>
Sent: Friday, January 18, 2019 2:29 AM
To: John Wang <wangzqbj@inspur.com>
Cc: Brenden Lai <Brenden_Lai@jabil.com>; openbmc@lists.ozlabs.org
Subject: Re: couple questions for OpenBMC


On Thu, Jan 17, 2019 at 2:34 AM John Wang <wangzqbj@inspur.com<mailto:wangzqbj@inspur.com>> wrote:
On Thu, Jan 17, 2019 at 3:52 PM Brenden Lai <Brenden_Lai@jabil.com<mailto:Brenden_Lai@jabil.com>> wrote:
>
> Hi
>
> I have couple questions about OpenBMC .

>
> 1.if I decide use OpenBMC solution , Does it mean I should put all BMC source code on github including some commercial software  ?
I don't know what you mean by commercial software.  In OpenBMC we strive to use open source software.

To build OpenBMC you only need to check out one repo github.com/openbmc/openbmc<http://github.com/openbmc/openbmc> and invoke the bitbake commands to build for a supported platform.  The repo page has build instructions on it  The recipes in openbmc/openbmc will download the necessary package sources from other online sources and invoke the build commands for each of those packages.  The downloaded packages are cached locally.  It's also possible to create a local mirror of downloaded packages for your team to use.


>
>
>
> 2.Are there any tutorial or /document  for using dbus within OpenBMC ?
please refer to this link [https://github.com/openbmc/sdbusplus] for
documentation and examples.
or you can use busctrl to find out it.

example:
    busctl tree xyz.openbmc_project.LED.GroupManager
    busctl introspect   xyz.openbmc_project.LED.GroupManager
/xyz/openbmc_project/led/groups/enclosure_fault

> 3.Why there is no release note after V1.05 ?  Will the coming release  attach release note ?

The tags you see are just random tags points, not a coordinated release.  We are in the middle of testing the 2.6 official release at the moment.  It will be done early February and it will contain release notes.  You can search this mailing list for release activities and also the meeting minutes from the release planning workgroup are here<https://github.com/openbmc/openbmc/wiki/Release-Planning>.

>
>
> 4.I know openBMC is using some file text to represent  device (LED , sensor)

Linux uses device tree to describe the hardware component,you can
refer to https://elinux.org/Device_Tree_Usage
This link[https://github.com/openbmc/docs/blob/master/LED-architecture.md]
tells you how openbmc controls led.

Can be roughly described:
          phosphor-led-manager(strategy) -->
phosphor-led->sysfs(action)  --> linux led subsystem

 linux led subsystem :
https://github.com/openbmc/linux/blob/dev-4.19/Documentation/leds/leds-class.txt

>but I am curious about how this files bind to real device ?
>    Where is the low level operation relate code ?

https://github.com/openbmc/phosphor-led-sysfs/blob/e0844ff447abad01fa6f902caab3839336d1518d/physical.cpp#L131

>
>
> Thanks -Brenden
>
>
>
>
>
> Brenden Lai
> SR. BMC Design Engineer
> E&I, Jabil Design Services
>
>

[-- Attachment #2: Type: text/html, Size: 7548 bytes --]

  reply	other threads:[~2019-01-18  1:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17  7:51 couple questions for OpenBMC Brenden Lai
2019-01-17 10:27 ` John Wang
2019-01-17 18:28   ` Nancy Yuen
2019-01-18  1:55     ` Brenden Lai [this message]
2019-01-21 23:12       ` couple questions for OpenBMC - license 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=SN6PR02MB569328246D6D9163D1A93850969C0@SN6PR02MB5693.namprd02.prod.outlook.com \
    --to=brenden_lai@jabil.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wangzqbj@inspur.com \
    --cc=yuenn@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.