> Okay. How the raw data socket looks like is currently your choice. (: Maybe not quite that complicated, though: $ cat /proc/rds/radio0/raw/3a < last 3A block returned here > I figure it will let the kernel space stuff parse it into something that's logically organized, then let userspace actually figure out what it means. > Hmmm, do we use the official terms like RT, PS, PI, AF and CT? That might be nicer if only for closer adherance to the standard. It won't require a lot of work as to what to call them either. It's already laid out for us, and there won't be any namespace conflicts. > And how to present the TP/TA traffic-stuff, the altfreqs, timedate and > type? > $ cat /proc/rds/radio0/tpta > 10 <-- maybe binary, too? /proc/rds/radio0/tp would be 1/0, /proc/rds/radio0/ta would be 1/0. Why run them together? One item, one entry. > $ cat /proc/rds/radio0/type > 08 Science This should just be 08, which handles your next issue nicely... > And how to switch form RDS to RBDS (08 Soft Rock :)? ... namely, to let the locale stuff handle which table to use. Maybe another country will come along with yet another meaning for 08. It's no place for the kernel to force a translation value on the user. I'll try to figure out some foundation work for this over the weekend so we can play with the code and work out the arrangement of the data.
