Moikka
That changes DVBv3 SNR reporting from 0.1dB units to relative between
0-0x. For AF9033 it has been 0.1dB ages and I would like to keep it
as it is. So add logic here to return 0.1dB as it did for AF9033 and do
what you like for IT9133.
On switch-case default branch af9033_stat_work
Hello
I did some review and testing. Before that patch, IT9133 DVBv3 signal
strength measurement was broken - it returned 0x all the time. After
that is returns some realistic values between 0-0x.
Anyhow, AF9033 chip version it worked earlier too, just like old comment
says hw returns
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sat Oct 4 04:00:15 CEST 2014
git branch: test
git hash: cf3167cf1e969b17671a4d3d956d22718a8ceb85
gcc versi
Building with the attached random configuration file,
drivers/built-in.o: In function `gspca_disconnect':
/home/jim/linux/drivers/media/usb/gspca/gspca.c:2190: undefined
reference to `input_unregister_device'
drivers/built-in.o: In function `gspca_input_connect':
/home/jim/linux/drivers/media/usb/
From: Sakari Ailus
The Media controller doesn't tell much to the user in cases such as pipeline
startup failure. The link validation is the most common media graph (or in
V4L2's case, format) related reason for the failure. In more complex
pipelines the reason may not always be obvious to the use
Yeah, this is pure crap. It doesn't even compile.
drivers/media/dvb-frontends/si2165.c:1063:17: error: expected ‘,’ or
‘;’ before ‘SI2165_FIRMWARE’
MODULE_FIRMWARE(SI2165_FIRMWARE);
because it should presumably say "SI2165_FIRMWARE_REV_D" now.
Why the f*ck do you send me totally untested cr
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/topic/si2165-v3.17-rc8
For some changes at the si2165 firmware name and the removal of an extra
unneeded header added artificially via the script that extracts it from
the original driver p
Hi,
Do you have time to take a look at this (with the PC values) ?
On 09/30/2014 09:54 AM, Gaëtan Carlier wrote:
Hi,
The problem can also come from register address or bit offset because
depending source used (GStreamer for 2.6.22 or new coda kernel driver
3.6 or datasheet), registers do not hav
The embedded UART is apparently used to receive decoded IR (RC5?) codes.
Forward these scan codes to the RC framework and (where known) add
corresponding mapping tables to translate them into regular keys.
This patch has been tested on a TechniSat CableStar HD2. Other rc-maps
were taken from Chris
Em Fri, 03 Oct 2014 14:45:19 +0900
"AreMa Inc." escreveu:
> Mauro & Antti
>
> Please drop & replace Tsukada's PT3 patches.
It doesn't work like that. We don't simply drop a driver and replace by
some other one.
The way most open source project works with regards to patch reviewing
process work
2014-10-03 12:16 GMT+02:00 Carlos Sanmartín Bustos :
> Hi all,
>
> I'm interested in this driver with MC support too. I join the conversation
> and if I have time can try to develop some functionality.
>
> Only one question:
>
> 2014-10-02 16:50 GMT+02:00 Jean-Michel Hautbois
> :
>>
>> Hi Steve,
>>
Sorry for the resend, I forget send in plain text.
Hi all,
I'm interested in this driver with MC support too. I join the
conversation and if I have time can try to develop some functionality.
Only one question:
2014-10-02 16:50 GMT+02:00 Jean-Michel Hautbois
:
>
> Hi Steve,
>
> 2014-09-09 18:28
12 matches
Mail list logo
