Hi all
El 01/04/12 16:10, Alfredo Jesús Delaiti escribió:
Hi all
I found that this is the patch that makes no sound:
http://git.kernellabs.com/?p=stoth/cx23885-hvr1850-fixups.git;a=commit;h=e187d0d51bcd0659eeac1d608284644ec8404239
I will try to find that lines are responsible.
Please re
The default_value for the Bt878 V4L2_CID_CONTRAST control is currently
set to 32768. Internally this gets translated to an analog input
circuit gain of 1.19. However, the default gain should be 1.0. This
patch alters the default value to 27648 which corresponds to a gain of
1.0. It also alters the
On 02.04.2012 00:56, Antti Palosaari wrote:
On 02.04.2012 00:19, Hans-Frieder Vogt wrote:
Implementation of af9033_read_ber and af9033_read_ucblocks functions.
+ sw = ~sw;
I don't see any reason for that?
Now I see, it is some kind of switch to make operation every second call?
As it is defi
On 02.04.2012 00:19, Hans-Frieder Vogt wrote:
Implementation of af9033_read_ber and af9033_read_ucblocks functions.
Signed-off-by: Hans-Frieder Vogt
drivers/media/dvb/dvb-usb/af9033.c | 68
+++--
Same wrong path issue.
+ /* only update data every
On 01.04.2012 23:33, Michael Büsch wrote:
This adds USB message read checksumming to protect against
device and bus errors.
It also adds a read length check to avoid returning garbage from
the buffer, if the device truncated the message.
Signed-off-by: Michael Buesch
Applied thanks!
http://gi
On 02.04.2012 00:07, Hans-Frieder Vogt wrote:
Support of AVerMedia AVerTV HD Volar, with tuner MxL5007t, second version of
patch
(usage of clock_adc_lut instead of adc config variable)
Signed-off-by: Hans-Frieder Vogt
Patch does not apply.
wget -O - http://patchwork.linuxtv.org/patch/10536/mb
Implementation of af9033_read_ber and af9033_read_ucblocks functions.
Signed-off-by: Hans-Frieder Vogt
drivers/media/dvb/dvb-usb/af9033.c | 68 +++--
1 file changed, 66 insertions(+), 2 deletions(-)
diff -Nupr a/drivers/media/dvb/dvb-usb/af9033.c
b/drivers/me
Support of AVerMedia AVerTV HD Volar, with tuner MxL5007t, second version of
patch
(usage of clock_adc_lut instead of adc config variable)
Signed-off-by: Hans-Frieder Vogt
drivers/media/dvb/dvb-usb/af9033.c | 45 +++
drivers/media/dvb/dvb-usb/af9033.h |1
drive
Currently the ati_remote default keymap is selected directly based on
the USB device id.
Add support for instead specifying a function returning the default
keymap, allowing more complex selection logic to be added when needed.
This will be used for Medion X10 remotes in a following commit.
Sign
Add support for another Medion X10 remote. This was apparently
originally used with the Medion Digitainer box, but is now sold
separately without any Digitainer labeling.
A peculiarity of this remote is a scrollwheel in place of up/down
buttons. Each direction is mapped to 8 different scancodes, e
On 04/01/2012 03:24 PM, Hans Verkuil wrote:
No, this is the correct patch:
diff --git a/sound/pci/Kconfig b/sound/pci/Kconfig
index 8816804..5ca0939 100644
--- a/sound/pci/Kconfig
+++ b/sound/pci/Kconfig
@@ -2,8 +2,8 @@
config SND_TEA575X
tristate
- depends on SND_FM801_TEA575X_
Hi!
This patchset adds support for another Medion X10 remote to the
ati_remote driver. See the individual patches for detailed explanations.
Anssi Hannula (2):
[media] ati_remote: allow specifying a default keymap selector function
[media] ati_remote: add support for Medion X10 Digit
This adds USB message read checksumming to protect against
device and bus errors.
It also adds a read length check to avoid returning garbage from
the buffer, if the device truncated the message.
Signed-off-by: Michael Buesch
---
Index: linux/drivers/media/dvb/dvb-usb/af9035.c
=
On 04/01/2012 12:24 PM, Hans Verkuil wrote:
> On Sunday, April 01, 2012 21:09:34 Tracey Dent wrote:
>> radio-maxiradio depends on SND_FM801_TEA575X_BOOL to build or will
>> result in an build error such as:
>>
>> Kernel: arch/x86/boot/bzImage is ready (#1)
>> ERROR: "snd_tea575x_init" [drivers/me
On Sunday, April 01, 2012 21:09:34 Tracey Dent wrote:
> radio-maxiradio depends on SND_FM801_TEA575X_BOOL to build or will
> result in an build error such as:
>
> Kernel: arch/x86/boot/bzImage is ready (#1)
> ERROR: "snd_tea575x_init" [drivers/media/radio/radio-maxiradio.ko] undefined!
> ERROR: "
I'm so sorry for all the noise. I recently set up git on a new laptop
and I sis not configure it correctly. Can everybody disregard this
thread and I sent a new patch in a new thread thread which should fix
suggested issue[1].
Once again sorry.
[1]: https://lkml.org/lkml/2012/4/1/175
--
To unsub
Hi all
I found that this is the patch that makes no sound:
http://git.kernellabs.com/?p=stoth/cx23885-hvr1850-fixups.git;a=commit;h=e187d0d51bcd0659eeac1d608284644ec8404239
I will try to find that lines are responsible.
Thanks,
Alfredo
El 31/03/12 22:34, Alfredo Jesús Delaiti escribió:
Hi
radio-maxiradio depends on SND_FM801_TEA575X_BOOL to build or will
result in an build error such as:
Kernel: arch/x86/boot/bzImage is ready (#1)
ERROR: "snd_tea575x_init" [drivers/media/radio/radio-maxiradio.ko] undefined!
ERROR: "snd_tea575x_exit" [drivers/media/radio/radio-maxiradio.ko] undefin
radio-maxiradio depends on SND_FM801_TEA575X_BOOL to build or will
result in an build error such as:
Kernel: arch/x86/boot/bzImage is ready (#1)
ERROR: "snd_tea575x_init" [drivers/media/radio/radio-maxiradio.ko] undefined!
ERROR: "snd_tea575x_exit" [drivers/media/radio/radio-maxiradio.ko] undefin
On 01.04.2012 21:11, Hans-Frieder Vogt wrote:
attached is the i2c read fix (necessary e.g. for mxl5007t tuner, because it
sends a 2 bytes for a read request, thus msg[0].len != msg[1].len).
Enable i2c read requests.
Signed-off-by: Hans-Frieder Vogt
Applied, thank you!
http://git.linuxtv.org/
Antti,
attached is the i2c read fix (necessary e.g. for mxl5007t tuner, because it
sends a 2 bytes for a read request, thus msg[0].len != msg[1].len).
Am Sonntag, 1. April 2012 schrieb Antti Palosaari:
> On 01.04.2012 20:15, Hans-Frieder Vogt wrote:
> > Support of AVerMedia AVerTV HD Volar, wit
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:Sun Apr 1 19:00:20 CEST 2012
git hash:296da3cd14db9eb5606924962b2956c9c656dbb0
gcc version: i686-linux-gcc (GC
On Sun, Apr 1, 2012 at 10:23 AM, wrote:
> From: Tracey
Please fix your git config to have proper name and email (or whatever
tool you used). Your 'cc' list is similarly broken.
> Either selecting or depending on the CONFIG_SND_FM801_TEA575X_BOOL
> fixes the problem, but select seems to be more
On 01.04.2012 20:15, Hans-Frieder Vogt wrote:
Support of AVerMedia AVerTV HD Volar, with tuner MxL5007t (needs the i2c read
bug fixed patch send earlier).
Could you sent separate patch for I2C read fix?
The only functional comment I has is about ADC frequency. There is
Xtal/ADC lookup table
Support of AVerMedia AVerTV HD Volar, with tuner MxL5007t (needs the i2c read
bug fixed patch send earlier).
Signed-off-by: Hans-Frieder Vogt
drivers/media/dvb/dvb-usb/af9033.c | 36 +++---
drivers/media/dvb/dvb-usb/af9033.h |6 ++
drivers/media/dvb/dvb-usb/af9033_priv.
On Sun, 01 Apr 2012 19:39:56 +0300
Antti Palosaari wrote:
> > Well I didn't retry at that level, but at the fc0011 driver level.
> > It does already retry once in fc0011 (with complete tuner reset).
> > I increased it to 6 times (3 was not enough).
>
> Maybe some delay is needed in order to wait
On 01.04.2012 19:32, Michael Büsch wrote:
On Sun, 01 Apr 2012 19:20:21 +0300
Antti Palosaari wrote:
On 01.04.2012 19:15, Michael Büsch wrote:
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
[ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out t
On Sun, 1 Apr 2012 18:24:09 +0200
"Hans-Frieder Vogt" wrote:
> However, I found the problem: the buffer
> length needs to be msg[1].len, see below.
I spotted this bug, too, but it didn't fix the problem, as len is 1 for
both packets in my specific case. So it doesn't make a difference in this ca
On Sun, 01 Apr 2012 19:20:21 +0300
Antti Palosaari wrote:
> On 01.04.2012 19:15, Michael Büsch wrote:
> > On Sun, 1 Apr 2012 15:11:53 +0200
> > Michael Büsch wrote:
> >
> >> [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> >
> > Ok, it turns out that it doesn't fail all
Am Sonntag, 1. April 2012 schrieb Michael Büsch:
> On Sun, 1 Apr 2012 16:42:34 +0200
>
> "Hans-Frieder Vogt" wrote:
> > > [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> > >
> > > It doesn't run into this check on the other af903x driver.
> > > So I suspect an i2c read
On 01.04.2012 19:15, Michael Büsch wrote:
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
[ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out that it doesn't fail all the time, but only sporadically.
So increasing the number of retries fixes (or at
On Sun, 1 Apr 2012 15:11:53 +0200
Michael Büsch wrote:
> [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
Ok, it turns out that it doesn't fail all the time, but only sporadically.
So increasing the number of retries fixes (or at least works around) it.
No idea why this b
From: "Steinar H. Gunderson"
As others have noticed, sometimes, especially during DMA transfers, the IRQ0
flag is never properly set and thus reads never return. (The typical case for
this is when we've just done a write and the en50221 thread is waiting for the
CAM status word to signal STATUSR
From: "Steinar H. Gunderson"
wait_event_timeout() returns 0 on timeout, not -ERESTARTSYS.
Note that since this actually causes timeouts to be handled,
it makes the CA situation a lot worse without the next patch
in the series.
---
drivers/media/dvb/mantis/mantis_hif.c |4 ++--
1 file changed
From: "Steinar H. Gunderson"
Not my patch originally; picked up from verbal descriptions on
the linux-media list, and fixed up slightly.
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_ca.c |4 +++-
drivers/media/dvb/mantis/mantis_core.c | 20 ---
From: "Steinar H. Gunderson"
Basically a lot of the members of mantis_ca were accessed from several threads
without a mutex, which is a big no-no; I've mostly changed to using atomic
operations here, although I also added some locks were it made sense
(e.g. when resetting the CAM).
---
drivers/m
From: "Steinar H. Gunderson"
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_evm.c | 12
drivers/media/dvb/mantis/mantis_link.h |8
2 files changed, 4 insertions(+), 16 deletions(-)
diff --git a/drivers/media/dvb/mantis/mantis_evm.c
b/drive
From: "Steinar H. Gunderson"
By Marko Ristola; see http://patchwork.linuxtv.org/patch/8776/ .
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_cards.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/drivers/media/dvb/mantis/m
From: "Steinar H. Gunderson"
This lock is ideally held when banging on MANTIS_INT_STAT.
(I have no hardware documentation, so I'm afraid I don't
really know the specifics here.)
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_ca.c |2 --
drivers/media/dvb/mantis
From: "Steinar H. Gunderson"
On I2C reads and writes, show if we had any timeouts in the debug output.
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_i2c.c | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/drivers/media/d
From: "Steinar H. Gunderson"
Say what address we read/write from/to. This is useful when trying
to trace where the debug output comes from, and which accesses
fail, if any.
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_hif.c |9 +
1 file changed, 5 inserti
From: "Steinar H. Gunderson"
Clear out MANTIS_INT_RISCSTAT for debugging, so that status words
from the RISC do not show up as "Unknown" bits in the debug display.
Signed-off-by: Steinar H. Gunderson
---
drivers/media/dvb/mantis/mantis_cards.c |3 ++-
1 file changed, 2 insertions(+), 1 del
From: "Steinar H. Gunderson"
dvb_usercopy(), which is called on all ioctls, not only copies data to and from
userspace, but also takes a lock on the file descriptor, which means that only
one ioctl can run at a time. This means that if one thread of mumudvb is busy
trying to get, say, the SNR fro
Hi,
I was asked to break up my large patch into several smaller,
Signed-off-by-marked changes. I've rebased against linux-2.6 master and done
some today; note that since not all of these changes are originally by me,
you will probably have to consider each one separately for inclusion
(although th
On Sun, Apr 01, 2012 at 02:30:54PM +0100, Malcolm Priestley wrote:
> Originally, IT9135 chip version 2 devices were never intended to be supported
> in kernel 3.2
> as they were thought at the time only on ID 048d:9006.
>
> However, they have since been supplied on ID 048d:9135, the following err
Am Sonntag, 1. April 2012 schrieb Antti Palosaari:
> On 01.04.2012 17:31, Hans-Frieder Vogt wrote:
> > Antti,
> >
> > I could provide the SNR, BER and UCB implementation (simply porting from
> > my draft driver to yours).
> > But I first need to implement the support for my AverMedia A867R device
On 01.04.2012 17:31, Hans-Frieder Vogt wrote:
Antti,
I could provide the SNR, BER and UCB implementation (simply porting from my
draft driver to yours).
But I first need to implement the support for my AverMedia A867R device so that
I am able to test the implementation. Therefore it could take a
On Sun, 1 Apr 2012 16:42:34 +0200
"Hans-Frieder Vogt" wrote:
> > [ 3101.940765] i2c i2c-8: Failed to read VCO calibration value (got 20)
> >
> > It doesn't run into this check on the other af903x driver.
> > So I suspect an i2c read issue here.
>
> I would first uncomment the i2c read functional
Michael,
Am Sonntag, 1. April 2012 schrieb Michael Büsch:
> On Sun, 01 Apr 2012 15:29:07 +0300
>
> Antti Palosaari wrote:
> > buf[1] = msg[0].addr << 1;
> > Maybe you have given I2C address as a "8bit" format?
>
> Uhh, the address is leftshifted by one.
> So I changed the i2c address from 0xC0
Antti,
I could provide the SNR, BER and UCB implementation (simply porting from my
draft driver to yours).
But I first need to implement the support for my AverMedia A867R device so that
I am able to test the implementation. Therefore it could take a few hours
(maybe until tomorrow).
Regards,
On Thu, Mar 22, 2012 at 10:11:40PM +0100, Ninja wrote:
> I started some testing and so far the changes seem to be fine, but I
> still get freezes from time to time. I have to admit that I still
> need to test if I get the same error with other applications than
> mythtv.
It seems to be CAM depende
Originally, IT9135 chip version 2 devices were never intended to be supported
in kernel 3.2
as they were thought at the time only on ID 048d:9006.
However, they have since been supplied on ID 048d:9135, the following error
occurs.
[ 53.512013] usb 2-4: new high-speed USB device number 5 using
On 01.04.2012 16:11, Michael Büsch wrote:
On Sun, 01 Apr 2012 15:29:07 +0300
Antti Palosaari wrote:
buf[1] = msg[0].addr<< 1;
Maybe you have given I2C address as a "8bit" format?
Uhh, the address is leftshifted by one.
So I changed the i2c address from 0xC0 to 0x60.
That's a very common mi
On Sun, 01 Apr 2012 15:29:07 +0300
Antti Palosaari wrote:
> buf[1] = msg[0].addr << 1;
> Maybe you have given I2C address as a "8bit" format?
Uhh, the address is leftshifted by one.
So I changed the i2c address from 0xC0 to 0x60.
The i2c write seems to work now. At least it doesn't complain anym
Ooops forget to comment these...
On 01.04.2012 13:27, Hans-Frieder Vogt wrote:
Your new firmware loader implies that the firmware is available as a type
"download firmware". It seems this is indeed the case for most (all?) of the
AF9035 devices. If the IT9135 driver should be merged, the "copy f
On 01.04.2012 13:27, Hans-Frieder Vogt wrote:
nice work! I'll try to port the features that I have in my implementation of
an af9035 driver into yours.
You are welcome! But please tell me what you are doing to avoid
duplicate work. My today plan was to implement af9033 SNR, BER, UCB, but
if y
On 01.04.2012 15:19, Michael Büsch wrote:
Great work. I'll rebase my tree on the new branch and check those firmware
files asap.
Hm, none of these firmwares fix the problem. Maybe it's not a firmware
problem after all, but just incorrectly setup tuner-i2c.
Here's the dmesg log:
[...]
[ 132.
On Sun, 1 Apr 2012 10:33:15 +0200
Michael Büsch wrote:
> On Sun, 01 Apr 2012 07:51:33 +0300
> Antti Palosaari wrote:
> > > I have no clue about the firmware format, so it will probably be easier
> > > if you'd dive into that stuff as you already seem to know it.
> >
> > Done. I didn't have neit
Antti,
nice work! I'll try to port the features that I have in my implementation of
an af9035 driver into yours.
Am Sonntag, 1. April 2012 schrieb Antti Palosaari:
> On 31.03.2012 19:52, Michael Büsch wrote:
> > On Sat, 31 Mar 2012 19:48:34 +0300
> >
> > Antti Palosaari wrote:
> >> And about t
Il 01/04/2012 06:51, Antti Palosaari ha scritto:
[snip]
> I need more AF903x hardware, please give links to cheap eBay devices
> etc. Also I would like to get one device where is AF9033 but no AF9035
> at all just for stand-alone demodulator implementation. I know there is
> few such devices, lik
Hello there,
Here is the initial tuning data for another Dutch cable provider: nl-UPC
I had placed below content into /usr/share/dvb/dvb-c/nl-UPC.
Regards,
Jens
--
# Initial Tuning file for nl-UPC
# This file only lists the main
# frequencies. You still need to do
# a netwo
On Sun, 01 Apr 2012 07:51:33 +0300
Antti Palosaari wrote:
> > I have no clue about the firmware format, so it will probably be easier
> > if you'd dive into that stuff as you already seem to know it.
>
> Done. I didn't have neither info, but there was good posting from Daniel
> Glöckner that doc
62 matches
Mail list logo
