HomeSort by relevance Sort by last modified time
    Searched full:bridge (Results 726 - 750 of 1211) sorted by null

<<21222324252627282930>>

  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/linux/
socket.h 165 #define AF_BRIDGE 7 /* Multiprotocol bridge */
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/linux/
socket.h 165 #define AF_BRIDGE 7 /* Multiprotocol bridge */
  /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/plat-mac/lib-scriptpackages/Netscape/
Standard_Suite.py 167 """unique ID - Window\xd5s unique ID (a bridge between WWW! suite window id\xd5s and standard AE windows) """
  /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/
plugin.xml 40 <!-- Disabled for now due to AWT/SWT bridge issue on Leopard.
  /external/bluetooth/bluedroid/stack/pan/
pan_main.c 110 ** Make bridge request to the host system if connection
404 /* Create bridge if the destination role is NAP */
407 PAN_TRACE_EVENT0 ("PAN requesting for bridge");
  /external/chromium_org/chrome/browser/ui/cocoa/
browser_window_controller.h 194 // Access the C++ bridge between the NSWindow and the rest of Chromium.
209 // Access the C++ bridge object representing the status bubble for the window.
212 // Access the C++ bridge object representing the location bar.
  /external/chromium_org/third_party/mesa/src/src/mesa/drivers/dri/i965/
brw_misc_state.c 401 /* According to the Sandy Bridge PRM, volume 2 part 1, pp326-327
459 /* According to the Sandy Bridge PRM, volume 2 part 1, pp326-327
918 * and this continues through Ironlake. The Sandy Bridge PRM, vol
gen7_wm_surface_state.c 109 /* From the Ivy Bridge PRM, Vol4 Part1 p76, "MCS Base Address":
454 /* From the Ivy bridge PRM, Vol4 Part1 p62 (Surface Type: Programming
486 /* From the Ivy bridge PRM, Vol4 Part1 p65 (Tiled Surface: Programming Notes):
  /external/llvm/lib/Support/
Host.cpp 268 // Not all Sandy Bridge processors support AVX (such as the Pentium
272 // Ivy Bridge:
274 // Not all Ivy Bridge processors support AVX (such as the Pentium
  /external/mesa3d/src/mesa/drivers/dri/i965/
brw_misc_state.c 401 /* According to the Sandy Bridge PRM, volume 2 part 1, pp326-327
459 /* According to the Sandy Bridge PRM, volume 2 part 1, pp326-327
918 * and this continues through Ironlake. The Sandy Bridge PRM, vol
gen7_wm_surface_state.c 109 /* From the Ivy Bridge PRM, Vol4 Part1 p76, "MCS Base Address":
454 /* From the Ivy bridge PRM, Vol4 Part1 p62 (Surface Type: Programming
486 /* From the Ivy bridge PRM, Vol4 Part1 p65 (Tiled Surface: Programming Notes):
  /external/wpa_supplicant_8/wpa_supplicant/
wpa_supplicant_i.h 99 * bridge_ifname - Optional bridge interface name
101 * If the driver interface (ifname) is included in a Linux bridge
102 * device, the bridge interface may need to be used for receiving EAPOL
  /hardware/ti/omap3/dspbridge/inc/
DSPNode.h 19 * DSP-BIOS Bridge driver support functions for TI OMAP processors.
21 * This is the header for the DSP/BIOS Bridge node module.
50 *! 13-Feb-2001 kc: DSP/BIOS Bridge name updates.
  /hardware/ti/omap3/dspbridge/libbridge/
DSPNode.c 4 * DSP-BIOS Bridge driver support functions for TI OMAP processors.
22 * This is the source for the DSP/BIOS Bridge API node module. The
77 /* ----------------------------------- DSP/BIOS Bridge */
DSPStrm.c 4 * DSP-BIOS Bridge driver support functions for TI OMAP processors.
21 * This is the source for the DSP/BIOS Bridge API stream module. The
77 /* ----------------------------------- DSP/BIOS Bridge */
  /hardware/ti/omap3/dspbridge/libbridge/inc/
DSPNode.h 4 * DSP-BIOS Bridge driver support functions for TI OMAP processors.
21 * This is the header for the DSP/BIOS Bridge node module.
50 *! 13-Feb-2001 kc: DSP/BIOS Bridge name updates.
  /external/chromium_org/third_party/mesa/src/src/mesa/drivers/dri/intel/
intel_mipmap_tree.c 218 /* From p82 of the Sandy Bridge PRM, dw3[1] of SURFACE_STATE ("Tiled
317 /* From the Ivy Bridge PRM, Vol4 Part1 p77 ("MCS Enable"):
412 /* In the Sandy Bridge PRM, volume 4, part 1, page 31, it says:
792 /* From the Ivy Bridge PRM, Vol4 Part1 p76, "MCS Base Address":
812 /* From the Ivy Bridge PRM, Vol 2 Part 1 p326:
    [all...]
  /external/mesa3d/src/mesa/drivers/dri/intel/
intel_mipmap_tree.c 218 /* From p82 of the Sandy Bridge PRM, dw3[1] of SURFACE_STATE ("Tiled
317 /* From the Ivy Bridge PRM, Vol4 Part1 p77 ("MCS Enable"):
412 /* In the Sandy Bridge PRM, volume 4, part 1, page 31, it says:
792 /* From the Ivy Bridge PRM, Vol4 Part1 p76, "MCS Base Address":
812 /* From the Ivy Bridge PRM, Vol 2 Part 1 p326:
    [all...]
  /external/wpa_supplicant_8/src/drivers/
driver_nl80211.c 1196 /* device has been added to bridge */
1198 wpa_printf(MSG_DEBUG, "nl80211: Add ifindex %u for bridge %s",
1238 /* device has been removed from bridge */
1241 wpa_printf(MSG_DEBUG, "nl80211: Remove ifindex %u for bridge "
    [all...]
  /frameworks/base/core/java/android/os/
ParcelFileDescriptor.java 239 final ListenerBridge bridge = new ListenerBridge(comm[1], handler.getLooper(), listener); local
240 bridge.start();
    [all...]
  /frameworks/base/docs/html/tools/testing/
testing_otheride.jd 54 <a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>
298 Android Debug Bridge (adb)</a> shell.
320 Android Debug Bridge (adb)</a>, you get more options for choosing the tests
  /art/runtime/mirror/
art_method.h 405 // May be compiled managed code or a bridge for invoking a native method.
  /dalvik/vm/
Jni.cpp 744 // Synchronization is usually provided by the JNI bridge,
803 * Point "method->nativeFunc" at the JNI bridge, and overload "method->insns"
819 DalvikBridgeFunc bridge = gDvmJni.useCheckJni ? dvmCheckCallJNIMethod : dvmCallJNIMethod; local
820 dvmSetNativeFunc(method, bridge, (const u2*) func);
    [all...]
  /device/asus/deb/self-extractors/
generate-packages.sh 86 system/bin/port-bridge \
  /device/asus/deb/
vendor_owner_info.txt 139 system/bin/port-bridge:qcom

Completed in 858 milliseconds

<<21222324252627282930>>