All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tony Lee (李文富)" <Tony.Lee@quantatw.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: How to upload proposal and code for specifying and customizing projects?
Date: Fri, 8 Mar 2019 02:49:50 +0000	[thread overview]
Message-ID: <417a986a10d340148fdc010a703ded2e@quantatw.com> (raw)
In-Reply-To: <20190307041941.22vujoizv5prib57@thinkpad>

Hi Brad,

> Is this package already written?  Would you mind filling out a design template for it?
No, the package is not ready yet. I will filling out a design template for it.

> I can certainly create a quanta-dbus-interfaces repository if you'd like.  But first - I'm just curious about what sorts of DBus APIs you have?  Are they actually specific to Quanta machines, or could they be put in phosphor-dbus-interfaces?  
Understood. It can also be used for the machine has NVMe drives on it. The APIs could be put in phosphor-dbus-interfaces.
for example, "xyz.openbmc_project.Nvme.Information”. The properties will be SerialNumber, VendorID, SmartWarnings, StatusFlags, DriveLifeUsed.

> Could you briefly talk about what some of the applications that present/would present these APIs do?
The application is to retrieve information of the NVMe devices by NVMe-MI commands via SMBus directly.

Thanks
Best Regards,
Tony

-----Original Message-----
From: Brad Bishop [mailto:bradleyb@fuzziesquirrel.com] 
Sent: Thursday, March 7, 2019 12:20 PM
To: Tony Lee (李文富) <Tony.Lee@quantatw.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: How to upload proposal and code for specifying and customizing projects?

On Tue, Mar 05, 2019 at 07:05:59AM +0000, Tony Lee (李文富) wrote:
>Hi Brad,
>
>I have two new packages "phosphor-nvme" 

Is this package already written?  Would you mind filling out a design template for it?

https://github.com/openbmc/docs/blob/master/designs/design-template.md

> and "quanta-dbus-interfaces" for specifying and customizing projects.
>There was a service pooling status of NVMe devices in " phosphor-nvme "
>and several d-bus interfaces for Quanta in "quanta-dbus-interfaces".
>
>1. Is it will be put into a new repository or put it under the meta-quanta?
>2. As for the proposal, is it still need to commit to gerrit under openbmc/docs ?

I can certainly create a quanta-dbus-interfaces repository if you'd like.  But first - I'm just curious abouut what sorts of DBus APIs you have?  Are they actually specific to Quanta machines, or could they be put in phosphor-dbus-interfaces?  

Do the applications that implement the APIs in quanta-dbus-interfaces already exist or are you planning on writing them in the future?

Could you briefly talk about what some of the applications that present/would present these APIs do?

thx - brad

  reply	other threads:[~2019-03-08  2:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  7:05 How to upload proposal and code for specifying and customizing projects? Tony Lee (李文富)
2019-03-07  4:19 ` Brad Bishop
2019-03-08  2:49   ` Tony Lee (李文富) [this message]
2019-03-08 17:34     ` Ed Tanous
2019-03-09  8:11       ` Tony Lee (李文富)
2019-03-11 17:45         ` Ed Tanous
  -- strict thread matches above, loose matches on Subject: below --
2019-03-06  9:47 Tony Lee (李文富)

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=417a986a10d340148fdc010a703ded2e@quantatw.com \
    --to=tony.lee@quantatw.com \
    --cc=bradleyb@fuzziesquirrel.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.