Home
last modified time | relevance | path

Searched refs:segmented (Results 1 – 6 of 6) sorted by relevance

/linux-4.4.14/net/caif/
Dcfrfml.c100 bool segmented; in cfrfml_receive() local
114 segmented = tmp & RFM_SEGMENTATION_BIT; in cfrfml_receive()
116 if (segmented) { in cfrfml_receive()
/linux-4.4.14/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt109 * Can be configured to be segmented. When not segmented, we can
110 specify the PE# for the entire window. When segmented, a window
123 as segmented.
188 - Non-segmented M64 window: A non-segmented M64 window is mapped entirely
191 - Single segmented M64 windows: A segmented M64 window could be used just
197 - Multiple segmented M64 windows: As usual, each window is split into 256
224 IODA supports 256 PEs, so segmented windows contain 256 segments, so if
279 set the PE# for the window. But if it's in a segmented M64 window, the
/linux-4.4.14/Documentation/networking/
Dtimestamping.txt198 coalescing sections of previously segmented buffers associated with
/linux-4.4.14/Documentation/
Dxillybus.txt268 Even though a non-segmented data stream is presented to the user at both
/linux-4.4.14/Documentation/usb/
DWUSB-Design-overview.txt354 Data buffers have to be segmented out before sending--so we send first a
/linux-4.4.14/arch/x86/
DKconfig2129 call. This is required to run 16-bit or segmented code such as