Linux Media Controller development
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Andy Walls <awalls@radix.net>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: bttv, tvaudio and ir-kbd-i2c probing conflict
Date: Sun, 15 Mar 2009 23:28:42 +0100	[thread overview]
Message-ID: <20090315232842.62ea5417@hyperion.delvare> (raw)
In-Reply-To: <200903152309.05803.hverkuil@xs4all.nl>

On Sun, 15 Mar 2009 23:09:05 +0100, Hans Verkuil wrote:
> Actually, it seems like this used to work at one time in the past. Jean, can 
> you confirm that it used to be possible to have two i2c clients at the same 
> i2c address in the past? Looking at the post (see the link in my original 
> mail) it apparently worked in 2.6.19 at least.

No, it has never been possible. I can't explain why it used to work (if
it really did...) Maybe the reporter was using an alternative
implementation doing raw bus transfers? You originally suggested that
lirc was doing this.

> I do think that the initial approach to this is to ensure that tvaudio is at 
> least working. After all, it is better to have audio and no remote than to 
> have a working remote, but no audio. Until we find a proper solution I 
> think that this should not stop us from going forward since this way we 
> remain bug-compatible with the current situation. Or even slightly better 
> since we can now ensure that audio is working at least.

Agreed.

-- 
Jean Delvare

  reply	other threads:[~2009-03-15 22:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 12:44 bttv, tvaudio and ir-kbd-i2c probing conflict Hans Verkuil
2009-03-15 17:12 ` Jean Delvare
2009-03-15 17:42   ` Trent Piepho
2009-03-15 17:53     ` Jean Delvare
2009-03-16  9:08       ` Mauro Carvalho Chehab
2009-03-16  9:34       ` Mauro Carvalho Chehab
2009-03-16 11:18         ` Jean Delvare
2009-03-16 12:52           ` Mauro Carvalho Chehab
2009-03-16 14:28             ` Jean Delvare
2009-03-16 15:31               ` Mauro Carvalho Chehab
2009-03-16 19:43               ` Trent Piepho
2009-03-16 21:40                 ` Jean Delvare
2009-03-16 21:58                   ` Hans Verkuil
2009-03-16 22:47                   ` Trent Piepho
2009-03-17  9:31                     ` Jean Delvare
2009-03-17 20:23                       ` Trent Piepho
2009-03-15 19:34   ` Andy Walls
2009-03-15 22:09     ` Hans Verkuil
2009-03-15 22:28       ` Jean Delvare [this message]
2009-03-15 22:26     ` Jean Delvare
2009-03-16  0:52       ` Andy Walls
2009-03-16  4:26         ` hermann pitton
2009-03-16 12:58         ` Jean Delvare
2009-03-15 23:46     ` Trent Piepho
2009-03-16  8:35       ` Jean Delvare
2009-03-16 11:35 ` Andy Walls
  -- strict thread matches above, loose matches on Subject: below --
2009-03-16 11:56 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=20090315232842.62ea5417@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=awalls@radix.net \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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