From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 1/2] em28xx: allow setting the eeprom bus at cards struct
Date: Mon, 1 May 2017 14:54:25 -0300 [thread overview]
Message-ID: <20170501145425.10388b37@vento.lan> (raw)
In-Reply-To: <2431f8bf-1bbd-ffa6-1e72-488c31c9c2a7@googlemail.com>
Hi Frank,
Em Mon, 1 May 2017 16:11:51 +0200
Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
> Am 01.05.2017 um 13:38 schrieb Mauro Carvalho Chehab:
> > Right now, all devices use bus 0 for eeprom. However, newer
> > versions of Terratec H6 use a different buffer for eeprom.
> >
> > So, add support to use a different I2C address for eeprom.
>
> Has this been tested ?
> Did you read my reply to the previous patch version ?:
> See http://www.spinics.net/lists/linux-media/msg114860.html
>
> I doubt it will work. At least not for the device from the thread in the
> Kodi-forum.
Yes. Someone at IRC were complaining about this device (his nick is
buxy81). According with the tests he did, with both patches his
device is now working.
That's said, it would be great if he could provide us more details
about the tests he did, with the logs enabled, in order for us to see
if the eeprom contents is properly read.
Thanks,
Mauro
next prev parent reply other threads:[~2017-05-01 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 11:38 [PATCH 1/2] em28xx: allow setting the eeprom bus at cards struct Mauro Carvalho Chehab
2017-05-01 11:38 ` [PATCH 2/2] em28xx: add support for new revisions of Terratec H6 Mauro Carvalho Chehab
2017-05-01 14:11 ` [PATCH 1/2] em28xx: allow setting the eeprom bus at cards struct Frank Schäfer
2017-05-01 14:21 ` Devin Heitmueller
2017-05-01 17:54 ` Mauro Carvalho Chehab [this message]
2017-05-02 17:00 ` Frank Schäfer
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=20170501145425.10388b37@vento.lan \
--to=mchehab@s-opensource.com \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-doc@vger.kernel.org \
--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