modulo and frame number in mframe_sched.c

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Max.Suraev at fairwaves.ru
Thu Oct 18 11:48:15 UTC 2012


18.10.2012 12:15, Harald Welte пишет:

> On ARM, it doesn't matter.  even if you made those fields uint8_t
> in the struct mframe_sched_item, they would still be aligned to 32bit
> boundaries.  So you wouldn't change the memory layout at all based on
> your change.

That's odd - after I've changed it to uint8_t the
"board/compal_e88/rssi.compalram.elf section `.data' will not fit in region `LRAM'"
error is gone. I'm no expert in compiler internals but I think that indicates the
change in memory layout.

Could you please comment?

> Given that the CPU speed is more limited than RAM, I think the current
> approach makes sense.
> 

I agree.

>> Is it possible for 'modulo' to be bigger than 255?
> 
> I don't think so, at least not for standard GSM operation.
> 

As Sylvain explained on irc having modulo and frame number bigger than 256 might be
useful for experimentation with packets which are spread across several frames - to
represent them as huge 'fake' multiframe.

At least that's how I've understood it. He's surely doing some creepy magic with GSM :-)

-- 
best regards,
Max, http://fairwaves.ru




More information about the baseband-devel mailing list