On Mon, Jan 29, 2007 at 10:23:15AM -0800, Dan Halperin wrote:
> An unanswered question from before:
> >> Also, another (incidental) question, I get really bad performance when the
> >> fusb_options set by realtime being true are used
> >>
> What are the fusb_options all about, and how ca
An unanswered question from before:
>> Also, another (incidental) question, I get really bad performance when the
>> fusb_options set by realtime being true are used
>>
What are the fusb_options all about, and how can I get intuition on the
right settings for them?
> I think you're burnin
On Sat, Jan 27, 2007 at 04:25:19PM -0800, Dan Halperin wrote:
> Eric Blossom wrote:
> > overruns or underruns?
> >
>
> uO means a USRP Overrun right?
Yes.
> > Underruns are to be expected with tunnel.py, assuming that you're not
> > feeding it data constantly.
> >
> > (When the in-band signal
Eric Blossom wrote:
> overruns or underruns?
>
uO means a USRP Overrun right?
> Underruns are to be expected with tunnel.py, assuming that you're not
> feeding it data constantly.
>
> (When the in-band signaling stuff is complete, we'll have a more
> sensible interpretation for the underrun ca
On Sat, Jan 27, 2007 at 01:47:09PM -0800, Dan Halperin wrote:
> Hi,
>
> I'm trying to figure out what the right tools are to debug problems like
> overruns in the USRP. I have a modified version of tunnel.py running (I
> basically took out the tun/tap interfaces and added my own on top), and
> I'm
Hi,
I'm trying to figure out what the right tools are to debug problems like
overruns in the USRP. I have a modified version of tunnel.py running (I
basically took out the tun/tap interfaces and added my own on top), and
I'm finding things like after exactly 700 128-byte packets I see an
overrun -
