openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Thangavel <thangavel.k@hcl.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
	Patrick Williams <patrickw3@fb.com>,
	"deepak.kodihalli.83@gmail.com" <deepak.kodihalli.83@gmail.com>
Subject: Add firmware implementation in pldm
Date: Wed, 9 Dec 2020 15:50:07 +0000	[thread overview]
Message-ID: <HK0PR04MB2964D0B4027D7B3AE80A3E9EFDCC0@HK0PR04MB2964.apcprd04.prod.outlook.com> (raw)

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

Classification: Internal
Hi All,

         We planning to do NIC firmware update for our system pldm base.

         So, We would like to add implementation support for pldm base firmware update. This should be generic for all to use firmware update for any devices.

         Do we need to create files "firmwareupdate.cpp/.hpp files" under pldm deamon as generic to handle firmware base pldm commands?

         Also, please suggest to repo add the BMC applications to send and recv the command handling.

         Could Please provide your comments/suggestions on this implementation.

Thanks,
Kumar.
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

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

             reply	other threads:[~2020-12-09 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 15:50 Kumar Thangavel [this message]
2020-12-09 16:17 ` Add firmware implementation in pldm Deepak Kodihalli
2020-12-10 12:17   ` Kumar Thangavel
2021-02-04 13:55     ` Deepak Kodihalli

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=HK0PR04MB2964D0B4027D7B3AE80A3E9EFDCC0@HK0PR04MB2964.apcprd04.prod.outlook.com \
    --to=thangavel.k@hcl.com \
    --cc=deepak.kodihalli.83@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrickw3@fb.com \
    --cc=velumanit@hcl.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).