On Thu, Feb 10, 2005 at 08:54:17PM -0500, kilian wrote:
> Hi,
>
> On Thu, 2005-02-10 at 12:25, Eric Blossom wrote:
>
> > > to it. After I found out that I had to upload the firmware first, using
> > > 'burn-usrp2-eeprom', I ran test_usrp0 and got the following output:
> >
> > First off do you ha
Hi,
On Thu, 2005-02-10 at 12:25, Eric Blossom wrote:
> > to it. After I found out that I had to upload the firmware first, using
> > 'burn-usrp2-eeprom', I ran test_usrp0 and got the following output:
>
> First off do you have a rev0 or rev2 board? The rev0 board doesn't
> have any daughterboar
How can I pass complex output to audio sink ?
EX:
audio_sink = audio.sink(input_rate)
.
fg.connect (filter, fmmod)
fg.connect (fmmod, audio_sink)
where fmmod produces complex output.
Thanks,
Meenal
___
Discuss-gnuradio mailing list
Discus
Oh, and another thing - after you change the Makefile, go into the
gnuradio-core directory, not the gr-build directory, and just run
"make". Take a look at the "buildit" script to see what other things you
need to do. If you just run that script directly, it will in fact
rewrite the Makefile.
---
You didn't quite understand my instructions correctly. I didn't have the
lines in front of me, but now that I do, change:
LTASCOMPILE = $(LIBTOOL) --mode=compile $(AS) $(AM_ASFLAGS) $(ASFLAGS)
to
LTASCOMPILE = $(LIBTOOL) --mode=compile $(CCAS) $(CCASFLAGS)
It worked for me.
However, if, as Eri
On Mon, Feb 07, 2005 at 08:53:39PM -0600, David Young wrote:
>
> Rahul,
>
> I have been thinking a little about how to produce a novel MAC, without
> spending gobs of time & money. Here are some ideas:
>
> 1 Use an off-the-shelf 802.11 card. Change its mode from
> PCF/DCF usi
Quoting kilian <[EMAIL PROTECTED]>:
> mentioned USB performance and now I would like to add another data point
> to it. After I found out that I had to upload the firmware first, using
> 'burn-usrp2-eeprom', I ran test_usrp0 and got the following output:
Thanks for the data. 24 MB/s isn't too ba
On Thu, Feb 10, 2005 at 01:32:21AM -0500, kilian wrote:
>
> Hi,
>
> I received the usrp a short time ago and was so far able to at least
> compile the basic toolset comming with the usrp-0.7 tarball. The host is
> a dual [EMAIL PROTECTED] running yellowdog-linux-4.0 . I had no luck compiling
> gn
On Thu, Feb 10, 2005 at 04:45:57AM -0800, MJ wrote:
> Hey people,
>
> I wonder if anyone can point me in the right
> direction.I started gentoo linux about 4 weeks ago
> so please excuse my noobiness.
>
> Grabbing the files from cvs is fine. After doing a
> "./for-all-dirs ../buildit" the fol
Debian mc4020 users:
Here are a few notes on using the mc4020 driver with Debian GNU/Linux
(version testing / Sarge).
1. The "autoconf" package is needed. If both the "autoconf" and
"autoconf2.13" packages are installed ./bootstrap fails. To work around this
either remove autoconf2.13 or edit the b
After changing:
LTASCOMPILE = $(LIBTOOL) --mode=compile $(AS)
$(AM_ASFLAGS) $(ASFLAGS)
to
LTASCOMPILE = $(LIBTOOL) --mode=compile $(CCAS)
$(CCASFLAGS) $(AS) $(ASFLAGS)
and then running "./for-all-dirs ../buildit" it still
gives the same error. The Makefile is overwritten back
to the way it was
Hi Ilia,
Thanks for the reply. How do i stop Makefile from
getting overwritten when i do a "./for-all-dirs
../buildit"?
It says this at the top of Makefile:
"# This file is machine generated. All edits will be
overwritten"
thanks
--- Ilia Mirkin <[EMAIL PROTECTED]> wrote:
> That's funny... I
That's funny... I had the exact same problem, on gentoo. The way I fixed
it was to edit the Makefile in that directory (src/lib/filter), changing
the LTASCOMPILE definition from like
libtool --mode=compile . $(AS) $(ASFLAGS)
or something along those lines to
libtool --mode=compile $(CCAS) $(
Hey people,
I wonder if anyone can point me in the right
direction.I started gentoo linux about 4 weeks ago
so please excuse my noobiness.
Grabbing the files from cvs is fine. After doing a
"./for-all-dirs ../buildit" the following error stops
the rest of the compile.
make all-am
make[5]: E
14 matches
Mail list logo
