From: "chunhui.jia" <chunhui.jia@linux.intel.com>
To: "Jayashree D" <jayashree-d@hcl.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Boot Sequence Configuration in D-BUS interfaces.
Date: Thu, 04 Feb 2021 13:11:09 +0800 [thread overview]
Message-ID: <601B81E9.1080206@linux.intel.com> (raw)
In-Reply-To: <SG2PR04MB3093C3B95174DA7371D078D6E1B69@SG2PR04MB3093.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
Jayashree,
The combination of boot mode and boot source maps to IPMI boot order.
Sample code for mapping could be found in
https://github.com/openbmc/phosphor-host-ipmid/blob/8a7236ae9309a413cec0644baf9e69f3f9a80160/chassishandler.cpp#L1695
2021-02-04
chunhui.jia
发件人：Jayashree D <jayashree-d@hcl.com>
发送时间：2021-02-01 21:57
主题：Boot Sequence Configuration in D-BUS interfaces.
收件人："openbmc@lists.ozlabs.org"<openbmc@lists.ozlabs.org>
抄送：
Classification: Public
Hi Team,
In phosphor-dbus-interfaces repo, boot order supports only boot mode and boot source dbus interfaces.
We need to display all the boot order sequences ( "USB_DEV", "NET_IPV6", "SATA_HDD", "SATA_CD", "Others" ) using dbus interfaces.
Please provide your suggestions on this part.
Regards,
Jayashree
::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: 5270 bytes --]
prev parent reply other threads:[~2021-02-04 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 13:57 Boot Sequence Configuration in D-BUS interfaces Jayashree D
2021-02-04 5:11 ` chunhui.jia [this message]
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=601B81E9.1080206@linux.intel.com \
--to=chunhui.jia@linux.intel.com \
--cc=jayashree-d@hcl.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.