Searched refs:identify (Results 1 - 25 of 32) sorted by relevance

12

/barrelfish-2018-10-04/lib/vfs/
H A Dvfs_blockdevfs_ata.c201 err = ahci_mgmt_binding->rpc_tx_vtbl.identify(ahci_mgmt_binding, reply.port_ids[i],
207 ata_identify_t identify; local
208 ata_identify_initialize(&identify, (void *)identify_reply.identify_data);
211 //ata_identify_pr(buf, 8192, &identify);
217 if (ata_identify_plss_lls_rdf(&identify)) {
218 sector_size = 2*ata_identify_wpls_rd(&identify);
222 size_t sectors = ata_identify_tnuas48_rd(&identify);
H A Dvfs_blockdevfs_ahci.c309 err = ahci_mgmt_binding->rpc_tx_vtbl.identify(ahci_mgmt_binding,
315 ata_identify_t identify; local
316 ata_identify_initialize(&identify, (void *)identify_reply.identify_data );
319 //ata_identify_pr(buf, 8192, &identify);
325 if (ata_identify_plss_lls_rdf(&identify)) {
326 sector_size = 2*ata_identify_wpls_rd(&identify);
330 size_t sectors = ata_identify_tnuas48_rd(&identify);
/barrelfish-2018-10-04/include/ahci/
H A Dahci.h89 ata_identify_t identify; member in struct:ahci_binding
/barrelfish-2018-10-04/lib/blk/blk_ahci/
H A Dblk_ahci.h93 ata_identify_t identify; //< Points to identify_mem.vaddr, valid after port_identify() is done. member in struct:ahci_port
H A Dahci_port.c289 ata_identify_initialize(&port->identify, (mackerel_addr_t)port->identify_mem.vaddr);
292 ahci_port_print_identification(&port->identify);
/barrelfish-2018-10-04/lib/driverkit/
H A Dddomain_service.c193 DRIVERKIT_DEBUG("%s:%s:%d: Send identify %"PRIu64"\n", __FILE__, __FUNCTION__, __LINE__, ident);
194 errval_t send_err = rpc_bind.binding->tx_vtbl.identify(rpc_bind.binding, NOP_CONT, ident);
H A Dddomain_client.c156 DRIVERKIT_DEBUG("Got identify message %"PRIu64".\n", id);
178 USER_PANIC("Unknown identify call from ddomain...");
183 .identify = ddomain_identify_handler,
/barrelfish-2018-10-04/lib/octopus/client/
H A Doctopus.c199 err = cl->call_seq.identify(cl, client_identifier, octopus_BINDING_RPC);
/barrelfish-2018-10-04/usr/eclipseclp/Contrib/
H A Dxml.pl52 * The domain exception will attempt to identify the particular sub-term in
85 * is not well-formed, diagnosis tries to identify the specific culprit term.
/barrelfish-2018-10-04/doc/015-disk-driver-arch/
H A Dfuture.tex15 uniquely identify the disks attached to an \ac{ahci} controller. Neither do we
H A Dxahcid.tex21 rpc identify(in uint8 port_id,
H A Dlibahci.tex190 identify their correpsonding \ac{ahci} command.
/barrelfish-2018-10-04/doc/009-notifications/
H A DNotify.tex110 Domains do not have any efficient way to identify the (probably) small
178 core. This would identify to the destination core which FIFO to look
181 identify which fifos to poll. (the PCN entry for src$\_$core ==
/barrelfish-2018-10-04/lib/ahci/
H A Dahci.c31 uint8_t port; // only valid in open and identify cb
47 AHCI_DEBUG("got identify data for unbound port\n");
57 ata_identify_initialize(&ahci_binding->identify,
142 // fetch identify data from management daemon
/barrelfish-2018-10-04/doc/013-capability-mgmt/
H A Dtype_system.tex839 \arg CSpace address of the capability to identify
840 \arg Level of the capability to identify
850 identify
851 \arg Level in the dispatcher's CSpace of the capability to identify
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/
H A Dumsmemory.tex203 The debugger can help to identify nondeterministic predicates:
H A Dumsparallel.tex346 Its process id is used to identify a parallel session.
H A Dumssocket.tex181 the sender has to identify itself explicitly in the message
H A Dumsexcept.tex126 This handle is the only way to identify the event, and therefore must be
407 may be used to identify
H A Dumsdebug.tex71 the most recent CALL port. This allows to uniquely identify a
201 which makes it easy to identify corresponding delay and resume events.
268 number, it can be used to identify ports that belong to the same box.
819 %{\bf _c123} to identify the variable number.
1862 concepts of the library. Specific ports can be used to identify the
/barrelfish-2018-10-04/usr/eclipseclp/documents/visualisation/
H A Dannotate.tex84 atom which will be used to uniquely identify the \viewable{} later,
/barrelfish-2018-10-04/doc/006-routing/
H A DRouting.tex182 Multi-hop messages carry a virtual circuit identifier (VCI). Virtual circuit identifiers allow nodes to identify the particular multi-hop channel a message belongs to. Each node on a multi-hop channel maintains a forwarding table, which maps VCIs to the next hop on that particular channel. A node forwards multi-hop messages based on this forwarding table. At channel end-points, a VCI allows to identify the binding belonging to the multi-hop channel the message was sent over. Virtual circuit identifiers are not only local to a specific link, but also to a direction on that link. Figure~\ref{fig:vci} shows an example assignment of VCIs.
225 As described in section~\ref{section:vcis}, it is necessary that each node on the multi-hop channel tells its neighbouring nodes what virtual circuit identifier they should use for messages sent over that particular channel. Therefore, each message contains the virtual circuit identifier of the sender. The two response-messages additionally contain the VCI of the receiver. This allows the receiver of a response-message to identify the multi-hop channel the message belongs to.
234 As a multi-hop channel allows to send messages in two directions, the direction field is needed to identify the direction of a particular message. Currently we assign direction ''1'' to all messages going from the dispatcher who initiated the multi-hop channel to the other dispatcher, and direction ''2'' for messages going the opposite way.
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/
H A Dembremoteproto.tex207 connection. This is sent in EXDR format, and is used to identify this
435 the stream id for the memory queue. The id is used by both sides to identify
1410 connection, and is used to identify a particular remote peer (an
H A Ddbi.tex300 used to identify a connection to a database. Associated to that
/barrelfish-2018-10-04/usr/eclipseclp/documents/applications/
H A Dtutorial.tex208 Once the external API is clearly defined, we can start looking at the next level of internal structure. This will depend on the intended purpose of the system, but we can identify some typical structures that can be found in many applications. Here, we present two typical designs, one for solving combinatorial problems, the other for transforming data.
269 Once we have decided on a top-level structure, we must consider the input/output arguments of each part. We have to decide which data must be fed into which modules, where new data structures will be created and which other modules require this data. For each piece of information we must identify its source and its possible sinks. Designing these data flows is an iterative process, assigning functionality to modules and making sure that the required information is available. The design aim should be to minimize the amount of information that must be passed across module boundaries and to arrange functions in the correct data flow order, so that all information is produced before it is required in another module.
514 As key \index{key}we can use numbers, atoms or arbitrary terms, but atoms would be the most common key in a hash table. This is very useful when converting input data, since the external data representation often will use names (atoms) to identify objects.
1726 Run-time errors\index{run time error}\index{error, run time} occur if we call a built-in predicate with a wrong argument pattern. This will usually either be a type mismatch\index{type mismatch}, i.e. using a number where an atom is expected, or an instantiation problem, i.e. passing a variable where a ground value was expected or vice versa. In this case the ECLiPSe system prints out the offending call together with an error message\index{error message} indicating the problem. If we are lucky, we can identify the problem immediately, otherwise we may have to look up the documentation of the built-in to understand the problem.
1787 In a constraint problem we then have to identify which constraint(s) should eliminate this answer and why that didn't happen. There are two typical scenarios.

Completed in 127 milliseconds

12