FreeCalypso > hg > freecalypso-tools
comparison rvinterf/include/limits.h @ 0:e7502631a0f9
initial import from freecalypso-sw rev 1033:5ab737ac3ad7
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sat, 11 Jun 2016 00:13:35 +0000 |
| parents | |
| children | ca6e969be6ee |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:e7502631a0f9 |
|---|---|
| 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 */ |