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/op25-dev@lists.osmocom.org/.
Matt D md123 at nycap.rr.comOn 07/12/2013 07:45 PM, Steve Glass wrote: > Hi Matt, >> >> I am trying to get a handle on the data in the Link Control Word. >> The LCW is 72 bits right? On transmission the 72 bit LCW is >> serialized into 12 hex bits. And then it is encoded with a >> (24,12,13) RS code to yield 24 hex bits. The 24 hex bits are then >> encoded with a (10,6,3) shortened Hamming code to yield 240 bits >> total. >> >> Is it known how the bits are serialized? Or better yet is there >> an existing function for unserializing/serializing that will work >> here? >> > The Common Air Interface specification defines the bit > interleaving. We typically use a static const array identifying the > indices of the bits that make up a given logical field. > Hey, so where the Daniels manual uses the term 'serializing' (for the bits that make up the LCW) this simply refers to the process of turning the 72 bits into 6 hex bits? And this is done in the same way for the data information in the HDU even though it is not explicitly called serializing in the HDU section of the manual? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20130713/a62ab8ed/attachment.htm>