On Thu, Nov 06, 2008 at 05:02:46PM +0100, Mattias Kjellsson wrote:
> Eric Blossom wrote:
>>
> Then I probably have to read up on what VRT is...
>>> The timestamp in the same header, supposed to reflect when it's going
>>> to be sent out on the antenna, when it was received to the usrp2,
>>>
Eric Blossom wrote:
On Wed, Nov 05, 2008 at 07:30:01PM +0100, Mattias Kjellsson wrote:
Eric Blossom wrote:
There are a couple of headers. See usrp2_eth_packet.h
So I have. Regarding the channel and timestamp fields in "struct
u2_fixed_hdr_t", channel is going to (when implemen
On Wed, Nov 05, 2008 at 07:30:01PM +0100, Mattias Kjellsson wrote:
> Eric Blossom wrote:
>>
>> There are a couple of headers. See usrp2_eth_packet.h
>
> So I have. Regarding the channel and timestamp fields in "struct
> u2_fixed_hdr_t", channel is going to (when implemented) reflect which
> u
Eric Blossom wrote:
On Wed, Nov 05, 2008 at 06:15:03PM +0100, Mattias Kjellsson wrote:
I have been playing with ioctl's today and while browsing the USRP2-
code i found that max length of a packet is defined to 371 which results
in 1484 bytes of "data", and 16 bytes left, leaving room for
On Wed, Nov 05, 2008 at 06:15:03PM +0100, Mattias Kjellsson wrote:
> I have been playing with ioctl's today and while browsing the USRP2-
> code i found that max length of a packet is defined to 371 which results
> in 1484 bytes of "data", and 16 bytes left, leaving room for the 14 byte
> eth
I have been playing with ioctl's today and while browsing the USRP2-
code i found that max length of a packet is defined to 371 which results
in 1484 bytes of "data", and 16 bytes left, leaving room for the 14 byte
ethernet header, but not a 372:nd sample, since each sample is 4 bytes.
But whe
