This seems like a good idea, though kind of unusual to me. Is this a
standard or recommended way of implementing timed processing in Unix so as
to allow multiple timed events to be scheduled?
- Original Message -
From: "Daniel O'Connor" <[EMAIL PROTECTED]>
To:
Cc: "Eric Blossom" <[EM
Ok, a rough atsc transmitter benchmark: as it is now with almost
all the signal processing still taking place in the 0.9 code, that
is, one processor running 100% and the 2.0 script in the single
digit percent utilization - a 9 second mpeg stream takes 104
seconds to encode. Using 2GHz Opterons.
Shravan -
On Thu, Nov 02, 2006 at 03:53:35PM -0600, Shravan Rayanchu wrote:
> I was going through some gnuradio documentation (on comsec.org wiki)
> which says "...16-bit I and 16-bit Q data (complex), resulting in 8M
> complex samples/sec across the USB (32 Mbps max. data rate). This
> provides a
>Yes. Chances are, however, that your cppunit has been
compield with a>different compiler version than the one used to build
gnuradio. In>such cases, linking may result in such
mismatches.>I'd try compiling 1.12.0 from scratch, without using
cygwin prebuilt packages.>Tomasz
Tried it too..
Gang - I've been playing with the atsc transmitter and have a few notes
to report.
First, a good definition of "real time transmitter" would include a
firewire video camera, the processing to make an mpeg transport stream
(whatever that is, I'm not a video guy), then the atsc_tx out to the
usrp a
Does that mean 8Mhz is the max. width of spectrum I can sense? But I
remember reading on some post that we can sense spectrum upto +/-15MHz
from the carrier frequency. (i.e. a chunk of 30 Mhz). Which one of the
above is correct? What puts a limit on the maximum amount of spectrum
we can sense?
Al
Hello everyone,
I was going through some gnuradio documentation (on comsec.org wiki)
which says "...16-bit I and 16-bit Q data (complex), resulting in 8M
complex samples/sec across the USB (32 Mbps max. data rate). This
provides a maximum effective total spectral bandwidth of about
6MHz...".
By
Yes. Chances are, however, that your cppunit has been compield with a
different compiler version than the one used to build gnuradio. In
such cases, linking may result in such mismatches.
I'd try compiling 1.12.0 from scratch, without using cygwin prebuilt packages.
Tomasz
On 11/2/06, [EMAIL PR
Title: Re: [Discuss-gnuradio] reg: GNU RADIO BUILD PROBLEM
>To me it seems like a cppunit ABI mismatch.. Try getting the
most>recent source for cppunit and build it...>but, I never
used cygwin, I might be wrong.>Tomasz
The cpp unit i'm using is 1.12.0 (as instructed in the build guide)
I am currently working at Princeton University in a department responcible for some fMRI dsp work and managing a cluster for image processing.
We are currently discussing new projects to use the cluster for including a new tool for performing the different comparisons and algorithms in an easy t
To me it seems like a cppunit ABI mismatch.. Try getting the most
recent source for cppunit and build it...
but, I never used cygwin, I might be wrong.
Tomasz
>Well, if you want to use automake-1.10.x series (which is default on
>Gentoo Linux ATM) you can add the line
>AM_PROG_AS
>somewhere in
>Well, if you want to use automake-1.10.x series
(which is default on>Gentoo Linux ATM) you can add the
line>AM_PROG_AS>somewhere in the configure.ac, ./bootstrap and
./configure>Tomasz
Did that Exactly
that and the problem with the ./bootstrap went away and ./configure went
successfully f
%-style pattern rules are not errors, they are just warnings, nothing
to worry about (unless you use non-gnu make).
AM_PROG_AS - I don't know how it does that, but it makes automake
create all necessary Makefile.in files across the tree. By doing so,
it's possible to run ./configure and successfu
Re: [Discuss-gnuradio] reg: GNU RADIO BUILD PROBLEMI get the same errors
(except for those in pstoedit.m4) after updating
Cygwin automake to 1.10-1 and autoconf2.5 to 2.60-1 (the "current"
versions on my Cygwin mirror).
I am working with a several-weeks-old svn checkout of GNU Radio.
In addition
[EMAIL PROTECTED] wrote:
>
>
> >The first issue, with the automake version, can be addressed in the
> >Cygwin setup.exe program. It should be offering you version 1.9.6. If
> >it is not, the mirror you selected must be out of date.
>
> A cygcheck revealed the automake version as u indicated
>
Title: Re: [Discuss-gnuradio] reg: GNU RADIO BUILD PROBLEM
>The first issue, with the
automake version, can be addressed in the>Cygwin setup.exe program.
It should be offering you version 1.9.6. If>it is not, the mirror
you selected must be out of date.
A cygcheck revealed the aut
On Thu, 2006-11-02 at 14:15 -0500, Don Ward wrote:
> I think Shriram had automake vesion 1.10, which is offered as the new
> "current" version on the Cygwin mirror site that I use. Unless they broke
> something going to the new version, it should work. It sounds like the
> version listings on th
The first issue, with the automake version, can be addressed in the
Cygwin setup.exe program. It should be offering you version 1.9.6. If
it is not, the mirror you selected must be out of date.
I think Shriram had automake vesion 1.10, which is offered as the new
"current" version on the Cygwi
On 11/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>http://lists.gnu.org/archive/html/discuss-gnuradio/2006-10/msg00378.html
I tried that link but could not identify how the problem was solved!!!
Well, if you want to use automake-1.10.x series (which is default on
Gentoo Linux ATM) you ca
On Fri, 2006-11-03 at 00:06 +0530, [EMAIL PROTECTED] wrote:
> Even I thought of the same thing and I have tried with cygwin packages
> downloaded from almost four or five mirrorsFrom what you say,
> the problem seems to be with cygwin package, but how do I rectify it??
> Can you be more sp
>> I have tried this
with both the release 3.0 and the 3.0rc3 but get the>> same message.
Before I updated my cygwin package, I used the same>> source and was
able to build the GNUradio code fully without errors>> (But the
programs didnt work though!!).>Given the above two issues, it appears
On Thu, 2006-11-02 at 18:53 +0530, [EMAIL PROTECTED] wrote:
> /usr/share/automake-1.10/am/depend2.am:
GNU Radio requires automake 1.7.4 or later, as documented in the README
in the root directory of the source tree. Cygwin's website currently
lists automake 1.9.6 as the most recent available thro
Hello,
I have a RFX2400 board and can anyone tell me where i could find examples to
run on the board which works at 2.4 - 2.9 Ghz
Thanks,
Ravi
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-
I am using an external clock at 64MHz that will sync the USRP
with the rest of my system.
Can you talk a little bit more about this? I understand that when
there's a mismatch between the soundcard and the USRP you can get
underruns; this manifests itself (on my machine anyway) as an annoying
When running both usrp_oscope and usrp_fft, I lose the signal and the
GUI becomes unresponsive after 5 - 30 minutes of operation. I had
previously ran this system for more than 24 hours with an installation
on a laptop back in July. Here is a short summary of my setup:
1. Dual HT Intel 64-bit
When running both usrp_oscope and usrp_fft, I lose the
signal and the GUI becomes unresponsive after 5 - 30 minutes of
operation. I had previously ran this system for more than 24 hours with
an installation on a laptop back in July. Here is a short summary of my
setup:
1. Dual HT Intel 64-bit
>Date: Wed, 1 Nov 2006
22:06:10 +1100>Sorry to hear that u still have problems building
gnuradio.>This link might be useful.>http://lists.gnu.org/archive/html/discuss-gnuradio/2006-10/msg00378.html>Cheers>Kyle
I tried that link but could
not identify how the problem was solved!!!
Thanks,
s
Title: Re: [Discuss-gnuradio] reg: GNU RADIO BUILD PROBLEM
> >I was not able to find makefile.in the
"gnuradio/gnuradio-core/src/lib/filter" >>directory. Why is the ./configure asking for> >that file when it seems to
be not included with the package??>Normally, that file is created
when y
28 matches
Mail list logo
