Re: [Discuss-gnuradio] m-block timeouts, time passed

2008-04-25 Thread David Li
Hi George, I browsed through cmac.cc and got a few questions: 1. Can you explain more about Without m block to gr block connection, all raw samples are forced thru the MAC layer? 2. What kind of applications are needed to interface with your MAC code to do CS configuration and data

Re: [Discuss-gnuradio] m-block timeouts, time passed

2008-04-25 Thread George Nychis
David Li wrote: Hi George, I browsed through cmac.cc and got a few questions: 1. Can you explain more about Without m block to gr block connection, all raw samples are forced thru the MAC layer? Ahhh I need to change that comment. That comment is no longer true. The samples hit the PHY

Re: [Discuss-gnuradio] m-block timeouts, time passed, or

2008-04-24 Thread George Nychis
David Li wrote: Hi George, I am interested in your MAC work. Does it run in the kernel or user space? Does it interact with IP? Is there a branch that I can download and play with it? I have two USRP 2400 boxes. Hi David, Put your reading glasses on. To do MAC work in GNU

Re: [Discuss-gnuradio] m-block timeouts, time passed, or

2008-04-23 Thread David Li
Hi George, I am interested in your MAC work. Does it run in the kernel or user space? Does it interact with IP? Is there a branch that I can download and play with it? I have two USRP 2400 boxes. Thanks. - David Li Eric Blossom wrote: What your asking for would be hard

[Discuss-gnuradio] m-block timeouts, time passed, or pause?

2008-04-21 Thread George Nychis
Is there any way to get an approximate amount of time that has elapsed since a timeout has been scheduled? Or better yet, a way to pause a timer? This is extremely useful for backoff periods in MAC contention protocols. Where, for instance, the timer is only decremented when the channel is

Re: [Discuss-gnuradio] m-block timeouts, time passed, or pause?

2008-04-21 Thread Eric Blossom
On Mon, Apr 21, 2008 at 10:57:25PM -0400, George Nychis wrote: Is there any way to get an approximate amount of time that has elapsed since a timeout has been scheduled? Or better yet, a way to pause a timer? Nope. This is extremely useful for backoff periods in MAC contention protocols.

Re: [Discuss-gnuradio] m-block timeouts, time passed, or pause?

2008-04-21 Thread George Nychis
Eric Blossom wrote: How often are you checking for channel idle? Couldn't you just cancel and schedule a new one each time you check for channel idle? A new RSSI value is computed at the host with every new block of samples. It doesn't use the FPGA value. I suppose there is an

Re: [Discuss-gnuradio] m-block timeouts, time passed, or pause?

2008-04-21 Thread Eric Blossom
On Mon, Apr 21, 2008 at 11:18:22PM -0400, George Nychis wrote: Eric Blossom wrote: How often are you checking for channel idle? Couldn't you just cancel and schedule a new one each time you check for channel idle? A new RSSI value is computed at the host with every new block of samples.

Re: [Discuss-gnuradio] m-block timeouts, time passed, or pause?

2008-04-21 Thread George Nychis
Eric Blossom wrote: What your asking for would be hard to do using the existing framework. I still don't understand where you want to do this from. That is, which code would be making the determination that it was time to pause or unpause the timer. For instance, a new node enters a