FreeCalypso > hg > freecalypso-tools
view rvinterf/include/limits.h @ 1001:7df4c9ae6ba4
loadtools/scripts: w220.{config,init} => chimei.{config,init}
Motorola W220, first touched by FreeCalypso in 2019-05, is an ODM phone
made by Chi-Mei, and its peculiar property of relevance to loadtools
is that it has XRAM on Calypso nCS3 instead of the usual nCS1 - which
matters for fc-xram. We are now discovering other Chi-Mei phones
including Sony Ericsson J120, and they share the same quirk of XRAM
on nCS3 - hence we rename this loadtools target from w220 to chimei.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sat, 09 Dec 2023 17:53:44 +0000 |
parents | ca6e969be6ee |
children |
line wrap: on
line source
/* * 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. * * With current FreeCalypso fw, unchanged from classic TCS211 in this * aspect, the largest RVTMUX packets emitted by the fw are G23M PS * primitives forwarded externally via GPF routing mechanism, and some * of them exceed our previous arbitrary limit of 512 bytes. However, * the largest output packet size that can be generated via this * mechanism equals the largest partition size in GPF partition pool * configuration, and that largest size is 1600 bytes. Hence we have * our answer as to what maximum packet size we need to support. */ #define MAX_PKT_FROM_TARGET 1600 /* * Both limit definitions above counts all bytes between the opening and * closing STX flags, but not DLEs inserted for binary transparency. */