From: Patrice Chotard <patrice.chotard@sfr.fr>
To: Frédéric <fma@gbiloba.org>
Cc: linux-media@vger.kernel.org, rjkm@metzlerbros.de,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: Support for Terratec Cinergy 2400i DT in kernel 3.x
Date: Wed, 14 Nov 2012 21:46:04 +0100 [thread overview]
Message-ID: <50A4030C.70306@sfr.fr> (raw)
In-Reply-To: <201211140948.00913.fma@gbiloba.org>
Hi Frédéric,
You are right, in the ngene initial commit
(dae52d009fc950b5c209260d50fcc000f5becd3c), no fw_version was set, so by
default the ngene_15.fw is selected.
But in the patch available here
http://wiki.ubuntuusers.de/_attachment?target=/Terratec_Cinergy_2400i_DT/ngene_p11.tar.gz,
fw_version = 17 was set in ngene_info_terratec struct.
Before submitting the ngene patch set i have done tests with all
available firmware without noticing any difference.
I really don't known what are the difference between ngene_15.fw and
ngene_17.fw
Perhaps Ralph or Mauro has the answer ?
On 14/11/2012 09:48, Frédéric wrote:
> Le mardi 13 novembre 2012, Patrice Chotard a écrit :
>
>> Two patches have been already submitted and are available since v3.7-rc1
>>
>> media] ngene: add support for Terratec Cynergy 2400i Dual DVB-T :
>> 397e972350c42cbaf3228fe2eec23fecf6a69903
>>
>> and
>>
>> media] dvb: add support for Thomson DTT7520X :
>> 5fb67074c6657edc34867cba78255b6f5b505f12
>
> I had a look at your patches. I don't see the '.fw_version' param anymore in the 'ngene_info'
> structure... Is it normal?
>
prev parent reply other threads:[~2012-11-14 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 9:40 Support for Terratec Cinergy 2400i DT in kernel 3.x Frédéric
2012-11-13 21:51 ` Patrice Chotard
2012-11-14 8:48 ` Frédéric
2012-11-14 9:36 ` Frédéric
2012-11-14 20:50 ` Patrice Chotard
2012-11-14 20:46 ` Patrice Chotard [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=50A4030C.70306@sfr.fr \
--to=patrice.chotard@sfr.fr \
--cc=fma@gbiloba.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rjkm@metzlerbros.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.