/barrelfish-2018-10-04/lib/usb/ |
H A D | usb_device.c | 58 * \param iface_index the index of the interface 76 * \brief processes a configuration descriptor and allocates the interface 80 * \param iface the interface number 95 /* this is an parameter override, when setting an alternate interface */ 129 struct usb_interface *interface; local 141 /* get the next interface */ 142 interface = dev->ifaces + iface_ps.iface_index; 163 /* initialize the interface */ 164 assert(interface != NULL); 165 interface 340 struct usb_interface *interface, *ret = NULL; local [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
H A D | umsforeign.tex | 36 for Quintus or SICStus Prolog, or to interface 41 Since their external interface is incompatible with the {\eclipse} one, 43 interface into the foreign one, by defining a new C function 44 for every C function defined in the foreign interface. 52 This predicate generates a file {\it interface.c}, which contains 54 This file has to be compiled to obtain the {\it interface.o} file, 56 After the file {\it interface.o} has been generated, 58 interface, and calling {\bf load_foreign_files/2} will connect 61 Although it is possible to use this library to interface 63 port foreign interface fro [all...] |
H A D | embremote.tex | 34 This chapter describes the remote Tcl interface, which allows a separate 36 the embedding Tcl interface (see chapter~\ref{chaptcl}). Like the embedding 37 interface, Tcl and {\eclipse} code communicates by sending and receiving 40 The interface can thus be 41 used in similar fashion to the embedding interface, e.g.\ for the 46 The main features of the interface are: 54 single {\eclipse} via the remote interface. 56 similar, and once the connection is established in the remote interface, 60 The remote interface thus offers more flexibility than an embedding 61 interface i [all...] |
H A D | embtcl.tex | 39 The interface is similar in spirit to the {\eclipse} embedding 43 interface, described in chapter~\ref{chapremote}. In this case, the 46 possible to reuse the same Tcl and {\eclipse} code in both interface. The 47 advantage of the embedding interface is that {\eclipse} is much more 49 more efficient. The advantage of the remote interface is that the Tcl and 55 {\bf tkeclipse} is currently implemented using only the embedding interface, 62 \section{Loading the interface} 64 The {\eclipse} interface is provided as a Tcl-package called {\bf eclipse}, 94 commands of this interface (except ec_set_option) can be used. The 156 \item[\index{ec_rpc (Tcl embedding interface)}ec_rp [all...] |
H A D | dbi.tex | 26 \index{database, interface to|(} 27 \index{MySQL, interface to|(} 32 The \eclipse\ SQL database interface is a low-level interface to the SQL 34 full power of the SQL interface to the programmer. 47 The interface provides safe handles to database cursors. Higher 61 Nowhere in the interface are SQL commands ever looked 84 interface. To exchange 93 interface to different kinds of databases. The currently supported database is 97 \section{Using the SQL database interface} [all...] |
H A D | embvb.tex | 30 language interface of {\eclipse}. They are provided in source form 32 The interface is similar in spirit to the {\eclipse} embedding 38 This contains the classes which form the interface to eclipse. 63 Symbolic names for error conditions in the interface. 78 functions of this interface can be used.
|
/barrelfish-2018-10-04/lib/libc/net/ |
H A D | sourcefilter.c | 77 * Internal: Map an IPv4 unicast address to an interface index. 114 * Pass #2: Find the index of the interface matching the name 141 setipv4sourcefilter(int s, struct in_addr interface, struct in_addr group, argument 162 ifindex = __inaddr_to_index(interface.s_addr); 211 getipv4sourcefilter(int s, struct in_addr interface, struct in_addr group, argument 235 ifindex = __inaddr_to_index(interface.s_addr); 276 setsourcefilter(int s, uint32_t interface, struct sockaddr *group, argument 319 msfr.msfr_ifindex = interface; 333 getsourcefilter(int s, uint32_t interface, struct sockaddr *group, argument 342 if (interface [all...] |
/barrelfish-2018-10-04/lib/lwip/src/core/ipv4/ |
H A D | igmp.c | 131 LWIP_DEBUGF(IGMP_DEBUG, (" on if %p\n", group->interface)); 141 * Start IGMP processing on interface 143 * @param netif network interface on which start IGMP processing 173 * Stop IGMP processing on interface 175 * @param netif network interface on which stop IGMP processing 183 /* look for groups joined on this interface further down the list */ 186 /* is it a group joined on this interface? */ 187 if (group->interface == netif) { 217 * Report IGMP memberships for this interface 219 * @param netif network interface o [all...] |
/barrelfish-2018-10-04/doc/015-disk-driver-arch/ |
H A D | xahcid.tex | 7 ahcid's design is modeled after netd. It has a small \acs{idc} interface that 10 \acs{idc} messages. Currently the interface also provides access to the {\tt 17 interface}] 18 interface ahci_mgmt "AHCI Management Daemon" { 51 interface, which clients can then use to register themselves for a single port. 65 interface. Clearing the interrupts before delivering the completion messages to
|
H A D | conclusion.tex | 7 interface with disks. The overhead incurred is acceptable in the trade-off for 8 simplicity and modularity. The seperation of interface definition for \ac{ata}
|
H A D | design.tex | 69 management for sending and receiving messages to a disk. Its interface 70 resembles a Flounder-generated interface and makes use of Barrelfish's 77 resulting interface can be used similarly to performing \acs{idc}. 81 For our purposes (designing a messaging interface to disks) it was sufficient 87 interface specification.
|
/barrelfish-2018-10-04/include/usb/ |
H A D | usb_transfer.h | 51 uint8_t interface; ///< the itnerface to use member in struct:usb_transfer_setup
|
H A D | usb_request.h | 29 uint8_t recipient : 5; // device, interface, endpoint... 46 uint16_t wIndex; ///< interface / endpoint index 69 // masks for the index field depending on the recipent (interface or endpoint) 158 usb_error_t usb_set_alt_iface(uint16_t alt_setting, uint16_t interface);
|
/barrelfish-2018-10-04/include/lwip/lwip/ |
H A D | api_msg.h | 94 struct ip_addr *interface; member in struct:api_msg_msg::__anon88::__anon94
|
H A D | igmp.h | 98 * a list of groups for each interface 99 * these should really be linked from the interface, but 109 struct netif *interface; member in struct:igmp_group
|
/barrelfish-2018-10-04/usr/drivers/usb/usb_manager/ |
H A D | usb_device.c | 30 * \brief frees up the allocated interface and enpoint structures for the 60 * the interface and endpoint structures for this configuration 63 * \param iface the interface to initialze mostly USB_INTERFACE_ANY 80 /* the alternative interface index */ 121 /* reset the interface parsing state */ 129 struct usb_interface *interface; local 135 * + interface descriptor 1 138 * + interface descriptor 2 142 * we first have to get the next interface and then all the belonging 149 * there is a maximum of 32 interfaces, since the interface numbe [all...] |
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/ |
H A D | util.pl | 85 :- comment(interface/1, [template:"interface(+Module)", 86 summary:"List the module interface of the specified Module" 100 interface/1, 270 % print a module's interface 272 interface(Module) :- 276 get_module_info(Module, interface, List),
|
H A D | remote_tools.pl | 25 % ECLiPSe II remote development tools ECLiPSe side interface 123 interface. This allows the development tools to be used by any ECLiPSe 124 session, and not just one which uses the embedded Tcl interface.").
|
/barrelfish-2018-10-04/doc/018-Practical-guide/ |
H A D | helloWorldApp.tex | 56 requires defining an interface in Flounder IDL, updating the interfaces 70 In this subsection, we will create a new interface 71 for our use. We do this by creating a new interface file called 72 \texttt{hello.if} in the \texttt{if\\} directory. Following is simple interface 78 interface hello "Hello World interface" { 87 interface into the compilation process. 99 Adding the name of your interface here will make sure that the communication 113 write the interface file and include appropriate headers in the application 161 by calling export function on the service interface [all...] |
/barrelfish-2018-10-04/doc/011-idc/ |
H A D | IDC.tex | 96 alias \> call \> enum \> in \> interface \> message \\ 120 A Flounder input file must specify a single interface, of the form: 123 interface \synit{name} ["\synit{description}"] 133 \item[name] is an identifier for the interface type, and will be used to 141 describes the interface being specified, for example 170 one message in every interface. 179 interface file in place of the given builtin type. It does not alter the 185 to be created in the context of both the interface file and the programming 301 When invoked, Flounder processes a single interface file, and generates into a 336 the command line, before parsing of the interface definitio [all...] |
/barrelfish-2018-10-04/doc/026-device-queues/ |
H A D | devif.tex | 87 In this document we describe a queue based interface that unifies communication for 89 The interface should fit to as many devices as possible while still being efficient. 92 approach and define pieces that are ambiguous. These interface do not define a memory model 93 or what preconditions/postconditions an interface function has. 96 we want to document the interface as clearly as possible, and see the implementation and 103 \item \textbf{Region}: A Region is a chunk of memory that is registered to the \devif interface. From the memory of the region, buffers can be allocated. 112 The basic functionality of our queue based device interface (from now on called \devif) 114 A buffer is a variable sized piece of memory within a previously to the \devif interface 116 and deallocating buffers to keep the interface and the underlying protocol simple. 118 allocator which increases the complexity of the \devif interface [all...] |
/barrelfish-2018-10-04/doc/016-serial-ports/ |
H A D | Serial.tex | 52 At present, it only describes the kernel-space interface 56 In the future, it will also describe the interface to user-space UART 59 \chapter{CPU driver interface}\label{cha:cpudriver} 68 The interface to this subsystem is specified in the file 72 The interface is intentionally very basic. It assumes each UART runs
|
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/ |
H A D | umstkeclipse.tex | 26 {\tkeclipse} is a graphical user interface to {\eclipse}. It is an 27 alternative to the traditional textual line-based user interface, providing 38 \cite{Tcl94}, using the new {\eclipse} Tcl/Tk interface 209 interface (see the Embedding and Interfacing Manual) to provide a graphical 213 \item The user is using the embedding Tcl/Tk interface, and is thus 215 development tools via the embedding interface. This is described in 217 \item The user is not using the embedding Tcl/Tk interface. In this case 233 example usage of the interface. 235 In order to use the Tcl/Tk interface, the system must be initialized as 277 interface (se [all...] |
/barrelfish-2018-10-04/lib/lwip/src/api/ |
H A D | api_lib.c | 568 * @param interface the IP address of the network interface on which to send 576 struct ip_addr * interface, 588 msg.msg.msg.jl.interface = interface; 574 netconn_join_leave_group(struct netconn * conn, struct ip_addr * multiaddr, struct ip_addr * interface, enum netconn_igmp join_or_leave) argument
|
/barrelfish-2018-10-04/usr/eclipseclp/Opium/ |
H A D | loadopium.pl | 70 :- get_opium_file("interface", F), mycompile(F). 132 /* interface scenario requires help scenario */ 134 make(interface, opium_kernel, UntrGlobal, SD, OD),
|