Lines Matching refs:with

4 The fastboot protocol is a mechanism for communicating with bootloaders
30 2. Client response with a single packet no greater than 256 bytes.
43       The payload is printed as-is with no newline at the end.
63 4. Client responds with a single packet no greater than 256 bytes.
115 * Commands that begin with a lowercase letter are reserved for this
116   specification.  OEM-specific commands should not begin with a
117   lowercase letter, to prevent incompatibilities with future specs.
124                        should return a FAIL response, optionally with an error
134                        will reply with "DATA%08x" if it has enough
140                        with "DATA%08x" if it is ready to send %08x bytes of
142                        the client must reply with "FAIL".  After the client
144                        a single packet starting with "OKAY".  Clients
196 Names starting with a lowercase character are reserved by this
197 specification.  OEM-specific names should not start with lowercase
202 There are a number of commands to interact with logical partitions:
212                         old image is created with a zero size.
218                         Create a logical partition with the given name and
222                         Delete a logical partition with the given name.
281   1. As with TCP, the device will listen on UDP port 5554.
310             this by 1 with each new packet, and the device must provide the
318           The host sends a query packet once on startup to sync with the device.
338           send a packet with fastboot data, and the device will reply with an
340           and the device will reply with fastboot data. The device may not give
344           The device may respond to any packet with an error packet to indicate
352 correlation with download speed, so devices are strongly suggested to support at
353 least 1024-byte packets. On a local network with 0.5ms round-trip time this will
378 continuation packets. The receiver should respond to a continuation packet with
382 The host starts with a Query packet, then an Initialization packet, after
390       * respond with a Query packet with S in the data field
393       * create a response packet R with the same ID and sequence as P, containing
501     0x03  0x00  0x00  0x00  getvar:version [arrives late with old seq#, is ignored]