FreeCalypso > hg > freecalypso-sw
diff rvinterf/include/limits.h @ 256:2f285f20d617
rvinterf: *.h moved into include subdir
author | Michael Spacefalcon <msokolov@ivan.Harhan.ORG> |
---|---|
date | Tue, 04 Feb 2014 05:03:57 +0000 |
parents | rvinterf/limits.h@3256dc6e84ae |
children |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/rvinterf/include/limits.h Tue Feb 04 05:03:57 2014 +0000 @@ -0,0 +1,32 @@ +/* + * For sizing our buffers etc in the rvinterf suite, including the local + * UNIX domain socket protocol between rvinterf and fc-tmsh etc, we need + * to have some limits on the message sizes in both host->target and + * target->host directions. + * + * For the host->target direction, the choice of message size limit is + * easy: the packet Rx code in RVT on the target side also has a limit + * (quite naturally, as it needs to use a static buffer to reassemble + * incoming packets as they arrive at the UART in unpredictable interrupt- + * sized chunks), so we set our limit to match that in RVT. + */ + +#define MAX_PKT_TO_TARGET 255 + +/* + * In the other direction (target->host), there is no fixed limit + * definition easily visible in the target fw code: any fw component + * can call rvt_send_trace_cpy() or rvt_mem_alloc() followed by + * rvt_send_trace_no_cpy(), or some higher-level API that reduces to + * these functions, with a message of any size, subject only to memory + * limits, which obviously aren't as strict as a #define'd maximum + * message size. Hence in this direction we use our own arbitrary + * choice of size limit. + */ + +#define MAX_PKT_FROM_TARGET 512 + +/* + * Both limit definitions above counts all bytes between the opening and + * closing STX flags, but not DLEs inserted for binary transparency. + */