public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: "Dmitri Belimov" <d.belimov@gmail.com>,
	"Hans J. Koch" <koch@hjk-az.de>,
	"Hans-Jürgen Koch" <hjk@linutronix.de>,
	video4linux-list@redhat.com, linux-media@vger.kernel.org
Subject: Re: saa7134 and RDS
Date: Wed, 4 Mar 2009 10:32:54 +0100	[thread overview]
Message-ID: <20090304093253.GA3244@bluebox.local> (raw)
In-Reply-To: <1236127388.3324.20.camel@pc09.localdom.local>

On Wed, Mar 04, 2009 at 01:43:08AM +0100, hermann pitton wrote:
> Hi,
> 
> Am Montag, den 02.03.2009, 13:33 +0900 schrieb Dmitri Belimov:
> > Hi All.
> > 
> > I want use RDS on our TV cards. But now saa7134 not work with saa6588.
> > I found this old patch from Hans J. Koch. Why this patch is not in mercurial??
> > Yes I know that patch for v4l ver.1 and for old kernel. But why not?? 
> > v4l has other way for RDS on saa7134 boards?
> 
> I think the patch got lost, because it was not clear who should pull it
> in. Likely Hartmut or Mauro would have picked it up in 2006 if pinged
> directly.

The main reason was that at that time there was a conflict with the i2c
ir keyboard driver. I couldn't fix it immediately and was occupied with
different things afterwards. I don't know if saa7134 i2c got fixed
in the meantime.

> 
> Please try to work with Hans to get it in now. There was also a
> suggestion to add a has_rds capability flag and about how to deal with
> different RDS decoders later, IIRC.

Right. We should have a flag you could set to something like
  .has_rds = RDS_SAA6588
so that the rds driver could be loaded automagically.

But I'm afraid I cannot spend much time on this work ATM, sorry.

Thanks,
Hans


  reply	other threads:[~2009-03-04  9:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  4:33 saa7134 and RDS Dmitri Belimov
2009-03-04  0:43 ` hermann pitton
2009-03-04  9:32   ` Hans J. Koch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-04 10:03 Hans Verkuil
2009-03-04 12:02 ` Dmitri Belimov
2009-03-04 17:45   ` Hans Verkuil
2009-03-05 12:01     ` Dmitri Belimov
2009-03-07  1:50       ` Hans J. Koch
2009-03-05 12:07 Hans Verkuil
2009-03-05 16:36 ` Hans Verkuil
2009-03-07  1:55   ` Hans J. Koch
2009-03-07  8:54     ` Hans Verkuil
2009-03-07  9:02       ` Dmitri Belimov
2009-03-07  9:19         ` Hans Verkuil
2009-03-10  2:49           ` Dmitri Belimov
2009-03-10  7:17             ` Hans Verkuil
2009-03-10  8:04               ` Dmitri Belimov

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=20090304093253.GA3244@bluebox.local \
    --to=hjk@linutronix.de \
    --cc=d.belimov@gmail.com \
    --cc=hermann-pitton@arcor.de \
    --cc=koch@hjk-az.de \
    --cc=linux-media@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    /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