5 Feb
2016
5 Feb
'16
8 a.m.
On 05 Feb 2016, at 13:57, Harald Welte
<laforge(a)gnumonks.org> wrote:
I'm not sure what you mean here? AFAIK, the byTrxId can have arbitrary
values from the PHY side, we just need to use the same value as used in
the TRX-OPEN.req for all primitives belinging to that TRX. However,
internally we use them with 0...n.
I wondered which other fields we should have set and that work because talloc has used a
memset on the msgb. For trx==0 there is no change but with trx != 0 there would be a
fallout.