From: Matthias Bock <mail@matthiasbock.net>
To: linux-media@vger.kernel.org, v4l2-library@linuxtv.org
Subject: RDS help needed
Date: Tue, 01 May 2012 12:56:49 +0200 [thread overview]
Message-ID: <1335869809.4592.14.camel@localhost> (raw)
Hi there!
I hacked a RDS TMC-message receiver to work on the serial port.
http://www.matthiasbock.net/wiki/?title=Kategorie:GNS_TrafficBox_FM9_RDS_TMC-Receiver
According to
http://linuxtv.org/wiki/index.php/Radio_Data_System_(RDS)
already several different receivers are available for usage
with Linux but development of the RDS message daemon,
that would be required to collect, decode and distribute
the RDS messages to client applications
http://rdsd.berlios.de/
kindof stucked, didn't progress since 2009 (!)
The available SVN sources only support
SAA6588-based RDS receivers.
Is RDS support still an important task to
someone on this list ?
Is there someone, who would consider assisting me a little
in writing some documentation on the RDS daemon project,
some code maybe, lateron some linux kernel modules ?
Cheers! Matthias
next reply other threads:[~2012-05-01 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 10:56 Matthias Bock [this message]
2012-05-01 12:53 ` RDS help needed Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1335869809.4592.14.camel@localhost \
--to=mail@matthiasbock.net \
--cc=linux-media@vger.kernel.org \
--cc=v4l2-library@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox