Searched full:254 (Results 1 – 25 of 29) sorted by relevance
12
| /Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 114 volumeGroup-snap: 0 2097152 snapshot 254:11 254:12 P 16 115 volumeGroup-base: 0 2097152 snapshot-origin 254:11 118 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real 119 brw------- 1 root root 254, 12 29 ago 18:15 /dev/mapper/volumeGroup-snap-cow 120 brw------- 1 root root 254, 13 29 ago 18:15 /dev/mapper/volumeGroup-snap 121 brw------- 1 root root 254, 10 29 ago 18:14 /dev/mapper/volumeGroup-base 144 volumeGroup-base: 0 2097152 snapshot-merge 254:11 254:12 P 16 147 brw------- 1 root root 254, 11 29 ago 18:15 /dev/mapper/volumeGroup-base-real 148 brw------- 1 root root 254, 12 29 ago 18:16 /dev/mapper/volumeGroup-base-cow 149 brw------- 1 root root 254, 10 29 ago 18:16 /dev/mapper/volumeGroup-base
|
| D | vdo-design.rst | 18 deduplication rates of 254:1, i.e. up to 254 copies of a given 4K block can
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-qmi | 32 Write a number ranging from 1 to 254 to add a qmap mux 49 Write a number ranging from 1 to 254 to delete a previously
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 36 brw------- 1 root root 254, 0 Jul 28 13:37 /dev/mapper/swap0 106 echo 254:0 > /sys/power/resume 127 device if we don't want to resume. The line "echo 254:0 > /sys/power/resume"
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | mti,gic.yaml | 62 maximum: 254 64 maximum: 254
|
| /Documentation/mm/ |
| D | zsmalloc.rst | 153 254 4096 0 .. 0 0 0 0 1 0 158 to size class #254, which stores each object in its own physical page (objects 175 254 4096 0 .. 0 0 0 0 1 0 202 254 4096 0 .. 0 0 0 0 1 0
|
| /Documentation/arch/powerpc/ |
| D | hvcs.rst | 173 254:0 176 254:1 179 254:2 182 254:3 192 mknod /dev/hvcs0 c 254 0 193 mknod /dev/hvcs1 c 254 1 194 mknod /dev/hvcs2 c 254 2 195 mknod /dev/hvcs3 c 254 3
|
| /Documentation/devicetree/bindings/thermal/ |
| D | generic-adc-thermal.yaml | 76 118000 254
|
| /Documentation/userspace-api/media/v4l/ |
| D | colorspaces-defs.rst | 168 mapped to [0…255] (with possible clipping to [1…254] to avoid the 170 [0…255] (with possible clipping to [1…254] to avoid the 0x00 and
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 165 halted processing. Notice that descrs 0 through 254 are all marked 166 "full", while descr 254 and 255 are empty. (The "Last 1 descrs" is 167 descr 254, since tail was at 255.) Thus, the system is deadlocked,
|
| /Documentation/devicetree/bindings/dma/ |
| D | qcom,gpi.yaml | 109 <GIC_SPI 254 IRQ_TYPE_LEVEL_HIGH>,
|
| /Documentation/devicetree/bindings/net/ |
| D | qcom-emac.txt | 110 interrupts = <0 254 1>;
|
| /Documentation/scsi/ |
| D | g_NCR5380.rst | 21 If the irq parameter is 254 or is omitted entirely, the driver will probe
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_osd.rst | 154 | opacity=1..254: pixel opacity as specified in header 169 | R,G,B, and a opacity value: 0->transparent, 1..254->mix,
|
| /Documentation/hwmon/ |
| D | adm9240.rst | 112 - fan_min set to register value 254 which corresponds
|
| D | asc7621.rst | 215 4-254 Ignored.
|
| /Documentation/trace/ |
| D | histogram.rst | 785 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 975] } hitcount: … 786 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 3204] } hitcount: … 787 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 2888] } hitcount: … 788 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 3003] } hitcount: … 789 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 2873] } hitcount: … 790 …{ id: sys_inotify_add_watch [254], common_pid: gmain [ 3196] } hitcount: … 2806 { lat: 254, common_pid: 2036 } hitcount: 8 2807 { lat: 254, common_pid: 2043 } hitcount: 3 2808 { lat: 254, common_pid: 2041 } hitcount: 1 2809 { lat: 254, common_pid: 2042 } hitcount: 1 [all …]
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | bug-hunting.rst | 329 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 151 at index 0 and ranging to 254) for this HMC ID. The driver then does an
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | bug-hunting.rst | 332 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
|
| /Documentation/networking/ |
| D | arcnet-hardware.rst | 348 software). Since it's only 8 bits, you can only have 254 ARCnet cards 882 1 1 1 1 1 1 1 0 | FE | 254 1212 switches. Use an address from 1 to 254 1412 1 1 1 1 1 1 1 0 | FE | 254 1621 1 1 1 1 1 1 1 0 | FE | 254 2544 1 1 1 1 1 1 1 0 | FE | 254 2740 1 1 1 1 1 1 1 0 | FE | 254 2920 1 1 1 1 1 1 1 0 | FE | 254 3145 1 1 1 1 1 1 1 0 | FE | 254 |
|
| /Documentation/driver-api/mtd/ |
| D | nand_ecc.rst | 51 byte 254: bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 rp0 rp3 rp5 ... rp15 78 - rp0 is the parity of all even bytes (0, 2, 4, 6, ... 252, 254)
|
| /Documentation/filesystems/caching/ |
| D | netfs-api.rst | 107 should begin with the name of the filesystem and should be no longer than 254
|
| /Documentation/admin-guide/ |
| D | bug-hunting.rst | 368 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
|
| D | devices.txt | 380 243-254 Reserved for local use 1963 254 = /dev/evms/EVMSname2 Second EVMS native device 3008 234-254 char RESERVED FOR DYNAMIC ASSIGNMENT 3010 take numbers starting from 254 and downward. 3012 240-254 block LOCAL/EXPERIMENTAL USE 3082 once the 234-254 range is full.
|
12