From: matthieu castet <castet.matthieu@free.fr>
To: linux-media@vger.kernel.org
Cc: DVB list <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] [PATCH] Support faulty USB IDs on DIBUSB_MC
Date: Mon, 09 Feb 2009 21:16:31 +0100 [thread overview]
Message-ID: <49908F1F.90501@free.fr> (raw)
In-Reply-To: <412bdbff0902091144x56a00289u55c8f65015f28365@mail.gmail.com>
Devin Heitmueller wrote:
> On Mon, Feb 9, 2009 at 2:40 PM, matthieu castet <castet.matthieu@free.fr> wrote:
>> Hi,
>>
>> matthieu castet wrote:
>>> matthieu castet wrote:
>>>> Hi Patrick,
>>>>
>>>> Patrick Boettcher wrote:
>>>>> Hi,
>>>>>
>
> The assumption that you can only have write/read or write requests is
> one of the big things fixed in the 1.20 firmware. If you are running
> the 1.20 firmware, you just need to add the option to use the new i2c
> function instead of the legacy i2c transfer function.
Unfortunamty this is for dib0700 and not dib3000.
dib3000 doesn't got new firmware/i2c API.
But the same patch should be done for dib0700_i2c_xfer_legacy...
Matthieu
next prev parent reply other threads:[~2009-02-09 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 11:36 [linux-dvb] [PATCH] Support faulty USB IDs on DIBUSB_MC matthieu castet
2009-01-19 20:38 ` matthieu castet
2009-01-29 9:47 ` Mauro Carvalho Chehab
2009-01-29 10:19 ` Patrick Boettcher
2009-01-29 12:05 ` Mauro Carvalho Chehab
2009-01-29 13:08 ` Patrick Boettcher
2009-01-29 13:34 ` Mauro Carvalho Chehab
2009-01-29 20:05 ` matthieu castet
2009-01-29 20:46 ` matthieu castet
2009-02-09 19:40 ` matthieu castet
2009-02-09 19:44 ` [linux-dvb] " Devin Heitmueller
2009-02-09 20:16 ` matthieu castet [this message]
2009-02-09 20:32 ` Devin Heitmueller
2009-02-09 19:51 ` Devin Heitmueller
2009-05-16 13:08 ` [PATCH] DIBUSB_MC : fix i2c to not corrupt eeprom in case of strange read pattern matthieu castet
2009-05-20 8:42 ` Patrick Boettcher
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=49908F1F.90501@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-dvb@linuxtv.org \
--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