From: Michael Krufky <mkrufky@linuxtv.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: tuner-core i2c address range check: time to remove them?
Date: Tue, 14 Apr 2009 01:47:56 -0400 [thread overview]
Message-ID: <49E4238C.6000500@linuxtv.org> (raw)
In-Reply-To: <200904131310.18758.hverkuil@xs4all.nl>
Hans Verkuil wrote:
> On Sunday 29 March 2009 22:53:01 Hans Verkuil wrote:
>> Hi all,
>>
>> The tuner-core.c source contains this warning since 2.6.24:
>>
>> tuner_warn("Support for tuners in i2c address range 0x64 thru 0x6f\n");
>> tuner_warn("will soon be dropped. This message indicates that your\n");
>> tuner_warn("hardware has a %s tuner at i2c address 0x%02x.\n",
>> t->name, t->i2c->addr);
>> tuner_warn("To ensure continued support for your device, please\n");
>> tuner_warn("send a copy of this message, along with full dmesg\n");
>> tuner_warn("output to v4l-dvb-maintainer@linuxtv.org\n");
>> tuner_warn("Please use subject line: \"obsolete tuner i2c address.\"\n");
>> tuner_warn("driver: %s, addr: 0x%02x, type: %d (%s)\n",
>> t->i2c->adapter->name, t->i2c->addr, t->type,
>> t->name);
>>
>> Isn't it time to remove these i2c addresses? I don't believe we ever had
>> a real tuner at such an address.
>>
>> With the ongoing v4l2_subdev conversion I need to do a bit of cleanup in
>> tuner-core.c as well, so it would be a good time for me to combine it
>> (and it gets rid of an ugly cx88 hack in tuner-core.c as well).
>>
>> Regards,
>>
>> Hans
>
> Mike, please let me know if I can remove this!
Hans,
The warning message can be removed now, but please note that i2c address
0x64 *is* a valid i2c address for a tuner.
I believe that 0x65 thru 0x6f can be removed.
Regards,
Mike
prev parent reply other threads:[~2009-04-14 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 20:53 tuner-core i2c address range check: time to remove them? Hans Verkuil
2009-04-13 11:10 ` Hans Verkuil
2009-04-14 5:47 ` Michael Krufky [this message]
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=49E4238C.6000500@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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