All of lore.kernel.org
 help / color / mirror / Atom feed
From: krtaylor <kurt.r.taylor@gmail.com>
To: Andrew Geissler <geissonator@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: OpenBMC Starting Point
Date: Tue, 25 Feb 2020 09:31:28 -0600	[thread overview]
Message-ID: <2c6ac542-9834-8571-ae85-4b3074e78372@gmail.com> (raw)
In-Reply-To: <217C5292-AFE8-4139-A1DF-0761BF719781@gmail.com>

On 2/24/20 2:23 PM, Andrew Geissler wrote:
> 
> 
>> On Feb 24, 2020, at 9:40 AM, Samuel Herts <sdherts@gmail.com> wrote:
>>
>> So if I wanted a c++ script to run on the bmc whenever I desired, how exactly would I go about implementing it as a module to run? Kind of like the Phosphor state manager module that the Hello World guide starts on, specifically, what steps would I need to take or what resources should I look into for creating my own module that will run when a specific command is sent, like the systemctl start phosphor.
> 
> 
> This would probably make a good tutorial under
> https://github.com/openbmc/docs/tree/master/development
> but here’s the really fast answer from my perspective.

This is a *really good* quick-start tutorial. Care to push it as such?

Thanks Andrew!

Kurt Taylor (krtaylor)

<snip>

  reply	other threads:[~2020-02-25 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 17:38 OpenBMC Starting Point Samuel Herts
2020-01-20  6:57 ` Michael Richardson
2020-01-20 17:03   ` Samuel Herts
2020-01-21 15:21     ` Andrew Geissler
2020-01-21 16:52     ` Andrew Geissler
2020-01-31 17:15       ` Samuel Herts
2020-01-31 21:29         ` Andrew Geissler
2020-02-06 14:16         ` Michael Richardson
2020-02-24 15:40   ` Samuel Herts
2020-02-24 20:22     ` Andrew Geissler
2020-02-24 20:23     ` Andrew Geissler
2020-02-25 15:31       ` krtaylor [this message]
     [not found] <7601.1580558972@dooku>
2020-02-01 22:44 ` Michael Richardson

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=2c6ac542-9834-8571-ae85-4b3074e78372@gmail.com \
    --to=kurt.r.taylor@gmail.com \
    --cc=geissonator@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.