[Discuss-gnuradio] OpenBTS wiki moved back to GNU Radio

2009-09-18 Thread David Burgess

All -

The OpenBTS wiki has been moved back to http://gnuradio.org/trac/wiki/ 
OpenBTS after it's 10-month stay at sourceforge.


The trac tickets will remain at sourceforge for now.

We are in the process of updating the OpenBTS source code at GNU  
Radio and will make addition status postings as that work proceeds.


-- David

David A. Burgess
Kestrel Signal Processing, Inc.






___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] building fpga code in QuartusII

2009-09-18 Thread Rushikesh Khasgiwale
I am trying to modify the fpga verilog code for usrp1. I have installed 
Quartus-II on windows. does anyone know how to build the code? is there a 
project file?


I need a single Tx and Rx channel(both I-Q). can I modify the verilog code 
along the lines of inband1rxhb_1tx.rbf ?

This would free up some space on the fpga for my code.

thanks
-Rushikesh 




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] USRP: libusb-1.0 branch

2009-09-18 Thread Thomas Tsou
I pushed an update of the libusb-1.0 support patch to a public github
repository.

Public clone

git clone git://github.com/ttsou/gnuradio-libusb-1.0.git

Viewable at

http://github.com/ttsou/gnuradio-libusb-1.0

Libusb-1.0 is enabled with,

./configure --fusb-tech=libusb1

Why libusb-1.0?
The prior version of libusb provided a portable user-level library that
worked well for USB initialization and configuration, but the synchronous
calls proved incapable of supporting higher USRP data rates. To get around
this, gnuradio requires some novel approaches to combine libusb with OS
specific transfer methods. libusb-1.0 introduces an asynchronous I/O
interface, which provides an alternative approach to the current multi-OS
strategy.

Compatibility
The libusb-1.0 API is incompatible with prior libusb-0.12 interfaces. There
are quite a few similarities, however, that do exist. Because libusb-1.0 is
fairly new, and current availability is limited to Linux and Darwin,
libusb-0.12 support is necessary for the indefinite future. Eric asked me to
figure out how to cleanly support libusb-0.12 and libusb-1.0. This is the
main addition of this update.

Changes
The installed interfaces are virtually unchanged. An extra argument required
for libusb-1.0 defaults to null and is ignored in non-libusb1 builds, so
existing packages that build against previous low-level code are unaffected.
This change only affects usrp_prims. Also, some version dependent headers
are generated out of the configure scripts. The code generation isn't ideal
at this moment causing a number of Makefile warnings.

Testing
With this branch on Fedora 11, I get 32Mb/s on all of my machines using
test_usrp_standard_rx or tx. I still need to find some time and put oprofile
on it to compare against the native Linux USB devio implementation. That is
unlikely to happen within the next few weeks though.

Information on the original patch can be found in the gnuradio-patch
archives.

http://lists.gnu.org/archive/html/patch-gnuradio/2009-08/msg3.html

Comments welcome. Thanks.

--
Thomas
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] start_rx_streaming_at patch

2009-09-18 Thread Mattias Kjellsson



And what is VRT code?
  

I think that VRT is also referred to as VITA.

I think http://www.pentek.com/whatsnew/ViewRelease.cfm?Index=107
may be a start.

//Mattias


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] start_rx_streaming_at patch

2009-09-18 Thread Philip Balister

Bruce McGuffin wrote:


Doug

And what is VRT code?

I googled VRT,  but the choices I got were:
  Vestibular Rehabilitation Therapy
  Vulnerability Research Team
  Vlaamse Radio- en Televisieomroep (my personal favorite)
or
  Video Round Table


http://www.digitalif.org/

Philip




Bruce

Douglas Geiger wrote:

Bruce,
 In the firmware directory the important files are the app_common_v2.c
and .h file, and txrx.c (serdes_txrx.c and a bunch of the others I
think are mainly for testing). It looks like the host code (i.e. the
patches to libusrp2) all applied successfully, which is good. I have
been using that code, so if you are able to manually apply the patch
(i.e. go in and figure out where the changes need to happen - there's
a couple added functions, and some changes made in the control loop of
app_common and txrx). My patch added code to serdes_txrx,
mimo_tx_slave, and factorytest only because I added a function
declaration in app_common_v2, and so I needed a NOP definition in
those .c files for the build to be successful.
 In this end this patch was just a hack to get the functionality I
needed until the switchover to the VRT code on the USRP2 - so yes, it
works (i.e. it will wait to start streaming rx samples back until the
fpga clock/counter reaches the specified number), but it's not meant
to be the long-term solution.
 Doug

 




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio



smime.p7s
Description: S/MIME Cryptographic Signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] start_rx_streaming_at patch

2009-09-18 Thread Bruce McGuffin


Doug

And what is VRT code?

I googled VRT,  but the choices I got were:
  Vestibular Rehabilitation Therapy
  Vulnerability Research Team
  Vlaamse Radio- en Televisieomroep (my personal favorite)
or
  Video Round Table

Bruce

Douglas Geiger wrote:

Bruce,
 In the firmware directory the important files are the app_common_v2.c
and .h file, and txrx.c (serdes_txrx.c and a bunch of the others I
think are mainly for testing). It looks like the host code (i.e. the
patches to libusrp2) all applied successfully, which is good. I have
been using that code, so if you are able to manually apply the patch
(i.e. go in and figure out where the changes need to happen - there's
a couple added functions, and some changes made in the control loop of
app_common and txrx). My patch added code to serdes_txrx,
mimo_tx_slave, and factorytest only because I added a function
declaration in app_common_v2, and so I needed a NOP definition in
those .c files for the build to be successful.
 In this end this patch was just a hack to get the functionality I
needed until the switchover to the VRT code on the USRP2 - so yes, it
works (i.e. it will wait to start streaming rx samples back until the
fpga clock/counter reaches the specified number), but it's not meant
to be the long-term solution.
 Doug

  





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] about Bui lding wxPython in Cygwin‏

2009-09-18 Thread Don Ward

Li Mei-Wen wrote:

When I do the setp (9) (http://gnuradio.org/trac/wiki/wxPythonCygwinon 
windows)


python setup.py build_ext --inplace WXPORT=msw COMPILER=cygwin 
BUILD_GLCANVAS=0 BUILD_GIZMOS=0 UNICODE=0


I get sfollowing error message.
What can I do?

administra...@888tiger-452d27 /usr/src/wxPython-src-2.8.10.1/wxPython
$ python setup.py build_ext --inplace WXPORT=msw COMPILER=cygwin 
BUILD_GLCANVAS

=0 BUILD_GIZMOS=0 UNICODE=0
WARNING: WXWIN not set in environment. Assuming '..'
Found wx-config: /usr/local/bin/wx-config
   Using flags:  --toolkit=msw --unicode=no --version=2.8
Preparing CORE...
Preparing STC...
running build_ext
building '_controls_' extension
writing build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_.def
g++ -mcygwin -shared -s 
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap
.o 
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_.def -L/usr/local/lib  
-L/

usr/lib/python2.5/config -lwx_msw_richtext-2.8 -lwx_msw_aui-2.8 -lwx_msw_xrc-2.8
-lwx_msw_qa-2.8 -lwx_msw_html-2.8 -lwx_msw_adv-2.8 -lwx_msw_core-2.8 -lwx_base_
xml-2.8 -lwx_base_net-2.8 -lwx_base-2.8 -lpython2.5 -o wx/_controls_.dll
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xce4e8): undefined reference to 
`__imp___ZTV23wxDatePickerCtrlGeneric'

[snipped]

Did you make the change to setup.h described in step (4)?
Note: In versions 2.8.8.1, 2.8.9.1, and 2.8.10.1 you will need to find the 
file build-local/lib/wx/include/msw-ansi-release-2.8/wx/setup.h and after 
the line:


#define wxUSE_DATEPICKCTRL 1
add another line:

#define wxUSE_DATEPICKCTRL_GENERIC 1
before going to the next step.

-- Don W.



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] a bout Building wxPython in Cygw in‏

2009-09-18 Thread Li Mei-Wen

When I do the setp (9) (http://gnuradio.org/trac/wiki/wxPythonCygwinon 
windows)

python setup.py build_ext --inplace WXPORT=msw COMPILER=cygwin BUILD_GLCANVAS=0 
BUILD_GIZMOS=0 UNICODE=0

 I get sfollowing error message.
 What can I do?

administra...@888tiger-452d27 /usr/src/wxPython-src-2.8.10.1/wxPython
$ python setup.py build_ext --inplace WXPORT=msw COMPILER=cygwin BUILD_GLCANVAS
=0 BUILD_GIZMOS=0 UNICODE=0
WARNING: WXWIN not set in environment. Assuming '..'
Found wx-config: /usr/local/bin/wx-config
Using flags:  --toolkit=msw --unicode=no --version=2.8
Preparing CORE...
Preparing STC...
running build_ext
building '_controls_' extension
writing build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_.def
g++ -mcygwin -shared -s build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap
.o build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_.def -L/usr/local/lib -L/
usr/lib/python2.5/config -lwx_msw_richtext-2.8 -lwx_msw_aui-2.8 -lwx_msw_xrc-2.8
 -lwx_msw_qa-2.8 -lwx_msw_html-2.8 -lwx_msw_adv-2.8 -lwx_msw_core-2.8 -lwx_base_
xml-2.8 -lwx_base_net-2.8 -lwx_base-2.8 -lpython2.5 -o wx/_controls_.dll
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xce4e8): undefined reference to `__imp___ZTV23wxDatePickerCtrlGeneric'
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xce4f3): undefined reference to `__imp___ZN23wxDatePickerCtrlGeneric4InitE
v'
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xce55e): undefined reference to `__imp___ZN23wxDatePickerCtrlGeneric6Creat
eEP8wxWindowiRK10wxDateTimeRK7wxPointRK6wxSizelRK11wxValidatorRK8wxString'
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xceeed): undefined reference to `__imp___ZTV23wxDatePickerCtrlGeneric'
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xceef8): undefined reference to `__imp___ZN23wxDatePickerCtrlGeneric4InitE
v'
build/temp.cygwin-1.5.25-i686-2.5/src/msw/_controls_wrap.o:_controls_wrap.cpp:(.
text+0xcf41d): undefined reference to `__imp___ZN23wxDatePickerCtrlGeneric6Creat
eEP8wxWindowiRK10wxDateTimeRK7wxPointRK6wxSizelRK11wxValidatorRK8wxString'
collect2: ld returned 1 exit status
error: command 'g++' failed with exit status 1

  
_
隨身的 Windows Live Messenger 和 Hotmail,不限時地掌握資訊盡在指間 — Windows Live for Mobile
http://3c.msn.com.tw/mobile/___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio