discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Re: VRT_49.0 Protocol Spec


From: Eric Blossom
Subject: Re: [Discuss-gnuradio] Re: VRT_49.0 Protocol Spec
Date: Mon, 26 Apr 2010 16:27:23 -0700
User-agent: Mutt/1.5.20 (2009-08-17)

On Mon, Apr 26, 2010 at 07:11:26PM -0400, Marcus D. Leech wrote:
> On 04/26/2010 07:01 PM, Eric Blossom wrote:
> > On Mon, Apr 26, 2010 at 03:26:46PM -0700, Matt Ettus wrote:
> >   
> >> On 04/26/2010 03:19 PM, Marcus D. Leech wrote:
> >>     
> >>> Optional fields, optional packing formats.  Rather a nightmare.  Doing a
> >>> Wireshark parser is going to
> >>>   be just so much fun :-)
> >>>       
> >>
> >> We use a very well defined subset of VRT which makes parsing a lot
> >> easier.  We don't use class fields, for example.
> >>
> >> Matt
> >>     
> > FWIW, the code that's already written handles all of the cases
> > consistently.  It wasn't a big deal.  There's a finite set of stuff
> > and there's some machine generated code that handles all the optionally
> > there/not-there cases.
> >
> > Eric
> >
> >
> >   
> Well, perhaps I should look at that code as a dissector core for
> Wireshark, then.
> 
> Does it handle the lovely "optimized for wire-format-density vs
> optimized-for-machine-processing" wire-format
>   variabilities?

Currently only handles the "optimized for machine processing" case.

Eric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]