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/.
Erich Dachleger edachleger at yahoo.comHi list, Are all the obtained bursts.dat files useless when they are captured by unmodified burst_ind?When I use the standard burst_ind I obtain a chain of burst-files.I also sometime see displayed the word SACCH/8 on the log-screen. If one tries to single out burst-files belonging to SACCH/8 or TCH/F would these be useful as inputs to kraken after being converted to keystream? Somewhere on this list I read that captured data must be converted to the MAC-block,if one looks for frames, and that code could be found in airprobe .What ist the meaning of that? Aren't the MAC-block alreday displayed when using burst_ind? regards erich ________________________________ Fra: Bhaskar11 <niceguy108 at gmail.com> Til: Sylvain Munaut <246tnt at gmail.com>; osmocomBB <baseband-devel at lists.osmocom.org> Sendt: Tirsdag, 5. februar 2013 6.27 Emne: Content of burst data in burst_ind branch Can you please clarify what kind of preprocessing has been done for bursts in burst_ind data? Does TCH/F data come through with block-diagonal de-interleaved? Or does come as 8 interleaved bursts? I think all the intra-burst de-interleaving has already been done at DSP level. Is this correct? B -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20130205/b408476d/attachment.htm>