Reported-by: mjs mjst...@gmail.com
Tested-by: mjs mjst...@gmail.com
Cc: Geert Stappers stapp...@stappers.nl
Cc: sta...@vger.linux.org
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/media/usb/gspca/sunplus.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Mauro,
This pull-req supersedes my previous GIT PULL FIXES for 3.13, new
in this pull-req is an additional usb-id for the gspca_sunplus
driver.
Please pull from my tree for 4 small fixes for 3.13 :
The following changes since commit 80f93c7b0f4599ffbdac8d964ecd1162b8b618b9:
[media]
Reported-by: mjs mjst...@gmail.com
Tested-by: mjs mjst...@gmail.com
Cc: Geert Stappers stapp...@stappers.nl
Cc: sta...@vger.kernel.org
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/media/usb/gspca/sunplus.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Mauro,
This is a resend of my pull-req from a few minutes ago. I had
made an error in the Cc: stable (I used linux.org instead of kernel.org),
this pull-req is for the fixed commit (up to commit id changed).
This pull-req supersedes my previous GIT PULL FIXES for 3.13, new
in this pull-req
Are you in any financial difficulty? apply for loan at 2% low rate
email;ahmedbensonfina...@hotmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Jean,
Sorry, that I came upon this patch quite late.
On Mon, Jun 3, 2013 at 8:51 PM, Jean Delvare kh...@linux-fr.org wrote:
SNR is supposed to be reported by the frontend drivers in dB, so print
it that way for drivers which implement it properly.
Not all frontends do report report the
This is a frustration of mine. Some report it in SNR others report it
in terms of % (current snr / (max_snr-min_snr)) others its completely
random.
Seems many dvb-s report arbitrary % which is stupid and many atsc
report snr by 123 would be 12.3db. But there isnt any standardization
around.
imo
On Sun, Nov 24, 2013 at 11:32 PM, Chris Lee update...@gmail.com wrote:
This is a frustration of mine. Some report it in SNR others report it
in terms of % (current snr / (max_snr-min_snr)) others its completely
random.
Seems many dvb-s report arbitrary % which is stupid and many atsc
report
On Sun, Nov 24, 2013 at 1:02 PM, Chris Lee update...@gmail.com wrote:
This is a frustration of mine. Some report it in SNR others report it
in terms of % (current snr / (max_snr-min_snr)) others its completely
random.
Seems many dvb-s report arbitrary % which is stupid and many atsc
report
On Mon, Nov 18, 2013 at 00:06 +0100, Gerhard Sittig wrote:
the series is based on v3.12, but I'll rebase against v3.13-rc1
(when available) or any other subtree upon request
Now that v3.13-rc1 is out, I noticed that the series no longer
applies cleanly (minor context changes and conflicts)
I made an exception in my app if the system is ATSC/QAM it uses the
snr = snr * 10.0 and havent found a card yet that it doesnt work with.
Ive also converted quite a few of my dvb-s tuners to report db in the
same way. Havent found a card yet that doesnt have the ability to
report snr in db. Im
On Sun, Nov 24, 2013 at 1:40 PM, Chris Lee update...@gmail.com wrote:
I made an exception in my app if the system is ATSC/QAM it uses the
snr = snr * 10.0 and havent found a card yet that it doesnt work with.
Ive also converted quite a few of my dvb-s tuners to report db in the
same way.
Since I'm currently unable to dedicate sufficient time to the maintainership
of these two drivers update their status to orphan until new maintainers
appear.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
Sorry, didn't send to the media list originally.
MAINTAINERS |6
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: Mon Nov 25 04:00:27 CET 2013
git branch: test
git hash: 80f93c7b0f4599ffbdac8d964ecd1162b8b618b9
gcc
14 matches
Mail list logo
