Searched +full:system +full:- +full:wide (Results 1 – 25 of 173) sorted by relevance
1234567
| /Documentation/scsi/ |
| D | advansys.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 AdvanSys (Advanced System Products, Inc.) manufactures the following
8 RISC-based, Bus-Mastering, Fast (10 Mhz) and Ultra (20 Mhz) Narrow
9 (8-bit transfer) SCSI Host Adapters for the ISA, EISA, VL, and PCI
10 buses and RISC-based, Bus-Mastering, Ultra (20 Mhz) Wide (16-bit
21 - ABP-480 - Bus-Master CardBus (16 CDB)
24 - ABP510/5150 - Bus-Master ISA (240 CDB)
25 - ABP5140 - Bus-Master ISA PnP (16 CDB)
26 - ABP5142 - Bus-Master ISA PnP with floppy (16 CDB)
27 - ABP902/3902 - Bus-Master PCI (16 CDB)
[all …]
|
| D | FlashPoint.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 MYLEX INTRODUCES LINUX OPERATING SYSTEM SUPPORT FOR ITS
17 FREMONT, CA, -- October 8, 1996 -- Mylex Corporation has expanded Linux
18 operating system support to its BusLogic brand of FlashPoint Ultra SCSI
20 MultiMaster line, currently support the Linux operating system. Linux
30 The Linux Operating System
33 Linux is a freely-distributed implementation of UNIX for Intel x86, Sun
35 machines. It supports a wide range of software, including the X Window
36 System, Emacs, and TCP/IP networking. Further information is available at
43 and file server environments, are available in narrow, wide, dual channel,
[all …]
|
| D | BusLogic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
57 BT-948/958/958D, will always be available from my Linux Home Page at URL
62 driver and SCSI subsystem at startup, along with any subsequent system messages
63 relevant to SCSI operations, and a detailed description of your system's
69 the BT-948 PCI Ultra SCSI Host Adapter, and then again for the BT-958 PCI Wide
90 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at
92 mail at techsup@mylex.com, by Voice at 510/608-2400, or by FAX at 510/745-7715.
101 -----------------------------------
103 During system initialization, the driver reports extensively on the host
[all …]
|
| /Documentation/arch/riscv/ |
| D | vector.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Vector Extension Support for RISC-V Linux
8 order to support the use of the RISC-V Vector Extension.
11 ---------------------
19 are not portable to non-Linux, nor non-RISC-V environments, so it is discourage
27 argument consists of two 2-bit enablement statuses and a bit for inheritance
30 Enablement status is a tri-state value each occupying 2-bit of space in
33 * :c:macro:`PR_RISCV_V_VSTATE_CTRL_DEFAULT`: Use the system-wide default
34 enablement status on execve(). The system-wide default setting can be
43 arg: The control argument is a 5-bit value consisting of 3 parts, and
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
34 System Sleep model:
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
20 the target sleep state is referred to as *system suspend* too (in the majority
21 of cases, whether this means a transition or a sleep state of the system should
23 working state is referred to as *system resume*.
[all …]
|
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
19 and the system stays in it until a special signal is received from one of
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 …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 system-wide
12 working-state
|
| D | system-wide.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 System-Wide Power Management
10 sleep-states
11 suspend-flows
|
| /Documentation/power/ |
| D | freezing-of-tasks.rst | 11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There is one per-task flag (PF_NOFREEZE) and three per-task states
21 system enters a sleep state as well as before a hibernation image is created
23 to system-wide suspend too).
26 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
27 static key freezer_active (as opposed to a per-task flag or state) is used to
28 indicate whether the system is to undergo a freezing operation. And
45 signal-handling code, but the freezable kernel threads need to call it
61 oom_reaper_list = tsk->oom_reaper_list;
73 entire system-wide transition will be cancelled. For this reason, freezable
[all …]
|
| D | drivers-testing.rst | 7 1. Preparing the test system
10 Unfortunately, to effectively test the support for the system-wide suspend and
12 functional system with this driver loaded. Moreover, that should be done
18 Of course, for this purpose the test system has to be known to suspend and
20 resolve all suspend/resume-related problems in the test system before you start
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
27 Once you have resolved the suspend/resume-related problems with your test system
31 (see: Documentation/power/basic-pm-debugging.rst, 1).
34 "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
43 Documentation/power/basic-pm-debugging.rst, 2). [As far as the STR tests are
[all …]
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 2 Real-Time group scheduling
12 2.1 System-wide settings
21 Fiddling with these settings can result in an unstable system, the knobs are
27 system when the period is smaller than either the available hrtimer
31 system when the runtime is so small the system has difficulty making
33 are real-time processes).
40 ---------------
42 Real-time scheduling is all about determinism, a group has to be able to rely on
44 multiple groups of real-time tasks, each group must be assigned a fixed portion
45 of the CPU time available. Without a minimum guarantee a real-time group can
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power | 14 space to check if the device is enabled to wake up the system
20 used to activate the system from a sleep state. Such devices
31 For the devices that are not capable of generating system wakeup
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
61 with the main suspend/resume thread) during system-wide power
86 attribute is read-only. If the device is not capable to wake up
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
[all …]
|
| /Documentation/trace/ |
| D | tracepoint-analysis.rst | 15 what is going on within the system. There are a large number of methods for
27 ----------------------
32 $ find /sys/kernel/tracing/events -type d
37 ----------------------------------------
55 3.1 System-Wide Event Enabling
56 ------------------------------
59 can be enabled system-wide. A short example of enabling all events related
62 $ for i in `find /sys/kernel/tracing/events -name "enable" | grep mm_`; do echo 1 > $i; done
64 3.2 System-Wide Event Enabling with SystemTap
65 ---------------------------------------------
[all …]
|
| /Documentation/hwmon/ |
| D | vexpress.rst | 15 - http://infocenter.arm.com/help/topic/com.arm.doc.subset.boards.express/index.html
17 * Section "4.4.14. System Configuration registers" of the V2M-P1 TRM:
19 - http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0447-/index.html
24 -----------
27 reference & prototyping system for ARM Ltd. processors. It can be set up
28 from a wide range of boards, each of them containing (apart of the main
39 As these devices are non-discoverable, they must be described in a Device
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 File system Monitoring with fanotify
7 File system Error Reporting
10 Fanotify supports the FAN_FS_ERROR event type for file system-wide error
11 reporting. It is meant to be used by file system health monitoring
13 sysadmin, start recovery) when a file system problem is detected.
16 for a monitoring tool to know a problem in the file system has happened.
20 early file system problem detection and reporting recovery tools.
22 When a file system operation fails, it is common for dozens of kernel
26 error that occurred for a file system since the last notification, and
[all …]
|
| D | rtc.rst | 7 works even with system power off. Such clocks will normally not track
8 the local time zone or daylight savings time -- unless they dual boot
9 with MS-Windows -- but will instead be set to Coordinated Universal Time
12 The newest non-PC hardware tends to just count seconds, like the time(2)
13 system call reports, but RTCs also very commonly represent time using
16 Linux has two largely-compatible userspace RTC API families you may
20 so it's not very portable to non-x86 systems.
23 supported by a wide variety of RTC chips on all systems.
35 Old PC/AT-Compatible driver: /dev/rtc
36 --------------------------------------
[all …]
|
| /Documentation/admin-guide/perf/ |
| D | starfive_starlink_pmu.rst | 7 clusters with an L3 memory system.
43 $ perf stat -a -e /starfive_starlink_pmu/cycles/ sleep 1
46 Attaching to a task is not supported, only system-wide counting is supported.
|
| /Documentation/driver-api/ |
| D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
60 * Double-channel
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
67 * Chip-select row
70 accessed. Common chip-select rows for single channel are 64 bits, for
[all …]
|
| /Documentation/arch/x86/ |
| D | buslock.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
11 - Tony Luck <tony.luck@intel.com>
18 the system locks the bus while the CPU accesses the two cache lines.
21 memory or any locked access to non-WB memory. This is typically thousands of
23 performance on other cores and brings the whole system to its knees.
32 --------------------------------------
38 ------------------------------------
50 +------------------+----------------------------+-----------------------+
52 +------------------+----------------------------+-----------------------+
[all …]
|
| /Documentation/devicetree/bindings/clock/sifive/ |
| D | fu540-prci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/clock/sifive/fu540-prci.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Paul Walmsley <paul.walmsley@sifive.com>
14 On the FU540 family of SoCs, most system-wide clock and reset integration
17 macros defined in include/dt-bindings/clock/sifive-fu540-prci.h.
26 const: sifive,fu540-c000-prci
33 - description: high frequency clock.
34 - description: RTL clock.
[all …]
|
| D | fu740-prci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/clock/sifive/fu740-prci.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Zong Li <zong.li@sifive.com>
12 - Paul Walmsley <paul.walmsley@sifive.com>
15 On the FU740 family of SoCs, most system-wide clock and reset integration
18 macros defined in include/dt-bindings/clock/sifive-fu740-prci.h.
27 const: sifive,fu740-c000-prci
34 - description: high frequency clock.
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm-master-stats.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/qcom/qcom,rpm-master-stats.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Konrad Dybcio <konradybcio@kernel.org>
16 (particularly around entering hardware-driven low power modes: XO shutdown
17 and total system-wide power collapse) are first made at Master-level, and
18 only then aggregated for the entire system.
21 our device has entered the desired low-power mode, how long it took to do so,
26 This scheme has been used on various SoCs in the 2013-2023 era, with some
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 6 as for older dialects such as the Common Internet File System (CIFS)
20 wide variety of systems. It also supports mounting to the cloud
25 file system function for SMB3 compliant servers, including advanced
27 POSIX compliance, secure per-user session establishment, encryption,
39 https://git.samba.org/?p=cifs-utils.git
43 git://git.samba.org/cifs-utils.git
|
| /Documentation/arch/m68k/ |
| D | buddha-driver.rst | 8 ------------------------------------------------------------------------
11 Buddha-part of the Catweasel Zorro-II version
21 product number: 0 (42 for Catweasel Z-II)
23 Rom-vector: $1000
25 The card should be a Z-II board, size 64K, not for freemem
26 list, Rom-Vektor is valid, no second Autoconfig-board on the
30 as the Amiga Kickstart does: The lower nibble of the 8-Bit
36 otherwise your chance is only 1:16 to find the board :-).
38 The local memory-map is even active when mapped to $e8:
41 $0-$7e Autokonfig-space, see Z-II docs.
[all …]
|
1234567