Searched full:stand (Results 1 – 25 of 311) sorted by relevance
12345678910>>...13
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | bfs.rst | 7 The BFS filesystem is used by SCO UnixWare OS for the /stand slice, which
11 In order to access /stand partition under Linux you obviously need to
17 # losetup /dev/loop0 stand.img
18 # mount -t bfs /dev/loop0 /mnt/stand
20 where stand.img is a file containing the image of BFS filesystem.
28 # mount -t bfs -o loop stand.img /mnt/stand
44 look for the slice with tag "STAND", which is usually slice 10. With this
47 # umount /stand
48 # dd if=/dev/rdsk/c0b0t0d0sa of=stand.img bs=512
53 # od -Ad -tx4 stand.img | more
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | bfs.rst | 7 The BFS filesystem is used by SCO UnixWare OS for the /stand slice, which
11 In order to access /stand partition under Linux you obviously need to
17 # losetup /dev/loop0 stand.img
18 # mount -t bfs /dev/loop0 /mnt/stand
20 where stand.img is a file containing the image of BFS filesystem.
28 # mount -t bfs -o loop stand.img /mnt/stand
44 look for the slice with tag "STAND", which is usually slice 10. With this
47 # umount /stand
48 # dd if=/dev/rdsk/c0b0t0d0sa of=stand.img bs=512
53 # od -Ad -tx4 stand.img | more
|
| /kernel/linux/linux-5.10/fs/bfs/ |
| D | Kconfig | 8 files during the boot process. It is usually mounted under /stand
9 and corresponds to the slice marked as "STAND" in the UnixWare
11 on your /stand slice from within Linux. You then also need to say Y
|
| /kernel/linux/linux-6.6/fs/bfs/ |
| D | Kconfig | 9 files during the boot process. It is usually mounted under /stand
10 and corresponds to the slice marked as "STAND" in the UnixWare
12 on your /stand slice from within Linux. You then also need to say Y
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 5 This file is provided by the iio-trig-sysfs stand-alone trigger
26 This attribute is provided by the iio-trig-sysfs stand-alone
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 5 This file is provided by the iio-trig-sysfs stand-alone trigger
26 This attribute is provided by the iio-trig-sysfs stand-alone
|
| /kernel/linux/linux-5.10/sound/firewire/bebob/ |
| D | bebob_yamaha_terratec.c | 12 * Yamaha GO44 is not designed to be used as stand-alone mixer. So any streams
16 * way to recover this state. GO46 is better for stand-alone mixer.
|
| /kernel/linux/linux-6.6/sound/firewire/bebob/ |
| D | bebob_yamaha_terratec.c | 12 * Yamaha GO44 is not designed to be used as stand-alone mixer. So any streams
16 * way to recover this state. GO46 is better for stand-alone mixer.
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/ |
| D | ia_css_acc_types.h | 51 IA_CSS_ACC_STANDALONE, /** Stand-alone acceleration */
400 /* Structure describing the SP binary of a stand-alone accelerator.
415 * This descriptor descibes either SP code (stand-alone), or
443 int8_t sp_progname[]; **< SP program name, stand-alone only
444 uint8_t sp_code[]; **< SP blob, stand-alone only
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_acc_types.h | 50 IA_CSS_ACC_STANDALONE, /** Stand-alone acceleration */
404 /* Structure describing the SP binary of a stand-alone accelerator.
419 * This descriptor descibes either SP code (stand-alone), or
447 int8_t sp_progname[]; **< SP program name, stand-alone only
448 uint8_t sp_code[]; **< SP blob, stand-alone only
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | perf-sched.txt | 34 workload captured via perf sched record. Columns stand for
35 individual CPUs, and the two-letter shortcuts stand for tasks that
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-sched.txt | 34 workload captured via perf sched record. Columns stand for
35 individual CPUs, and the two-letter shortcuts stand for tasks that
|
| /kernel/linux/linux-6.6/Documentation/accel/ |
| D | introduction.rst | 11 These devices can be either stand-alone ASICs or IP blocks inside an SoC/GPU.
24 type of device can be stand-alone or an IP inside a SoC or a GPU. It will
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | README.rst | 150 Stand-alone build
154 mirror of the mainline's version of libbpf for a stand-alone build.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/can/ |
| D | holt_hi311x.txt | 1 * Holt HI-311X stand-alone CAN controller device tree bindings
|
| D | microchip,mcp251x.txt | 1 * Microchip MCP251X stand-alone CAN controller device tree bindings
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/ |
| D | holt_hi311x.txt | 1 * Holt HI-311X stand-alone CAN controller device tree bindings
|
| D | microchip,mcp251x.txt | 1 * Microchip MCP251X stand-alone CAN controller device tree bindings
|
| /kernel/linux/linux-5.10/tools/memory-model/litmus-tests/ |
| D | MP+polocks.litmus | 7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
|
| D | MP+porevlocks.litmus | 7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
|
| /kernel/linux/linux-6.6/tools/memory-model/litmus-tests/ |
| D | MP+porevlocks.litmus | 7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
|
| D | MP+polocks.litmus | 7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
|
| /kernel/linux/linux-6.6/Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 135 Stand-alone build
139 mirror of the mainline's version of libbpf for a stand-alone build.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ptp/ |
| D | timestamper.txt | 5 can simply attach their interface directly to the PHY instance), stand
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ptp/ |
| D | timestamper.txt | 5 can simply attach their interface directly to the PHY instance), stand
|
12345678910>>...13