Searched full:features (Results 1 – 25 of 526) sorted by relevance
12345678910>>...22
| /Documentation/networking/ |
| D | netdev-features.rst | 4 Netdev features mess and how to get out from it alive
16 verbatim. Today's devices add multiple features and bugs (read: offloads)
19 are commonly referred to as netdev features in Linux kernel world.
21 There are currently three sets of features relevant to the driver, and
24 1. netdev->hw_features set contains features whose state may possibly
29 2. netdev->features set contains features which are currently enabled
33 3. netdev->vlan_features set contains features whose state is inherited
34 by child VLAN devices (limits netdev->features set). This is currently
45 Part II: Controlling enabled features
48 When current feature set (netdev->features) is to be changed, new set
[all …]
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 3 (skiboot/doc/device-tree/ibm,powerpc-cpu-features/binding.txt)
5 There is more complete overview and documentation of features in that
9 ibm,powerpc-cpu-features binding
12 This device tree binding describes CPU features available to software, with
16 found in design.txt, which also points to documentation of specific features.
19 /cpus/ibm,powerpc-cpu-features node binding
22 Node: ibm,powerpc-cpu-features
26 The node name must be "ibm,powerpc-cpu-features".
38 Definition: "ibm,powerpc-cpu-features"
66 /cpus/ibm,powerpc-cpu-features/example-feature node bindings
[all …]
|
| /Documentation/devicetree/bindings/arm/mrvl/ |
| D | tauros2.txt | 5 - marvell,tauros2-cache-features : Specify the features supported for the
7 The features including
16 marvell,tauros2-cache-features = <0x3>;
|
| /Documentation/driver-api/firmware/ |
| D | core.rst | 2 Firmware API core features
5 The firmware API has a rich set of core features available. This section
6 documents these features.
|
| D | other_interfaces.rst | 18 Some features of the Intel Stratix10 SoC require a level of privilege
19 higher than the kernel is granted. Such secure features include
21 at Exception Level 1 (EL1), access to the features requires
25 drivers to request access to the secure features. The requests are queued
|
| /Documentation/filesystems/ |
| D | incfs.rst | 15 Features chapter
18 /sys/fs/incremental-fs/features/corefs
21 /sys/fs/incremental-fs/features/v2
22 Reads 'supported'. Present if all v2 features of incfs are supported. These
35 /sys/fs/incremental-fs/features/zstd
38 /sys/fs/incremental-fs/features/bugfix_throttling
|
| D | btrfs.rst | 8 features while focusing on fault tolerance, repair and easy administration.
12 The main Btrfs features include:
33 questions, use cases, mount options, comprehensible changelogs, features,
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 18 5. New features must default to off (userspace should explicitly request them).
21 6. New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2
36 11. New guest visible features must either be documented in a hardware manual
39 12. Features must be robust against reset and kexec - for example, shared
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 10 # of the recursive limitation is that drivers cannot negate features from other
15 # annotate this, all features that driver A selects cannot now be negated by
19 # core requirements are not carefully synced, as drivers evolve features
24 # describes a simple driver core layout of example features a kernel might
43 # problem consisted on matching semantics with newly introduced features.
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 13 LIRC_GET_FEATURES - Get the underlying hardware device's features
20 ``int ioctl(int fd, LIRC_GET_FEATURES, __u32 *features)``
28 ``features``
29 Bitmask with the LIRC features.
34 Get the underlying hardware device's features. If a driver does not
35 announce support of certain features, calling of the corresponding ioctls
38 LIRC features
|
| /Documentation/x86/ |
| D | cpuinfo.rst | 13 an X86_FEATURE_* defined. These flags represent hardware features as
14 well as software features.
29 shows features which the kernel supports. For a full list of CPUID flags
45 b: Flags can be from scattered CPUID-based features.
47 Hardware features enumerated in sparsely populated CPUID leaves get
55 [EAX=7, ECX=0] has 30 features and is dense, but the CPUID leaf [EAX=7, EAX=1]
60 c: Flags can be created synthetically under certain conditions for hardware features.
62 Examples of conditions include whether certain features are present in
64 conditions are met, the features are enabled by the set_cpu_cap or
70 d: Flags can represent purely software features.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-incfs | 1 What: /sys/fs/incremental-fs/features/corefs
6 What: /sys/fs/incremental-fs/features/v2
9 Description: Reads 'supported'. Present if all v2 features of incfs are
12 What: /sys/fs/incremental-fs/features/zstd
18 What: /sys/fs/incremental-fs/features/bugfix_throttling
|
| D | sysfs-class-iommu-amd-iommu | 9 What: /sys/class/iommu/<iommu>/amd-iommu/features
14 Extended features of the IOMMU. Format: %llx
|
| /Documentation/gpu/ |
| D | vkms.rst | 44 Add Plane Features
47 There's lots of plane features we could add support for:
68 features, we could write back the entire composited frame, and expose it as:
82 features. Also, this allows compositors to test whether they work correctly on
86 Output Features
109 This needs a bunch of features (plane compositing, multiple outputs, ...)
|
| /Documentation/arm64/ |
| D | elf_hwcaps.rst | 11 Some hardware or software features are only available on some CPU
14 kernel exposes the presence of these features to userspace through a set
17 Userspace software can test for features by acquiring the AT_HWCAP or
34 Features cannot be probed reliably through other means. When a feature
43 The majority of hwcaps are intended to indicate the presence of features
59 Other hwcaps may indicate the presence of features which cannot be
105 These ID registers may imply the availability of features.
|
| /Documentation/networking/device_drivers/fddi/ |
| D | skfp.rst | 163 New features:
170 New features:
175 New features:
191 New features:
197 New features:
221 New features:
233 New features:
|
| /Documentation/devicetree/bindings/arm/ |
| D | microchip,sparx5.yaml | 17 features such as advanced TCAM-based VLAN and QoS processing
35 gigabit switch with 20 SFP ports. It features spi-nor and
42 gigabit switch with 48+4 Cu ports. It features spi-nor and
|
| /Documentation/networking/device_drivers/ethernet/neterion/ |
| D | vxge.rst | 10 2) Features supported
29 inside the ASIC. Features like independent hw reset, statistics, bandwidth/
33 (See below for a complete list of features supported for both IPv4 and IPv6)
35 2. Features supported
|
| D | s2io.rst | 12 - 3. Features supported
21 Xframe II PCI-X 2.0 adapters. It supports several features
23 See below for complete list of features.
25 All features are supported for both IPv4 and IPv6.
53 3. Features supported
|
| /Documentation/admin-guide/cifs/ |
| D | todo.rst | 7 A Partial List of Missing Features
12 is a partial list of the known problems and missing features:
14 a) SMB3 (and SMB3.1.1) missing optional features:
22 but additional features would be supportable by the protocol).
56 k) Add tools to take advantage of more smb3 specific ioctls and features
|
| /Documentation/vm/ |
| D | index.rst | 9 User guides for MM features
13 various features of the Linux memory management
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 8 provides support for computer/IT management and security features.
15 a host application and the Intel ME features.
32 features allow only a single instance.
37 Because some of the Intel ME features can change the system
47 virtual channels with an Intel ME feature. Not all features support
|
| /Documentation/hwmon/ |
| D | ibmaem.rst | 31 The v1 AEM interface has a simple set of features to monitor energy use. There
40 Special Features
|
| /Documentation/powerpc/ |
| D | ptrace.rst | 5 GDB intends to support the following hardware debug features of BookE
21 Query for GDB to discover the hardware debug features. The main info to
39 uint64_t features; /* bitmask of the individual flags */
42 features will have bits indicating whether there is support for::
|
| /Documentation/fpga/ |
| D | dfl.rst | 22 device MMIO space to provide an extensible way of adding features. Software can
23 walk through these predefined data structures to enumerate FPGA features:
24 FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
62 Private Features represent sub features of the FIU and AFU. They could be
63 various function blocks with different IDs, but all private features which
72 This Device Feature List provides a way of linking features together, it's
133 to the accelerator and exposes features such as reset and debug. Each FPGA
201 (FPGA base region), discover feature devices and their private features from the
204 also abstracts operations for the private features and exposes common ops to
216 provides the key features for FPGA management, including:
[all …]
|
12345678910>>...22