comparison rvinterf/limits.h @ 174:3256dc6e84ae

rvinterf: refactored rvtdump compiles and works
author Michael Spacefalcon <msokolov@ivan.Harhan.ORG>
date Fri, 22 Nov 2013 07:41:31 +0000
parents rvinterf/old/txpkt.h@f42854da4563
children
comparison
equal deleted inserted replaced
173:f42854da4563 174:3256dc6e84ae
1 /*
2 * For sizing our buffers etc in the rvinterf suite, including the local
3 * UNIX domain socket protocol between rvinterf and fc-tmsh etc, we need
4 * to have some limits on the message sizes in both host->target and
5 * target->host directions.
6 *
7 * For the host->target direction, the choice of message size limit is
8 * easy: the packet Rx code in RVT on the target side also has a limit
9 * (quite naturally, as it needs to use a static buffer to reassemble
10 * incoming packets as they arrive at the UART in unpredictable interrupt-
11 * sized chunks), so we set our limit to match that in RVT.
12 */
13
14 #define MAX_PKT_TO_TARGET 255
15
16 /*
17 * In the other direction (target->host), there is no fixed limit
18 * definition easily visible in the target fw code: any fw component
19 * can call rvt_send_trace_cpy() or rvt_mem_alloc() followed by
20 * rvt_send_trace_no_cpy(), or some higher-level API that reduces to
21 * these functions, with a message of any size, subject only to memory
22 * limits, which obviously aren't as strict as a #define'd maximum
23 * message size. Hence in this direction we use our own arbitrary
24 * choice of size limit.
25 */
26
27 #define MAX_PKT_FROM_TARGET 512
28
29 /*
30 * Both limit definitions above counts all bytes between the opening and
31 * closing STX flags, but not DLEs inserted for binary transparency.
32 */