| /openbmc/openbmc-test-automation/gui/test/access_control/ |
| H A D | test_obmc_gui_local_users.robot | 3 Documentation Test OpenBMC GUI "Local users" sub-menu of "Access control".
14 ${xpath_select_user} //input[contains(@class,"bmc-table__checkbox-input")]
15 ${xpath_edit_user} //button[@aria-label="Edit"]
16 ${xpath_delete_user} //button[@aria-label="Delete"]
18 ${xpath_add_user} //button[text()[contains(.,"Add user")]]
29 Verify Existence Of All Sections In Local User Management Page
30 [Documentation] Verify existence of all sections in local user management page.
36 Verify Existence Of All Buttons In Local User Management Page
37 [Documentation] Verify existence of all buttons in local user management page.
46 Verify Existence Of All Input Boxes In Local User Management Page
[all …]
|
| /openbmc/linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 2 Firmware Management
3 -------------------
7 Interface-Manifest
8 ------------------
11 Firmware Management Protocol. To support Firmware Management by the AP, the
12 Interface Manifest shall at least contain the Firmware Management Bundle and a
13 Firmware Management Protocol CPort within it.
18 For example, this is how the Firmware Management part of the Interface Manifest
21 ; Firmware Management Bundle (Bundle 1):
22 [bundle-descriptor 1]
[all …]
|
| /openbmc/openbmc/meta-phosphor/classes/ |
| H A D | obmc-phosphor-image.bbclass | 5 # - obmc-bmc-state-mgmt - OpenBMC BMC state management
6 # - obmc-bmcweb - OpenBMC webserver
7 # - obmc-chassis-mgmt - OpenBMC chassis management
8 # - obmc-chassis-state-mgmt - OpenBMC chassis state management
9 # - obmc-console - OpenBMC serial over LAN
10 # - obmc-dbus-monitor - OpenBMC dbus monitoring
11 # - obmc-debug-collector - OpenBMC debug collector
12 # - obmc-devtools - OpenBMC development and debugging tools
13 # - obmc-fan-control - OpenBMC fan management
14 # - obmc-fan-mgmt - Deprecated - use obmc-fan-control instead
[all …]
|
| /openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
| H A D | test_user_management_sub_menu.robot | 3 Documentation Test OpenBMC GUI "User management" sub-menu of "Security and access".
16 ${xpath_user_management_heading} //h1[text()="User management"]
17 ${xpath_select_user} //input[contains(@class,"custom-control-input")]
19 ${xpath_add_user} //button[contains(text(),'Add user')]
20 ${xpath_edit_user} //*[@data-test-id='userManagement-tableRowAction-edit-0']
21 ${xpath_delete_user} //*[@data-test-id='userManagement-tableRowAction-delete-1']
22 ${xpath_account_status_enabled_button} //*[@data-test-id='userManagement-radioButton-statusEnable…
23 ${xpath_account_status_disabled_button} //*[@data-test-id='userManagement-radioButton-statusDisabl…
24 ${xpath_username_input_button} //*[@data-test-id='userManagement-input-username']
25 ${xpath_privilege_list_button} //*[@data-test-id='userManagement-select-privilege']
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | user-management.md | 1 # User Management - OpenBMC - Design document
6 user-management components. The implementation detail is beyond the scope of
11 1. Use common user-management (e.g. phosphor-user-manager) rather than
12 application-based user-management. Especially, avoid IPMI based
13 user-management.
14 2. For security reasons, avoid transmitting passwords over any D-Bus API.
15 Observe this rule even while creating, modifying or authenticating the user.
16 3. Have applications use the PAM module to authenticate the user instead of
17 relying on a D-Bus API-based approach.
18 4. User creation has to be generic in nature wherever possible.
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | vhost-user.json | 1 # -*- Mode: Python -*-
7 # Marc-André Lureau <marcandre.lureau@redhat.com>
10 # later. See the COPYING file in the top-level directory.
13 # = vhost user backend discovery & capabilities
19 # List the various vhost user backend types.
32 # @rproc-serial: virtio remoteproc serial link
53 'rproc-serial',
63 # List of vhost user "block" features.
65 # @read-only: The --read-only command line option is supported.
66 # @blk-file: The --blk-file command line option is supported.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Power Management Strategies
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
[all …]
|
| /openbmc/docs/ |
| H A D | features.md | 5 - [BMCWeb][] HTTP/Web server
6 - [WebUI Vue][] web application
7 - REST Management: [BMCWeb Redfish][], [Phosphor REST APIs][] includes [Host
8 management REST APIs][]
9 - [D-Bus interfaces][] describes internal interfaces
10 - [D-Bus Object Mapper][]
11 - [Remote KVM][]
12 - [IPMI in band][] and [IPMI out of band][]
13 - Full IPMI 2.0 Compliance with DCMI
14 - SSH based SOL: [How to use][sol how to use]
[all …]
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-port.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ``devlink-port`` is a port that exists on the device. It has a logically
19 .. list-table:: List of devlink port flavours
22 * - Flavour
23 - Description
24 * - ``DEVLINK_PORT_FLAVOUR_PHYSICAL``
25 - Any kind of physical port. This can be an eswitch physical port or any
27 * - ``DEVLINK_PORT_FLAVOUR_DSA``
28 - This indicates a DSA interconnect port.
29 * - ``DEVLINK_PORT_FLAVOUR_CPU``
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
| H A D | README.md | 1 # User Management
5 User Manager service exposes D-Bus methods for user management operations.
7 ### User Manager Interface
9 User manager interface `xyz.openbmc_project.User.Manager` provides following
12 #### xyz.openbmc_project.User.Manager interface
16 - CreateUser - To create new user to the system.
17 - RenameUser - To rename existing user to new name in the system.
21 - AllGroups - To list all the groups supported in the system.
22 - AllPrivileges - To list all the privileges supported in the system.
26 - UserRenamed - Signal sent out when user is renamed in the system.
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | ipmb.rst | 5 The Intelligent Platform Management Bus or IPMB, is an
8 between the baseboard management (BMC) and chassis electronics.
12 The devices using the IPMB are usually management
13 controllers that perform management functions such as servicing
15 hot-swapping disk drivers in the system chassis, etc...
19 sends IPMI requests to a device (usually a Satellite Management
27 ----------------------------
29 ipmb-dev-int - This is the driver needed on a Satellite MC to
38 2) It defines the read and write functions to enable a user
43 --------------------
[all …]
|
| /openbmc/linux/kernel/power/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
9 suspend-to-RAM state (e.g. the ACPI S3 state).
27 Skip the kernel sys_sync() before freezing user processes.
30 user-space before invoking suspend. There's a run-time switch
32 This setting changes the default for the run-tim switch. Say Y
47 called "hibernation" in user interfaces. STD checkpoints the
60 for suspend states like suspend-to-RAM (STR) often don't work very
72 <file:Documentation/power/swsusp-and-swap-files.rst>).
100 The default resume partition is the partition that the suspend-
101 to-disk implementation will look for a suspended disk image.
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bb | 1 SUMMARY = "OpenBMC - Applications"
8 ${PN}-bmc-state-mgmt \
9 ${PN}-bmcweb \
10 ${PN}-chassis-state-mgmt \
11 ${PN}-console \
12 ${PN}-dbus-monitor \
13 ${PN}-extras \
14 ${PN}-devtools \
15 ${PN}-fan-control \
16 ${PN}-health-monitor \
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | amd_hsmp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 management functionality via HSMP (Host System Management Port).
10 The Host System Management Port (HSMP) is an interface to provide
11 OS-level software with access to system management functions via a
15 "7 Host System Management Port (HSMP)" of the family/model PPR
25 /dev/hsmp to let user space programs run hsmp mailbox commands.
27 $ ls -al /dev/hsmp
28 crw-r--r-- 1 root root 10, 123 Jan 21 21:41 /dev/hsmp
35 * Only root user is allowed to open the file in write mode.
38 In-kernel integration:
[all …]
|
| /openbmc/openbmc-tools/openbmctool/ |
| H A D | README.md | 12 - `-H`: The hostname or IP for the BMC
13 - `-U`: The username One of the password options:
14 - `-P`: The password, provided in-line
15 - `-A`: Prompt for a password
16 - `-E`: Take the password from envvar `OPENBMCTOOL_PASSWORD`
18 ## Enabling and Disabling Local BMC User Accounts
20 The local user accounts on the BMC, such as root, can be disabled, queried, and
21 re-enabled with the `local_users` sub-command.
23 Important: After disabling local users, an LDAP user will need to be used for
27 To view current local user account status:
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-flask-user_0.6.19.bb | 1 SUMMARY = "Customizable user account management for Flask"
2 DESCRIPTION = "Customizable User Account Management for Flask; Register \
5 HOMEPAGE = " https://github.com/lingthio/Flask-User"
6 LICENSE = "BSD-2-Clause"
11 PYPI_PACKAGE = "Flask-User"
16 python3-babel \
17 python3-blinker \
18 python3-flask \
19 python3-flask-login \
20 python3-flask-mail \
[all …]
|
| H A D | python3-flask-login_0.6.3.bb | 1 SUMMARY = "User session management for Flask"
2 DESCRIPTION = "Flask-Login provides user session management for Flask. \
5 HOMEPAGE = " https://github.com/maxcountryman/flask-login"
11 PYPI_PACKAGE = "Flask-Login"
15 RDEPENDS:${PN}:class-target = "python3-flask"
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-habanalabs | 21 Description: Allows the user to set the maximum clock frequency, in MHz.
23 The user should read the clk_cur_freq_mhz to see the actual
64 on-board EEPROM
82 Description: Interface to trigger a hard-reset operation for the device.
83 Hard-reset will reset ALL internal components of the device
90 Description: Displays how many times the device have undergone a hard-reset
97 Description: Allows the user to set the maximum clock frequency for MME, TPC
98 and IC when the power management profile is set to "automatic".
105 Description: Allows the user to set the maximum clock frequency, in Hz, of
107 device only when the power management profile is set to "manual"
[all …]
|
| H A D | sysfs-class-scsi_host | 7 Storage Control Unit embeds up to two 4-port controllers in
34 Contact: linux-ide@vger.kernel.org
36 (RW) This parameter allows the user to read and set the link
37 (interface) power management.
46 max_performance: Generally, this means no power management.
48 management.
56 management) on top, which makes it match the Windows IRST (Intel
60 a) It does not use host-initiated slumber mode, but it does
61 allow device-initiated slumber
68 Contact: linux-ide@vger.kernel.org
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | sprd,sc27xx-pmic.txt | 1 Spreadtrum SC27xx Power Management Integrated Circuit (PMIC)
5 mobile handset power management, audio codec, battery management and user
8 - DCDCs to support CPU, memory.
9 - LDOs to support both internal and external requirement.
10 - Battery management system, such as charger, fuel gauge.
11 - Audio codec.
12 - User interface function, such as indicator, flash LED and so on.
13 - IC level interface, such as power on/off control, RTC and typec and so on.
16 - compatible: Should be one of the following:
22 - reg: The address of the device chip select, should be 0.
[all …]
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | x86_pkg_temperature_thermal.rst | 7 * x86: with package level thermal management
14 ---------
16 Intel® 64 and IA-32 Architectures Software Developer’s Manual (Jan, 2013):
17 Chapter 14.6: PACKAGE LEVEL THERMAL MANAGEMENT
20 -----------
23 zone with maximum two user mode configurable trip points. Number of trip points
25 user mode can receive notification via thermal notification mechanism and can
29 Threshold management
30 --------------------
39 - trip_point_0_temp
[all …]
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | libsas.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The SAS Layer is a management infrastructure which manages
11 phy/OOB/link management, the SAS layer is concerned with:
13 * SAS Phy/Port/HA event management (LLDD generates,
15 * SAS Port management (creation/destruction),
17 * SAS Domain device management,
21 * Expander management and exporting expander control
22 to user space.
25 phy/OOB management, and vendor specific tasks and generates
47 ------------------
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | apm-acpi.rst | 6 odds are it supports either Advanced Power Management (APM) or
8 of the two technologies and puts power management in the hands of the
9 operating system, allowing for more intelligent power management than
21 simply cannot mix and match the two. Only one power management
24 User-space Daemons
25 ------------------
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
|
| /openbmc/ipmitool/ |
| H A D | README | 4 ipmitool-devel@lists.sourceforge.net
9 the Intelligent Platform Management Interface. IPMI is an open standard
12 service processor (or Baseboard Management Controller, BMC) is the brain
13 behind platform management and its primary purpose is to handle the
16 The ipmitool program provides a simple command-line interface to this BMC.
26 Microsystems. Sun had just embarked on a new line of general-purpose x86
29 feature for my systems in the lab and from there it grew into a multi-
33 ipmitool was not written to provide large-scale (aka Enterprise) management
37 who like the simplicity and scriptability of command-line utilities, as
44 that supports the IPMI specification. Many x86-based servers are now
[all …]
|
| /openbmc/linux/include/rdma/ |
| H A D | ib_mad.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB */
7 * Copyright (c) 2004-2006 Voltaire Corporation. All rights reserved.
18 /* Management base versions */
24 /* Management classes */
42 /* Management methods */
165 * 64-bit fields that are only 32-bit aligned. 64-bit architectures will
310 * ib_get_cpi_resp_time - Returns the resp_time value from
316 return (u8)(be32_to_cpu(cpi->cap_mask2_resp_time) & in ib_get_cpi_resp_time()
321 * ib_set_cpi_resptime - Sets the response time in an
329 cpi->cap_mask2_resp_time = in ib_set_cpi_resp_time()
[all …]
|