On 12/13/2010 05:28 PM, Josh Blum wrote:
>
>
> On 12/13/2010 05:04 PM, b...@sigmatix.com wrote:
>> Josh,
>>
>> This is great!
>>
>> Although it goes without saying, I'm assuming users should also need
>> to keep in mind that there's no magic going on here w.r.t. gigE
>> bandwidth (i.e., one U2
On Dec 13, 2010, at 7:33 PM, Tom Rondeau wrote:
> The biggest problem that I see with cmake is that the burden of proof
> lies with cmake.
I'm 100% confident that CMake, or QMake for that matter (and, I'm sure, BJam
and other build tools), could handle the GNU Radio build system robustly if
some
On 12/13/2010 05:04 PM, b...@sigmatix.com wrote:
> Josh,
>
> This is great!
>
> Although it goes without saying, I'm assuming users should also need
> to keep in mind that there's no magic going on here w.r.t. gigE
> bandwidth (i.e., one U2 running "wide open" can pretty much consume
> an entir
> The biggest problem that I see with cmake is that the burden of proof
> lies with cmake. We have years of building up the project
> configuration in autotools and every problem we have come across has
> been solvable and solved in this framework. While some/many of these
> problems might have bee
Josh,
This is great!
Although it goes without saying, I'm assuming users should also need to keep
in mind that there's no magic going on here w.r.t. gigE bandwidth (i.e., one U2
running "wide open" can pretty much consume an entire gigE port. Now that
you've got 2 U2's sharing a single con
Hello list,
I would like to announce support for the MIMO cable with UHD. The
support is experimental, so its not in the mainline yet, and is only
available for USRP2 at the moment.
The source for the FPGA code has not yet been pushed but you can get the
pre-built images here:
http://www.ettus.co
On Sat, Dec 11, 2010 at 1:55 PM, Josh Blum wrote:
> Hey list,
>
> I would like to share my experiences with CMake.
>
> I started using CMake because I needed a cross-platform build system for
> making UHD and I stumbled upon CMake. After learning CMake and building
> UHD on-top of it, I can conclu
On 12/13/2010 01:51 AM, Josh Blum wrote:
2) A build from git source would be the same as a build from a release
tarball (because we just tar.gz'd up the source tree itself). So in a
sense, it provides a build uniformity.
This is a good point.
Ok, back to the books again, I will give it a try o
On 12/12/2010 07:43 PM, Andrew Ge wrote:
Josh or Matt,
Would you please tell me which TI OMAP processor is exactly used in
E100, OMAP3530 or OMAP 3525 or other?
Also, is there some hardware architecture diagram available somewhere?
What software support is currently available?
We have updated
The git next branch has recently had some issues with performing a
"make distcheck" if you didn't have the UHD libraries installed onto
your system. I believe I have just pushed a fix for this.
If you've been having trouble performing a distcheck because of this,
try it now. Let me know if you're
Hey Tom,
Great work implementing the libvolk. I had a chance to take a peek at
the implementation, so now I have constructive criticism. :-)
I see that the various vector functions are all implemented in headers,
and at compile time, a python application generates them into the table
look-up-code
Hello:
I have a USRP2 + WBX running with GNU Radio 3.3.0 on openSUSE 11.2.
In my flowgraph, I am trying to create a timer that will call a function
periodically, say every 200ms. This function would dynamically change some
parameters of my flowgraph, such as the frequency or amplitude of a Sign
Hi, I am a fellow n00b to gnuradio. Just to add to Tom's advice, when I
first started I found that the easiest and quickest way to get familiar with
gnuradio is with the gnuradio companion (and reading everything you can find
on gnuradio...). Try searching the web for "gnuradio tutorials." Some
Looks like these files were not moved from gnuradio/usrp.
A symlink in fpga/usrp1 to ../../gnuradio/usrp/firmware seems to do the
trick, but it would be nice if one of the repos had everything necessary.
On 12/13/2010 12:49 PM, Brett L. Trotter wrote:
> `include "../../firmware/include/fpga_regs
`include "../../firmware/include/fpga_regs_common.v"
`include "../../firmware/include/fpga_regs_standard.v"
these seem to be absent from the repo obtained here: git clone
git://git.ettus.com/ettus/fpga.git
Where can I find those files?
___
Discuss-gnu
On 12/12/2010 07:43 PM, Andrew Ge wrote:
Josh or Matt,
Would you please tell me which TI OMAP processor is exactly used in
E100, OMAP3530 or OMAP 3525 or other?
We use the Gumstix Overo Tide module which has an OMAP3530 at 720 MHz
with 512 MB of RAM.
Also, is there some hardware architectu
On Mon, Dec 13, 2010 at 5:58 AM, wrote:
> Hello every one...
>
> I am just start to learn gnu radio...
> i start to track its C++ part...
> i start it with usrp_source_s/c files...
>
> can any one tell me that i am on the right way or not...
> & how can i go further...
>
>
> i also found a method
Hello every one...
I am just start to learn gnu radio...
i start to track its C++ part...
i start it with usrp_source_s/c files...
can any one tell me that i am on the right way or not...
& how can i go further...
i also found a method gnuradio::get_initial_sptr() which takes an object...
but i
On Mon, Dec 13, 2010 at 4:43 AM, Andrew Ge wrote:
> Josh or Matt,
>
> Would you please tell me which TI OMAP processor is exactly used in E100,
> OMAP3530 or OMAP 3525 or other?
I can only guess, but it was mentioned in the announcement thread that
the board has 512 MB RAM, which suggests it it t
19 matches
Mail list logo
