Searched full:fit (Results 1 – 25 of 3082) sorted by relevance
12345678910>>...124
| /kernel/linux/linux-6.6/arch/mips/generic/ |
| D | Kconfig | 20 comment "Legacy (non-UHI/non-FIT) Boards"
51 comment "FIT/UHI Boards"
57 from Imagination Technologies in the FIT kernel image. You should
65 from Imagination Technologies in the FIT kernel image.
71 National Instruments in the FIT kernel image.
77 from Imagination Technologies in the FIT kernel image.
84 from Microsemi in the FIT kernel image.
92 from Microsemi in the FIT kernel image.
100 from Microsemi in the FIT kernel image.
108 from Microsemi in the FIT kernel image.
|
| /kernel/linux/linux-5.10/arch/mips/generic/ |
| D | Kconfig | 20 comment "Legacy (non-UHI/non-FIT) Boards"
46 comment "FIT/UHI Boards"
52 from Imagination Technologies in the FIT kernel image. You should
60 National Instruments in the FIT kernel image.
66 from Imagination Technologies in the FIT kernel image.
73 from Microsemi in the FIT kernel image.
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 8 depthcharge_ bootloader. Depthcharge_ expects the OS to be packaged as a `FIT
10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and
34 Depthcharge_ will look through all device trees in the `FIT Image`_ trying to
36 through all device trees in the `FIT Image`_ trying to find the one that
69 .. _`FIT Image`: https://doc.coreboot.org/lib/payloads/fit.html
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/aspeed/ |
| D | facebook-bmc-flash-layout-128.dtsi | 35 * FIT image: 119 MB.
37 fit@100000 {
39 label = "fit";
|
| D | facebook-bmc-flash-layout.dtsi | 19 fit@80000 {
21 label = "fit";
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 27 software-hardware interface to be set up. They should not have a natural fit
28 to any existing kernel subsystem and not be a good fit for an operating system,
33 from userspace will likely be a good fit for using GPIO lines from userspace as
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 27 software-hardware interface to be set up. They should not have a natural fit
28 to any existing kernel subsystem and not be a good fit for an operating system,
33 from userspace will likely be a good fit for using GPIO lines from userspace as
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | facebook-bmc-flash-layout.dtsi | 19 fit@80000 {
21 label = "fit";
|
| /kernel/linux/linux-5.10/arch/m68k/ |
| D | Kconfig.bus | 27 expansion cards that do not fit in the Zorro slots but fit in e.g.
|
| /kernel/linux/linux-6.6/arch/m68k/ |
| D | Kconfig.bus | 27 expansion cards that do not fit in the Zorro slots but fit in e.g.
|
| /kernel/linux/linux-6.6/drivers/ata/pata_parport/ |
| D | fit2.c | 11 * Newer models of the FIT products use an enhanced protocol.
30 * NB: The FIT adapter does not appear to use the control registers.
113 dev_info(&pi->dev, "FIT 2000 adapter at 0x%x, delay %d\n", in fit2_log_adapter()
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| D | fit2.c | 11 Newer models of the FIT products use an enhanced protocol.
33 NB: The FIT adapter does not appear to use the control registers.
118 { printk("%s: fit2 %s, FIT 2000 adapter at 0x%x, delay %d\n", in fit2_log_adapter()
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-targets.rst | 40 - Bounds of the crop rectangle. All valid crop rectangles fit inside
62 - Bounds of the compose rectangle. All valid compose rectangles fit
|
| D | subdev-image-processing-crop.svg | 45 fit-margin-top="0"
46 fit-margin-left="0"
47 fit-margin-right="0"
48 fit-margin-bottom="0"
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-targets.rst | 46 - Bounds of the crop rectangle. All valid crop rectangles fit inside
68 - Bounds of the compose rectangle. All valid compose rectangles fit
|
| D | subdev-image-processing-crop.svg | 45 fit-margin-top="0"
46 fit-margin-left="0"
47 fit-margin-right="0"
48 fit-margin-bottom="0"
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | atmel-smc.c | 64 * not fit in the register field. in atmel_smc_cs_encode_ncycles()
90 * Returns -EINVAL if shift is invalid, -ERANGE if ncycles does not fit in
132 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
171 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
210 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | atmel-smc.c | 64 * not fit in the register field. in atmel_smc_cs_encode_ncycles()
90 * Returns -EINVAL if shift is invalid, -ERANGE if ncycles does not fit in
132 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
171 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
210 * Returns -EINVAL if @shift is invalid, -ERANGE if @ncycles does not fit in
|
| /kernel/linux/linux-6.6/net/core/ |
| D | gso.c | 244 * skb_gso_validate_network_len - Will a split GSO skb fit into a given MTU?
249 * skb_gso_validate_network_len validates if a given skb will fit a
260 * skb_gso_validate_mac_len - Will a split GSO skb fit in a given length?
265 * skb_gso_validate_mac_len validates if a given skb will fit a wanted
|
| /kernel/linux/linux-6.6/fs/xfs/libxfs/ |
| D | xfs_dir2_sf.c | 162 * directory and a header for the sf directory, if it will fit it the
163 * space currently present in the inode. If it won't fit, the output
254 * Caller has already checked that it will fit, and built us a header.
361 * Convert to block form if necessary, if the new entry won't fit.
406 * Won't fit as shortform any more (due to size), in xfs_dir2_sf_addname()
413 * Just checking or no space reservation, it doesn't fit. in xfs_dir2_sf_addname()
503 * Find a hole that the new entry will fit into, and copy
594 * Decide if the new entry will fit at all.
595 * If it will fit, pick between adding the new entry to the end (easy)
597 * Return 0 (won't fit), 1 (easy), 2 (hard).
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | rcu_node-lock.svg | 72 fit-margin-top="5"
73 fit-margin-right="5"
74 fit-margin-left="5"
75 fit-margin-bottom="5" />
|
| /kernel/linux/linux-6.6/Documentation/RCU/Design/Memory-Ordering/ |
| D | rcu_node-lock.svg | 72 fit-margin-top="5"
73 fit-margin-right="5"
74 fit-margin-left="5"
75 fit-margin-bottom="5" />
|
| /kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/ |
| D | multi-display-hdcp-mpo.svg | 70 fit-margin-top="0"
71 fit-margin-left="0"
72 fit-margin-right="0"
73 fit-margin-bottom="0" />
|
| /kernel/linux/linux-5.10/drivers/pinctrl/mediatek/ |
| D | mtk-eint.h | 62 /* Used to fit into various EINT device */
66 /* Used to fit into various pinctrl device */
|
| /kernel/linux/linux-6.6/Documentation/filesystems/nfs/ |
| D | reexport.rst | 40 The result must fit into the RFC-mandated filehandle size limits:
51 NFSv2 if the original server gives you filehandles that fit in 10
72 All will therefore fit in an NFSv3 or NFSv4 filehandle after reexport,
|
12345678910>>...124
