<feed xmlns='http://www.w3.org/2005/Atom'>
<title>osmo-bts, branch master</title>
<subtitle>Osmocom BTS-Side code (Abis, scheduling)</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/'/>
<entry>
<title>contrib: Re-load the firmware before restarting the main application</title>
<updated>2012-05-14T20:29:45Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-05-14T20:27:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=b18f00f162e1b7b3f3583e151b8a2091932c8708'/>
<id>b18f00f162e1b7b3f3583e151b8a2091932c8708</id>
<content type='text'>
More recent firmware appears to have issues even after a clean shutdown,
make sure to fully reset the DSP before starting the BTS software.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
More recent firmware appears to have issues even after a clean shutdown,
make sure to fully reset the DSP before starting the BTS software.
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmobts l1: make sure to read messages of arbitrary size</title>
<updated>2012-05-13T13:25:27Z</updated>
<author>
<name>Harald Welte</name>
<email>laforge@gnumonks.org</email>
</author>
<published>2012-05-13T13:25:27Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=268c7f02fd83f05409a357796217274efc3c6c1b'/>
<id>268c7f02fd83f05409a357796217274efc3c6c1b</id>
<content type='text'>
... and warn if the size is not what we expect.

This is required to work with sysmobts-v2 firmware &gt;= v2.1, as the
SuperFemto_Prim_t is now larger than the GsmL1_Prim_t.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
... and warn if the size is not what we expect.

This is required to work with sysmobts-v2 firmware &gt;= v2.1, as the
SuperFemto_Prim_t is now larger than the GsmL1_Prim_t.
</pre>
</div>
</content>
</entry>
<entry>
<title>Adapt to L1 firmware/API version 2.1</title>
<updated>2012-05-13T12:16:28Z</updated>
<author>
<name>Harald Welte</name>
<email>laforge@gnumonks.org</email>
</author>
<published>2012-05-13T12:16:28Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=388b9d0a357fece464f8c6dc37ae06aacf175897'/>
<id>388b9d0a357fece464f8c6dc37ae06aacf175897</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmobts: Document the values of the clock-source in the vty command</title>
<updated>2012-05-12T06:49:35Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-05-12T06:48:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=9de1e9f914cfff62236649549b52b5d675966e3c'/>
<id>9de1e9f914cfff62236649549b52b5d675966e3c</id>
<content type='text'>
We need to have a documentation for each possible value, add some simple
ones for the available clock sources.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We need to have a documentation for each possible value, add some simple
ones for the available clock sources.
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmobts: Save the clock-source to the config file</title>
<updated>2012-05-12T06:49:35Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-05-12T06:38:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=7fe0838588f1a2bb4df7c078e00f8b7b67a9abed'/>
<id>7fe0838588f1a2bb4df7c078e00f8b7b67a9abed</id>
<content type='text'>
Make the clock names lower case to match with the vty command.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Make the clock names lower case to match with the vty command.
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmobts: Add Network Listen as clock source for the bts</title>
<updated>2012-05-12T06:49:35Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-05-12T06:37:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=3af5426d7188e810d7ee2aacb2d7af22e1054665'/>
<id>3af5426d7188e810d7ee2aacb2d7af22e1054665</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>update the readme</title>
<updated>2012-05-05T12:44:29Z</updated>
<author>
<name>Harald Welte</name>
<email>laforge@gnumonks.org</email>
</author>
<published>2012-05-05T12:44:29Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=e6ed814dc35c6c242eff23fc5e63563bcc12a53f'/>
<id>e6ed814dc35c6c242eff23fc5e63563bcc12a53f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmo-bts: Use HW_SYSMOBTS_V1 to select the development hardware</title>
<updated>2012-04-28T15:05:03Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-04-28T15:02:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=f7fd2e47986d5385de5e892037a9bd3b663c1085'/>
<id>f7fd2e47986d5385de5e892037a9bd3b663c1085</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>sysmo-bts: Move the payload setting into a new method</title>
<updated>2012-04-28T15:04:56Z</updated>
<author>
<name>Holger Hans Peter Freyther</name>
<email>zecke@selfish.org</email>
</author>
<published>2012-04-28T14:57:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=36a3b0d85b514b92052ac2f85d4afa53780304e5'/>
<id>36a3b0d85b514b92052ac2f85d4afa53780304e5</id>
<content type='text'>
Make this code a bit easier to read by moving the payload setting
into a new method.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Make this code a bit easier to read by moving the payload setting
into a new method.
</pre>
</div>
</content>
</entry>
<entry>
<title>RSL / SI: Make sure to have correct LAPDm header in SI5/SI6 on SACCH</title>
<updated>2012-04-27T13:12:46Z</updated>
<author>
<name>Harald Welte</name>
<email>laforge@gnumonks.org</email>
</author>
<published>2012-04-27T13:12:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=36179bbcdf9407bcc4c06f7608f28e0dfcc29861'/>
<id>36179bbcdf9407bcc4c06f7608f28e0dfcc29861</id>
<content type='text'>
SI5/SI6 and other messages on SACCH need the C/R and the EA bit set in
the LAPDm header.  Most devices accept a broken header, but especially
the Wavecom Q2686 responds with tons of RR STATUS messages if there is
any invalid bit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
SI5/SI6 and other messages on SACCH need the C/R and the EA bit set in
the LAPDm header.  Most devices accept a broken header, but especially
the Wavecom Q2686 responds with tons of RR STATUS messages if there is
any invalid bit.
</pre>
</div>
</content>
</entry>
</feed>

