Searched +full:512 +full:- +full:bytes (Results 1 – 25 of 99) sorted by relevance
1234
| /Documentation/admin-guide/device-mapper/ |
| D | dm-ebs.rst | 2 dm-ebs
8 size. Its main purpose is to provide emulation of 512 byte sectors on
11 Supported emulated logical block sizes 512, 1024, 2048 and 4096.
17 ----------------
23 Full pathname to the underlying block-device,
24 or a "major:minor" device-number.
30 1, 2, 4, 8 sectors of 512 bytes supported.
36 2^N supported, e.g. 8 = emulate 8 sectors of 512 bytes = 4KiB.
42 Emulate 1 sector = 512 bytes logical block size on /dev/sda starting at
|
| D | dm-crypt.rst | 2 dm-crypt
5 Device-Mapper's "crypt" target provides transparent encryption of block devices
21 cipher[:keycount]-chainmode-ivmode[:ivopts]
25 aes-cbc-essiv:sha256
26 aes-xts-plain64
27 serpent-xts-plain64
36 capi:cipher_api_spec-ivmode[:ivopts]
40 capi:cbc(aes)-essiv:sha256
41 capi:xts(aes)-plain64
45 capi:gcm(aes)-random
[all …]
|
| D | dm-dust.rst | 1 dm-dust
27 With dm-dust, the user can use the "addbadblock" and "removebadblock"
31 This allows the pre-writing of test data and metadata prior to
35 ----------------
46 Block size in bytes
48 (minimum 512, maximum 1073741824, must be a power of 2)
51 ------------------
53 First, find the size (in 512-byte sectors) of the device to be used::
55 $ sudo blockdev --getsz /dev/vdb1
58 Create the dm-dust device:
[all …]
|
| D | dm-integrity.rst | 2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
9 writing the sector and the integrity tag must be atomic - i.e. in case of
12 To guarantee write atomicity, the dm-integrity target uses journal, it
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
20 disk encryption - if the attacker modifies the encrypted device, an I/O
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 1 What: /sys/kernel/debug/nx-crypto/*
7 These debugfs interfaces are built by the nx-crypto driver, built in
18 The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19 recorded here (the hcall will retry until -EBUSY goes away).
29 The total number of bytes encrypted using AES in any of the driver's
36 The total number of bytes hashed by the hardware using SHA-256.
39 The total number of SHA-256 operations submitted to the hardware.
42 The total number of bytes hashed by the hardware using SHA-512.
45 The total number of SHA-512 operations submitted to the hardware.
|
| D | debugfs-turris-mox-rwtm | 1 What: /sys/kernel/debug/turris-mox-rwtm/do_sign
9 device's OTP. The message must be exactly 64 bytes
10 (since this is intended for SHA-512 hashes).
11 (Read) The resulting signature, 136 bytes. This contains the
13 big-endian format.
|
| /Documentation/filesystems/ |
| D | sysv-fs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Xenix FS,
9 - SystemV/386 FS,
10 - Coherent FS.
18 mount [-r] -t sysv device mountpoint
22 -t sysv
23 -t xenix
24 -t coherent
30 - Coherent FS:
32 - The "free list interleave" n:m is currently ignored.
[all …]
|
| D | isofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 There is also an option of doing UTF-8 translations with the
24 utf8 Encode Unicode names in UTF-8 format. Default is no.
30 block=512 Set the block size for the disk to 512 bytes
31 block=1024 Set the block size for the disk to 1024 bytes
32 block=2048 Set the block size for the disk to 2048 bytes
36 map=off Do not map non-Rock Ridge filenames to lower case
37 map=normal Map non-Rock Ridge filenames to lower case
59 - http://www.y-adagio.com/
60 - ftp://ftp.ecma.ch/ecma-st/Ecma-119.pdf
[all …]
|
| D | romfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ROMFS - ROM File System
15 defunct) filesystems, compiled as module need more than 20000 bytes,
16 while romfs is less than a page, about 4000 bytes (assuming i586
26 As the name suggests, romfs could be also used (space-efficiently) on
27 various read-only media, like (E)EPROM disks if someone will have the
34 floppy drives can be loaded later if you use the "initrd"--initial
35 RAM disk--feature of the kernel. This would not be really news
52 is 32 bytes (this is an empty file, with a less than 16 character
53 name). The maximum overhead for any non-empty file is the header, and
[all …]
|
| D | affs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 in file names are case-insensitive, as they ought to be.
32 All of the above filesystems allow block sizes from 512 to 32K bytes.
33 Supported block sizes are: 512, 1024, 2048 and 4096 bytes. Larger blocks
75 Sets the blocksize to blksize. Valid block sizes are 512,
107 Amiga -> Linux:
111 - R maps to r for user, group and others. On directories, R implies x.
113 - W maps to w.
115 - E maps to x.
117 - D is ignored.
[all …]
|
| D | bfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 # mount -t bfs /dev/loop0 /mnt/stand
24 # losetup -d /dev/loop0
28 # mount -t bfs -o loop stand.img /mnt/stand
35 /proc/mounts. You will need to do it manually using "-d" switch of
48 # dd if=/dev/rdsk/c0b0t0d0sa of=stand.img bs=512
53 # od -Ad -tx4 stand.img | more
55 The first 4 bytes should be 0x1badface.
|
| D | qnx6.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 ------
32 size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
36 2^32 * 4096 bytes or 16TB
39 ---------------
61 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
65 Unused block pointers are always set to ~0 - regardless of root node,
76 device address, zeroing the last 3 bytes and then subtracting 0x1000 from
79 0x1000 is the size reserved for each superblock - regardless of the
83 ------
[all …]
|
| /Documentation/misc-devices/ |
| D | max6875.rst | 13 Datasheet: http://pdfserv.maxim-ic.com/en/ds/MAX6874-MAX6875.pdf
19 -----------
21 The Maxim MAX6875 is an EEPROM-programmable power-supply sequencer/supervisor.
23 It also provides 512 bytes of user EEPROM.
33 - vin gpi vout
43 -------------
45 eeprom - 512 bytes of user-defined EEPROM space.
49 ---------------
61 $ echo max6875 0x50 > /sys/bus/i2c/devices/i2c-0/new_device
65 The even-address instance is called 'max6875', the odd one is 'dummy'.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-block | 7 with 4KB physical sectors exposing 512-byte logical
9 indicates how many bytes the beginning of the device is
20 parameter indicates how many bytes the beginning of the
31 operation must not exceed this number of bytes.
35 power-of-two and atomic_write_unit_max_bytes may also be
37 This parameter - along with atomic_write_unit_min_bytes
38 and atomic_write_unit_max_bytes - will not be larger than
50 atomic_write_unit_min. This value must be a power-of-two.
60 be a power-of-two. This value will not be larger than
70 parameter specifies the size in bytes of the atomic boundary if
[all …]
|
| /Documentation/networking/ |
| D | smc-sysctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 autocorking_size - INTEGER
17 autocorking_size limits the maximum corked bytes that can be sent to
25 smcr_buf_type - INTEGER
27 SMC-R link group. Only for SMC-R.
33 - 0 - Use physically contiguous buffers
34 - 1 - Use virtually contiguous buffers
35 - 2 - Mixed use of the two types. Try physically contiguous buffers first.
38 smcr_testlink_time - INTEGER
39 How frequently SMC-R link sends out TEST_LINK LLC messages to confirm
[all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 11 force_ro Enforce read-only access even if write protect switch is off.
17 All attributes are read-only.
47 "erase_size" is the minimum size, in bytes, of an erase
51 always one 512 byte sector. For SD, "erase_size" is 512
52 if the card is block-addressed, 0 otherwise.
62 duration of the erase - which could be a several
76 For MMC, "preferred_erase_size" is the high-capacity
83 "preferred_erase_size" is in bytes.
|
| /Documentation/block/ |
| D | cmdline-partition.rst | 15 blkdevparts=<blkdev-def>[;<blkdev-def>]
16 <blkdev-def> := <blkdev-id>:<partdef>[,<partdef>]
17 <partdef> := <size>[@<offset>](part-name)
19 <blkdev-id>
24 partition size, in bytes, such as: 512, 1m, 1G.
29 "-" is used to denote all remaining space.
32 partition start address, in bytes.
37 (part-name)
48 'blkdevparts=mmcblk0:1G(data0),1G(data1),-;mmcblk0boot0:1m(boot),-(kernel)'
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
|
| /Documentation/admin-guide/auxdisplay/ |
| D | ks0108.rst | 7 :Date: 2006-10-27
19 ---------------------
25 ---------------------
30 :Webpage: -
31 :Device Webpage: -
39 :Memory size: 8 * 64 * 1 = 512 bytes
43 ---------
50 For example, check Documentation/admin-guide/auxdisplay/cfag12864b.rst
|
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------
9 .. list-table::
11 :header-rows: 1
13 * - Group 0 Padding
14 - ext4 Super Block
15 - Group Descriptors
16 - Reserved GDT Blocks
17 - Data Block Bitmap
18 - inode Bitmap
[all …]
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at25.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christian Eggers <ceggers@arri.de>
15 - pattern: "^eeprom@[0-9a-f]{1,2}$"
16 - pattern: "^fram@[0-9a-f]{1,2}$"
26 - items:
27 - enum:
28 - anvo,anv32e61w
29 - atmel,at25256B
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | amlogic,axg-fifo.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/amlogic,axg-fifo.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jerome Brunet <jbrunet@baylibre.com>
15 - enum:
16 - amlogic,axg-toddr
17 - amlogic,axg-frddr
18 - items:
19 - enum:
[all …]
|
| /Documentation/devicetree/bindings/net/can/ |
| D | st,stm32-bxcan.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/can/st,stm32-bxcan.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 - Dario Binacchi <dario.binacchi@amarulasolutions.com>
15 - $ref: can-controller.yaml#
20 - st,stm32f4-bxcan
22 st,can-primary:
32 st,can-secondary:
47 - description: transmit interrupt
[all …]
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Altera Triple-Speed Ethernet MAC driver
9 Copyright |copy| 2008-2014 Altera Corporation
11 This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
24 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP
31 Triple-Speed Ethernet instance is using an SGDMA or MSGDMA component. The
36 The SGDMA component is to be deprecated in the near future (over the next 1-2
46 Scatter-gather DMA is not supported by the SGDMA or MSGDMA at this time.
47 Scatter-gather DMA will be added to a future maintenance update to this
60 Device Drivers ---> Network device support ---> Ethernet driver support --->
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | mm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Complete virtual memory map with 4-level page tables
12 - Negative addresses such as "-23 TB" are absolute addresses in bytes, counted down
13 from the top of the 64-bit address space. It's easier to understand the layout
14 when seen both in absolute addresses and in distance-from-top notation.
16 For example 0xffffe90000000000 == -23 TB, it's 23 TB lower than the top of the
17 64-bit address space (ffffffffffffffff).
22 - "16M TB" might look weird at first sight, but it's an easier way to visualize size
24 It also shows it nicely how incredibly large 64-bit address space is.
32 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
[all …]
|
1234