| /dports/devel/boost-docs/boost_1_72_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/databases/xtrabackup/boost_1_59_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/databases/percona57-pam-for-mysql/boost_1_59_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/databases/mysqlwsrep57-server/boost_1_59_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/databases/percona57-server/boost_1_59_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/databases/percona57-client/boost_1_59_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/devel/boost-libs/boost_1_72_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/devel/hyperscan/boost_1_75_0/libs/fusion/doc/ |
| H A D | organization.qbk | 11 The library is organized into layers of modules, with each module addressing a particular
84 If, for example, you want to use `list`, depending on the granularity that
|
| /dports/www/firefox/firefox-99.0/docs/nspr/ |
| H A D | about_nspr.rst | 97 regard to whether the addressing technology is IPv4 or IPv6.
110 but expects clients to deal with that issue. The *granularity* of the
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/driver-api/ |
| H A D | vfio.rst | 47 meant for translation (ie. solving the addressing problems of devices
52 This isolation is not always at the granularity of a single device
68 granularity, any system is susceptible to reduced granularity. The
73 While the group is the minimum granularity that must be used to
75 granularity. In IOMMUs which make use of page tables, it may be
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/driver-api/ |
| H A D | vfio.rst | 47 meant for translation (ie. solving the addressing problems of devices
52 This isolation is not always at the granularity of a single device
68 granularity, any system is susceptible to reduced granularity. The
73 While the group is the minimum granularity that must be used to
75 granularity. In IOMMUs which make use of page tables, it may be
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/driver-api/ |
| H A D | vfio.rst | 47 meant for translation (ie. solving the addressing problems of devices
52 This isolation is not always at the granularity of a single device
68 granularity, any system is susceptible to reduced granularity. The
73 While the group is the minimum granularity that must be used to
75 granularity. In IOMMUs which make use of page tables, it may be
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/core-api/ |
| H A D | dma-api-howto.rst | 149 DMA addressing capabilities
153 addressing. For a 64-bit capable device, this needs to be increased, and for
157 64-bit addressing (DAC) for all transactions. And at least one platform (SGI
162 your devices DMA addressing capabilities.
206 The standard 64-bit addressing device would do something like this::
213 If the device only supports 32-bit addressing for descriptors in the
231 dev_warn(dev, "mydev: 24-bit DMA addressing not available\n");
243 DMA addressing limitations, you may wish to probe each mask and
274 and thus retaining the 16MB DMA addressing limitations of ISA.
579 into one (e.g. if DMA mapping is done with PAGE_SIZE granularity, any
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/core-api/ |
| H A D | dma-api-howto.rst | 149 DMA addressing capabilities
153 addressing. For a 64-bit capable device, this needs to be increased, and for
157 64-bit addressing (DAC) for all transactions. And at least one platform (SGI
162 your devices DMA addressing capabilities.
206 The standard 64-bit addressing device would do something like this::
213 If the device only supports 32-bit addressing for descriptors in the
231 dev_warn(dev, "mydev: 24-bit DMA addressing not available\n");
243 DMA addressing limitations, you may wish to probe each mask and
274 and thus retaining the 16MB DMA addressing limitations of ISA.
579 into one (e.g. if DMA mapping is done with PAGE_SIZE granularity, any
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/core-api/ |
| H A D | dma-api-howto.rst | 149 DMA addressing capabilities
153 addressing. For a 64-bit capable device, this needs to be increased, and for
157 64-bit addressing (DAC) for all transactions. And at least one platform (SGI
162 your devices DMA addressing capabilities.
206 The standard 64-bit addressing device would do something like this::
213 If the device only supports 32-bit addressing for descriptors in the
231 dev_warn(dev, "mydev: 24-bit DMA addressing not available\n");
243 DMA addressing limitations, you may wish to probe each mask and
274 and thus retaining the 16MB DMA addressing limitations of ISA.
579 into one (e.g. if DMA mapping is done with PAGE_SIZE granularity, any
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/styleguide/web/ |
| H A D | web.md | 112 amount of addressing (adding an ID just to wire up event handling).
223 * If time lengths are less than 1 second, use millisecond granularity.
227 * Use two colons when addressing a pseudo-element (i.e. `::after`, `::before`,
|
| /dports/math/gemmlowp/gemmlowp-dc69acd/doc/ |
| H A D | packing.md | 70 // give up random-access addressing, and instead content ourselves
98 We still need some random access at larger scales (with high granularity), which
|
| /dports/www/qt5-webengine/qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/styleguide/web/ |
| H A D | web.md | 122 the amount of addressing (adding an ID just to wire up event handling).
233 * If time lengths are less than 1 second, use millisecond granularity.
237 * Use two colons when addressing a pseudo-element (i.e. `::after`, `::before`,
|
| /dports/devel/p5-Workflow/Workflow-1.59/ |
| H A D | Changes.md | 57 …kflow/pull/119) adds capability of configuring custom workflow classes addressing issue [#107](htt…
61 …fixed via PR [#122](https://github.com/jonasbn/perl-workflow/pull/122) addressing issue [#121](htt…
71 …tion()` via PR [#56](https://github.com/jonasbn/perl-workflow/pull/56) addressing issue [#54](http…
73 …made public PR [#57](https://github.com/jonasbn/perl-workflow/pull/57) addressing issue [#55](http…
81 - This release changes logging granularity: instead of using the Log::Log4perl root logger for all …
106 - PR [#85](https://github.com/jonasbn/perl-workflow/pull/85) addressing bug with use of database fi…
110 - Improved test coverage, addressing issue [#36](https://github.com/jonasbn/perl-workflow/issues/36…
144 …SAFE_INC`, PR [#53](https://github.com/jonasbn/perl-workflow/pull/53), addressing issue [#52](http…
174 - Minor feature addition addressing issue [#5](https://github.com/jonasbn/perl-workflow/issues/5) w…
202 - Patch from Oliver Welter, addressing issue with greedy join handling error message, ref: PR [#16]…
|
| /dports/devel/arduino-avrdude/avrdude-6.3/ |
| H A D | ChangeLog-2011 | 142 granularity requirements).
374 bug #31779: Add support for addressing usbtinyisp with -P option
419 * avrdude.conf.in (ATtiny4313): Fix flash addressing bits for manual ISP
|
| /dports/cad/PrusaSlicer/PrusaSlicer-version_2.3.3/src/avrdude/ |
| H A D | ChangeLog-2011 | 142 granularity requirements).
374 bug #31779: Add support for addressing usbtinyisp with -P option
419 * avrdude.conf.in (ATtiny4313): Fix flash addressing bits for manual ISP
|
| /dports/devel/avrdude/avrdude-6.4/ |
| H A D | ChangeLog-2011 | 142 granularity requirements).
374 bug #31779: Add support for addressing usbtinyisp with -P option
419 * avrdude.conf.in (ATtiny4313): Fix flash addressing bits for manual ISP
|
| /dports/devel/asl/asl-current/doc_EN/ |
| H A D | as.tex | 2462 addressing:
3936 ST7/STM8, AVR (only if code segment granularity is 8 bits)}
9075 addressing.
10186 The \tty{Gran} field describes the code's ''granularity'', i.e. the size of
10191 address refers to the granularity, the \tty{Length} value is always
10194 granularity of 1, however \$303 for a granularity of 4! Granularities
10209 type, the target segment is fixed to \tty{CODE} and the granularity is
10415 Address specifications always relate to the granularity of the
13695 granularity is 1. The \tty{ListGran} entry therefore has to be set to
13766 to the current segment's granularity.}
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/mlir/docs/Dialects/ |
| H A D | Vector.md | 210 dialects at arbitrary levels of granularity and lends itself favorably to
223 granularity.
397 1. Loops around `vector` values are indirect addressing of vector values, they
404 3. HW may support >1-D vectors with intrinsics for indirect addressing within
|