On Mon, 22 Aug 2005, Eric Blossom wrote:
> Try stepping it from -20.0 to 0.0 by 0.1. I'm pretty sure it works.
>
> If you get a chance, can you check it again?
>
Yes - that's it, operator error, -20 to 0 gets peaks at 40 to 300.
Interestingly, if you set it back to 255 with
self.usrp._write_
On Mon, Aug 22, 2005 at 11:35:27PM +0530, Ramakrishnan Muthukrishnan wrote:
>
> Folks,
>
> I just uploaded the 2.5 version of gnuradio-core and all the other packages
> (wxgui, gr-audio-*, examples) into Debian Unstable. These are built with
> the new g++ 4.x package.
>
> Another good news is th
On Mon, Aug 22, 2005 at 01:53:55PM -0400, cswiger wrote:
> Just another stab - set_pga() seems to be screwy. With a
> usrp_siggen.py looped back to usrp_oscope.py, not using
> set_pga and amplitude 16e3 there's a signal peaking at 500.
> However, use set_pga(0,n) (n=any value from 0 to 20)
> and th
On Mon, Aug 22, 2005 at 09:08:39AM -0400, Krzysztof Kamieniecki wrote:
> Quoting Eric Blossom <[EMAIL PROTECTED]>:
> > The test code has an alignment problem under gcc 4.x (that we should fix...)
> > When run within the normal gnu radio framework, the alignment
> > constraint is met and the right a
On Mon, Aug 22, 2005 at 08:35:08AM -0400, Krzysztof Kamieniecki wrote:
> Quoting Eric Blossom <[EMAIL PROTECTED]>:
> >
> > I'm open for suggestions as to how we should select SSE vs 3DNow.
> > Shall we benchmark the first time through and store the answer?
> >
> I would be happy with a manual sel
Folks,
I just uploaded the 2.5 version of gnuradio-core and all the other packages
(wxgui, gr-audio-*, examples) into Debian Unstable. These are built with
the new g++ 4.x package.
Another good news is that wxgtk 2.6 is now in Debian unstable. So those of
you who were waiting for it (after the a
Just another stab - set_pga() seems to be screwy. With a
usrp_siggen.py looped back to usrp_oscope.py, not using
set_pga and amplitude 16e3 there's a signal peaking at 500.
However, use set_pga(0,n) (n=any value from 0 to 20)
and the signal drops to about 300. Checking with
print self.usrp._rea
Hi Martin,
> Did you copy the risc code from another driver or
> did you specially make it for this driver?
It's a new risc code I guess. I did not really look at
the risc code for cx88 driver to see whether it is the
same and I doubt it is the same. I just been through
the code, notice there are
Quoting Eric Blossom <[EMAIL PROTECTED]>:
> On Mon, Aug 22, 2005 at 12:44:58AM -0400, Krzysztof Kamieniecki wrote:
> > Hello All,
> >
> > It seems like something may have broken in the 3Dnow fir code (on Debian
> > Unstable), it may be GNURadio or it may be GCC. Has anybody seen this?
> >
> >
Quoting Eric Blossom <[EMAIL PROTECTED]>:
> On Mon, Aug 22, 2005 at 12:44:58AM -0400, Krzysztof Kamieniecki wrote:
> > Hello All,
> >
> > It seems like something may have broken in the 3Dnow fir code (on Debian
> > Unstable), it may be GNURadio or it may be GCC. Has anybody seen this?
> >
> >
>
On Mon, Aug 22, 2005 at 12:44:58AM -0400, Krzysztof Kamieniecki wrote:
> Hello All,
>
> It seems like something may have broken in the 3Dnow fir code (on Debian
> Unstable), it may be GNURadio or it may be GCC. Has anybody seen this?
>
>
> SSE seems to be faster on this processor anyways, is th
11 matches
Mail list logo
