On Thu, Sep 15, 2016 at 2:16 AM, Guy Harris wrote:
> On Sep 14, 2016, at 7:13 AM, Jonathan Brucker
> wrote:
>> Does it make more sense to define an enum (0..7) instead of ASCII symbols?
> So I'm OK with changing it - but let's do it quickly. It's not on the
>
V4L2_RDS_BLOCK_B 1
#define V4L2_RDS_BLOCK_C 2
#define V4L2_RDS_BLOCK_D 3
#define V4L2_RDS_BLOCK_C_ALT 4
#define V4L2_RDS_BLOCK_INVALID 7
Should we do the same? We would also have to add the missing #define
RDS_BLOCK_E 5
On Tue, Sep 13, 2016 at 7:20 PM, Guy Harris wrote:
> On Sep 4, 2016, at 6:43 AM, Jonat
) in the US.
References and Specifications:
https://en.wikipedia.org/wiki/Radio_Data_System
http://www.nrscstandards.org/SG/nrsc-4-B.pdf
http://www.rds.org.uk/2010/RDS-Specification.htm
Thanks,
Jonathan Brucker.
RDS Packet Structure
+---+
| RDS Information Word 1
in:
https://rftap.github.io/
and
https://rftap.github.io/blog/2016/08/27/decoding-rds-with-rftap.html
On Wed, Aug 31, 2016 at 4:38 PM, Guy Harris wrote:
> On Aug 31, 2016, at 9:18 AM, Jonathan Brucker
> wrote:
>
>> I am posting to request a value for DLT_RFTAP and LINKTYPE_RFTAP.
packet, and more.
https://rftap.github.io/specifications/
RFtap protocol support is already integrated into Wireshark.
Thanks,
Jonathan Brucker.
RFtap Packet Structure
+---+
| Magic |
| (4 Octets
