Empathy List Archives

TT

Thomas Tsou

Wed, Nov 17, 2010 3:09 PM

I'm announcing the availability of USRP2 support with OpenBTS. The
patch set consists of a new device implementation that uses the UHD
driver from Ettus Research and allows the use of an external 10MHz
reference clock. Additional implementation details can be found in the
comments and commit log.

Download:

git clone git://github.com/ttsou/openbts-uhd.git

git clone http://github.com/ttsou/openbts-uhd.git

http://github.com/ttsou/openbts-uhd/tarball/master

GitHub:

http://github.com/ttsou/openbts-uhd

Build:

USRP2 support requires the UHD driver and firmware. GNU Radio is not required.

http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

./bootstrap
./configure --with-uhd
make

Without the '--with-uhd' option, the standard USRP1 implementation
will be built.

Release Notes:

*The USRP2 is clocked at 100MHz and does not output fractional sample
rates, so only the non-52M Transceiver is available.

*Tested with a single WBX board, which is capable of operation on all
4 GSM bands. Other boards should work, but are untested.

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

External Reference Clock:

The front panel 10MHz reference input of the USRP2 can be used to
improve stability of the internal oscillator (~20 ppm). To test
frequency offset, a modified version of Kalibrate -
http://thre.at/kalibrate - is available. Information and examples for
the UHD development branch can be found here.

http://ttsou.github.com/kalibrate-uhd

That's about it. Hopefully, a number of people will find this useful.
Let me know if you have any questions. Comments and feedback are
always welcome.

Thomas

I'm announcing the availability of USRP2 support with OpenBTS. The patch set consists of a new device implementation that uses the UHD driver from Ettus Research and allows the use of an external 10MHz reference clock. Additional implementation details can be found in the comments and commit log. Download: git clone git://github.com/ttsou/openbts-uhd.git git clone http://github.com/ttsou/openbts-uhd.git http://github.com/ttsou/openbts-uhd/tarball/master GitHub: http://github.com/ttsou/openbts-uhd Build: USRP2 support requires the UHD driver and firmware. GNU Radio is not required. http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki ./bootstrap ./configure --with-uhd make Without the '--with-uhd' option, the standard USRP1 implementation will be built. Release Notes: *The USRP2 is clocked at 100MHz and does not output fractional sample rates, so only the non-52M Transceiver is available. *Tested with a single WBX board, which is capable of operation on all 4 GSM bands. Other boards should work, but are untested. *Operation in the upper bands (1800, 1900MHz) requires an external reference for reliable operation. This is true to a lesser extent in the lower bands as well. External Reference Clock: The front panel 10MHz reference input of the USRP2 can be used to improve stability of the internal oscillator (~20 ppm). To test frequency offset, a modified version of Kalibrate - http://thre.at/kalibrate - is available. Information and examples for the UHD development branch can be found here. http://ttsou.github.com/kalibrate-uhd That's about it. Hopefully, a number of people will find this useful. Let me know if you have any questions. Comments and feedback are always welcome. Thomas

JB

Josh Blum

Wed, Nov 17, 2010 7:20 PM

I'm announcing the availability of USRP2 support with OpenBTS. The
patch set consists of a new device implementation that uses the UHD
driver from Ettus Research and allows the use of an external 10MHz
reference clock. Additional implementation details can be found in the
comments and commit log.

You are awesome.

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

I wonder if this will be necessary for the USRP-N210 since that has a
10MHz TCXO for an "internal" reference.

In another note. I am considering modifying the old USRP classic FPGA
code to get receive timestamps (secs and ticks) for the USRP1 + UHD
support. What is needed for in terms of timestamps with transmit for
OpenBTS? Basically, does it a timestamped send_at() capability?

-Josh

> I'm announcing the availability of USRP2 support with OpenBTS. The > patch set consists of a new device implementation that uses the UHD > driver from Ettus Research and allows the use of an external 10MHz > reference clock. Additional implementation details can be found in the > comments and commit log. > You are awesome. > *Operation in the upper bands (1800, 1900MHz) requires an external > reference for reliable operation. This is true to a lesser extent in > the lower bands as well. > I wonder if this will be necessary for the USRP-N210 since that has a 10MHz TCXO for an "internal" reference. In another note. I am considering modifying the old USRP classic FPGA code to get receive timestamps (secs and ticks) for the USRP1 + UHD support. What is needed for in terms of timestamps with transmit for OpenBTS? Basically, does it a timestamped send_at() capability? -Josh

TT

Thomas Tsou

Wed, Nov 17, 2010 11:17 PM

On Wed, Nov 17, 2010 at 2:20 PM, Josh Blum josh@joshknows.com wrote:

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

I wonder if this will be necessary for the USRP-N210 since that has a 10MHz
TCXO for an "internal" reference.

I'm thinking that it will suitable to hold calls on all bands; but it
depends on the requirements of application. I'm sure there are some
people who won't be happy with anything but carrier grade rubidium.

In another note. I am considering modifying the old USRP classic FPGA code
to get receive timestamps (secs and ticks) for the USRP1 + UHD support. What
is needed for in terms of timestamps with transmit for OpenBTS? Basically,
does it a timestamped send_at() capability?

The transmit samples go out in a continuous stream so the critical
timing points are the start and resync period after an interruption
(underrun). For the latter, the underrun and late packet arrival
behaviour is the main factor. The USRP2 will still transmit packets
that arrive late, so they're checked and dropped at the host.
Otherwise, we get a constant shift in the transmit slots compared to
those on the receive side.

Thomas

On Wed, Nov 17, 2010 at 2:20 PM, Josh Blum <josh@joshknows.com> wrote: > >> *Operation in the upper bands (1800, 1900MHz) requires an external >> reference for reliable operation. This is true to a lesser extent in >> the lower bands as well. >> > > I wonder if this will be necessary for the USRP-N210 since that has a 10MHz > TCXO for an "internal" reference. I'm thinking that it will suitable to hold calls on all bands; but it depends on the requirements of application. I'm sure there are some people who won't be happy with anything but carrier grade rubidium. > In another note. I am considering modifying the old USRP classic FPGA code > to get receive timestamps (secs and ticks) for the USRP1 + UHD support. What > is needed for in terms of timestamps with transmit for OpenBTS? Basically, > does it a timestamped send_at() capability? The transmit samples go out in a continuous stream so the critical timing points are the start and resync period after an interruption (underrun). For the latter, the underrun and late packet arrival behaviour is the main factor. The USRP2 will still transmit packets that arrive late, so they're checked and dropped at the host. Otherwise, we get a constant shift in the transmit slots compared to those on the receive side. Thomas

B

Belial

Thu, Nov 18, 2010 7:31 PM

Hi Thomas,

Good work! Got OpenBTS working on the USRP2.

B

On 17 November 2010 15:09, Thomas Tsou ttsou@vt.edu wrote:

I'm announcing the availability of USRP2 support with OpenBTS. The
patch set consists of a new device implementation that uses the UHD
driver from Ettus Research and allows the use of an external 10MHz
reference clock. Additional implementation details can be found in the
comments and commit log.

Download:

git clone git://github.com/ttsou/openbts-uhd.git

git clone http://github.com/ttsou/openbts-uhd.git

http://github.com/ttsou/openbts-uhd/tarball/master

GitHub:

http://github.com/ttsou/openbts-uhd

Build:

USRP2 support requires the UHD driver and firmware. GNU Radio is not
required.

http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

./bootstrap
./configure --with-uhd
make

Without the '--with-uhd' option, the standard USRP1 implementation
will be built.

Release Notes:

*The USRP2 is clocked at 100MHz and does not output fractional sample
rates, so only the non-52M Transceiver is available.

*Tested with a single WBX board, which is capable of operation on all
4 GSM bands. Other boards should work, but are untested.

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

External Reference Clock:

The front panel 10MHz reference input of the USRP2 can be used to
improve stability of the internal oscillator (~20 ppm). To test
frequency offset, a modified version of Kalibrate -
http://thre.at/kalibrate - is available. Information and examples for
the UHD development branch can be found here.

http://ttsou.github.com/kalibrate-uhd

That's about it. Hopefully, a number of people will find this useful.
Let me know if you have any questions. Comments and feedback are
always welcome.

Thomas

Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev

Openbts-discuss mailing list
Openbts-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

Hi Thomas, Good work! Got OpenBTS working on the USRP2. B On 17 November 2010 15:09, Thomas Tsou <ttsou@vt.edu> wrote: > I'm announcing the availability of USRP2 support with OpenBTS. The > patch set consists of a new device implementation that uses the UHD > driver from Ettus Research and allows the use of an external 10MHz > reference clock. Additional implementation details can be found in the > comments and commit log. > > Download: > > git clone git://github.com/ttsou/openbts-uhd.git > > git clone http://github.com/ttsou/openbts-uhd.git > > http://github.com/ttsou/openbts-uhd/tarball/master > > GitHub: > > http://github.com/ttsou/openbts-uhd > > Build: > > USRP2 support requires the UHD driver and firmware. GNU Radio is not > required. > > http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki > > ./bootstrap > ./configure --with-uhd > make > > Without the '--with-uhd' option, the standard USRP1 implementation > will be built. > > Release Notes: > > *The USRP2 is clocked at 100MHz and does not output fractional sample > rates, so only the non-52M Transceiver is available. > > *Tested with a single WBX board, which is capable of operation on all > 4 GSM bands. Other boards should work, but are untested. > > *Operation in the upper bands (1800, 1900MHz) requires an external > reference for reliable operation. This is true to a lesser extent in > the lower bands as well. > > External Reference Clock: > > The front panel 10MHz reference input of the USRP2 can be used to > improve stability of the internal oscillator (~20 ppm). To test > frequency offset, a modified version of Kalibrate - > http://thre.at/kalibrate - is available. Information and examples for > the UHD development branch can be found here. > > http://ttsou.github.com/kalibrate-uhd > > That's about it. Hopefully, a number of people will find this useful. > Let me know if you have any questions. Comments and feedback are > always welcome. > > Thomas > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Openbts-discuss mailing list > Openbts-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbts-discuss >

H

hanwen

Tue, Nov 30, 2010 9:44 PM

Hi, *,

The OpenBTS works with my USRP2+1 WBX works pretty fine. Actually, this is
the first time in my life that I successfully made a call with OpenBTS. As I
don't have RFX900/1800 boards, I tried to make it work with USRP1+WBX before
but failed.

THANKS to Thomas and other guys contribute to this UHD-supported OpenBTS!

I still got the ALARMS when starting OpenBTS:
1291152553.1603 ALARM 3073911008 TRXManager.cpp:447:setMaxDelay: SETMAXDLY
failed with status -1
1291152553.1605 ALARM 3073911008 TRXManager.cpp:458:setRxGain: SETRXGAIN
failed with status -1

And when I tried to use rxgain command to set RX gain, I still get this:
1291153403.5711 ALARM 3074988256 TRXManager.cpp:458:setRxGain: SETRXGAIN
failed with status -1
new RX gain is 0 dB

Any clue for this problem?

Cheers,
Hanwen

2010/11/17 Thomas Tsou ttsou@vt.edu

I'm announcing the availability of USRP2 support with OpenBTS. The
patch set consists of a new device implementation that uses the UHD
driver from Ettus Research and allows the use of an external 10MHz
reference clock. Additional implementation details can be found in the
comments and commit log.

Download:

git clone git://github.com/ttsou/openbts-uhd.git

git clone http://github.com/ttsou/openbts-uhd.git

http://github.com/ttsou/openbts-uhd/tarball/master

GitHub:

http://github.com/ttsou/openbts-uhd

Build:

USRP2 support requires the UHD driver and firmware. GNU Radio is not
required.

http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

./bootstrap
./configure --with-uhd
make

Without the '--with-uhd' option, the standard USRP1 implementation
will be built.

Release Notes:

*The USRP2 is clocked at 100MHz and does not output fractional sample
rates, so only the non-52M Transceiver is available.

*Tested with a single WBX board, which is capable of operation on all
4 GSM bands. Other boards should work, but are untested.

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

External Reference Clock:

The front panel 10MHz reference input of the USRP2 can be used to
improve stability of the internal oscillator (~20 ppm). To test
frequency offset, a modified version of Kalibrate -
http://thre.at/kalibrate - is available. Information and examples for
the UHD development branch can be found here.

http://ttsou.github.com/kalibrate-uhd

That's about it. Hopefully, a number of people will find this useful.
Let me know if you have any questions. Comments and feedback are
always welcome.

Thomas

Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev

Openbts-discuss mailing list
Openbts-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

Hi, *, The OpenBTS works with my USRP2+1 WBX works pretty fine. Actually, this is the first time in my life that I successfully made a call with OpenBTS. As I don't have RFX900/1800 boards, I tried to make it work with USRP1+WBX before but failed. THANKS to Thomas and other guys contribute to this UHD-supported OpenBTS! I still got the ALARMS when starting OpenBTS: 1291152553.1603 ALARM 3073911008 TRXManager.cpp:447:setMaxDelay: SETMAXDLY failed with status -1 1291152553.1605 ALARM 3073911008 TRXManager.cpp:458:setRxGain: SETRXGAIN failed with status -1 And when I tried to use rxgain command to set RX gain, I still get this: 1291153403.5711 ALARM 3074988256 TRXManager.cpp:458:setRxGain: SETRXGAIN failed with status -1 new RX gain is 0 dB Any clue for this problem? Cheers, Hanwen 2010/11/17 Thomas Tsou <ttsou@vt.edu> > I'm announcing the availability of USRP2 support with OpenBTS. The > patch set consists of a new device implementation that uses the UHD > driver from Ettus Research and allows the use of an external 10MHz > reference clock. Additional implementation details can be found in the > comments and commit log. > > Download: > > git clone git://github.com/ttsou/openbts-uhd.git > > git clone http://github.com/ttsou/openbts-uhd.git > > http://github.com/ttsou/openbts-uhd/tarball/master > > GitHub: > > http://github.com/ttsou/openbts-uhd > > Build: > > USRP2 support requires the UHD driver and firmware. GNU Radio is not > required. > > http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki > > ./bootstrap > ./configure --with-uhd > make > > Without the '--with-uhd' option, the standard USRP1 implementation > will be built. > > Release Notes: > > *The USRP2 is clocked at 100MHz and does not output fractional sample > rates, so only the non-52M Transceiver is available. > > *Tested with a single WBX board, which is capable of operation on all > 4 GSM bands. Other boards should work, but are untested. > > *Operation in the upper bands (1800, 1900MHz) requires an external > reference for reliable operation. This is true to a lesser extent in > the lower bands as well. > > External Reference Clock: > > The front panel 10MHz reference input of the USRP2 can be used to > improve stability of the internal oscillator (~20 ppm). To test > frequency offset, a modified version of Kalibrate - > http://thre.at/kalibrate - is available. Information and examples for > the UHD development branch can be found here. > > http://ttsou.github.com/kalibrate-uhd > > That's about it. Hopefully, a number of people will find this useful. > Let me know if you have any questions. Comments and feedback are > always welcome. > > Thomas > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Openbts-discuss mailing list > Openbts-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbts-discuss >

DA

David A. Burgess

Tue, Nov 30, 2010 10:00 PM

These errors probably mean you are running the 64 MHz version of the
OpenBTS transceiver, since it does not support these commands.

If you are running OpenBTS on a stock 64 MHz USRP clock,
congratulations. It often doesn't work at all, but sometimes you get
lucky.

What kind of operating range do you get with the singe WBX board and
with what antenna arrangement? Any idea of the level of tx/rx
isolation?

On Nov 30, 2010, at 1:44 PM, hanwen wrote:

Hi, *,

The OpenBTS works with my USRP2+1 WBX works pretty fine. Actually,
this is the first time in my life that I successfully made a call
with OpenBTS. As I don't have RFX900/1800 boards, I tried to make
it work with USRP1+WBX before but failed.

THANKS to Thomas and other guys contribute to this UHD-supported
OpenBTS!

I still got the ALARMS when starting OpenBTS:
1291152553.1603 ALARM 3073911008 TRXManager.cpp:447:setMaxDelay:
SETMAXDLY failed with status -1
1291152553.1605 ALARM 3073911008 TRXManager.cpp:458:setRxGain:
SETRXGAIN failed with status -1

And when I tried to use rxgain command to set RX gain, I still get
this:
1291153403.5711 ALARM 3074988256 TRXManager.cpp:458:setRxGain:
SETRXGAIN failed with status -1
new RX gain is 0 dB

Any clue for this problem?

Cheers,
Hanwen

2010/11/17 Thomas Tsou ttsou@vt.edu
I'm announcing the availability of USRP2 support with OpenBTS. The
patch set consists of a new device implementation that uses the UHD
driver from Ettus Research and allows the use of an external 10MHz
reference clock. Additional implementation details can be found in the
comments and commit log.

Download:

git clone git://github.com/ttsou/openbts-uhd.git

git clone http://github.com/ttsou/openbts-uhd.git

http://github.com/ttsou/openbts-uhd/tarball/master

GitHub:

http://github.com/ttsou/openbts-uhd

Build:

USRP2 support requires the UHD driver and firmware. GNU Radio is
not required.

http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

./bootstrap
./configure --with-uhd
make

Without the '--with-uhd' option, the standard USRP1 implementation
will be built.

Release Notes:

*The USRP2 is clocked at 100MHz and does not output fractional sample
rates, so only the non-52M Transceiver is available.

*Tested with a single WBX board, which is capable of operation on all
4 GSM bands. Other boards should work, but are untested.

*Operation in the upper bands (1800, 1900MHz) requires an external
reference for reliable operation. This is true to a lesser extent in
the lower bands as well.

External Reference Clock:

The front panel 10MHz reference input of the USRP2 can be used to
improve stability of the internal oscillator (~20 ppm). To test
frequency offset, a modified version of Kalibrate -
http://thre.at/kalibrate - is available. Information and examples for
the UHD development branch can be found here.

http://ttsou.github.com/kalibrate-uhd

That's about it. Hopefully, a number of people will find this useful.
Let me know if you have any questions. Comments and feedback are
always welcome.

Thomas

Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating
great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev

Openbts-discuss mailing list
Openbts-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with
the
Intel(R) Software Partner Program. Five $500 cash prizes are up for
grabs.
http://p.sf.net/sfu/intelisp-
dev2dev_______________________________________________
Openbts-discuss mailing list
Openbts-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbts-discuss

David A. Burgess
Kestrel Signal Processing, Inc.

These errors probably mean you are running the 64 MHz version of the OpenBTS transceiver, since it does not support these commands. If you *are* running OpenBTS on a stock 64 MHz USRP clock, congratulations. It often doesn't work at all, but sometimes you get lucky. What kind of operating range do you get with the singe WBX board and with what antenna arrangement? Any idea of the level of tx/rx isolation? On Nov 30, 2010, at 1:44 PM, hanwen wrote: > Hi, *, > > The OpenBTS works with my USRP2+1 WBX works pretty fine. Actually, > this is the first time in my life that I successfully made a call > with OpenBTS. As I don't have RFX900/1800 boards, I tried to make > it work with USRP1+WBX before but failed. > > THANKS to Thomas and other guys contribute to this UHD-supported > OpenBTS! > > I still got the ALARMS when starting OpenBTS: > 1291152553.1603 ALARM 3073911008 TRXManager.cpp:447:setMaxDelay: > SETMAXDLY failed with status -1 > 1291152553.1605 ALARM 3073911008 TRXManager.cpp:458:setRxGain: > SETRXGAIN failed with status -1 > > And when I tried to use rxgain command to set RX gain, I still get > this: > 1291153403.5711 ALARM 3074988256 TRXManager.cpp:458:setRxGain: > SETRXGAIN failed with status -1 > new RX gain is 0 dB > > Any clue for this problem? > > Cheers, > Hanwen > > > > 2010/11/17 Thomas Tsou <ttsou@vt.edu> > I'm announcing the availability of USRP2 support with OpenBTS. The > patch set consists of a new device implementation that uses the UHD > driver from Ettus Research and allows the use of an external 10MHz > reference clock. Additional implementation details can be found in the > comments and commit log. > > Download: > > git clone git://github.com/ttsou/openbts-uhd.git > > git clone http://github.com/ttsou/openbts-uhd.git > > http://github.com/ttsou/openbts-uhd/tarball/master > > GitHub: > > http://github.com/ttsou/openbts-uhd > > Build: > > USRP2 support requires the UHD driver and firmware. GNU Radio is > not required. > > http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki > > ./bootstrap > ./configure --with-uhd > make > > Without the '--with-uhd' option, the standard USRP1 implementation > will be built. > > Release Notes: > > *The USRP2 is clocked at 100MHz and does not output fractional sample > rates, so only the non-52M Transceiver is available. > > *Tested with a single WBX board, which is capable of operation on all > 4 GSM bands. Other boards should work, but are untested. > > *Operation in the upper bands (1800, 1900MHz) requires an external > reference for reliable operation. This is true to a lesser extent in > the lower bands as well. > > External Reference Clock: > > The front panel 10MHz reference input of the USRP2 can be used to > improve stability of the internal oscillator (~20 ppm). To test > frequency offset, a modified version of Kalibrate - > http://thre.at/kalibrate - is available. Information and examples for > the UHD development branch can be found here. > > http://ttsou.github.com/kalibrate-uhd > > That's about it. Hopefully, a number of people will find this useful. > Let me know if you have any questions. Comments and feedback are > always welcome. > > Thomas > > ---------------------------------------------------------------------- > -------- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating > great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Openbts-discuss mailing list > Openbts-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > ---------------------------------------------------------------------- > -------- > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with > the > Intel(R) Software Partner Program. Five $500 cash prizes are up for > grabs. > http://p.sf.net/sfu/intelisp- > dev2dev_______________________________________________ > Openbts-discuss mailing list > Openbts-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbts-discuss David A. Burgess Kestrel Signal Processing, Inc.

usrp-users@lists.ettus.com

[ANNOUNCE] OpenBTS USRP2 support