Re: [PATCH 1/2] usbtv: Use same decoder sequence as Windows driver

2018-03-09 Thread Hans Verkuil
On 27/02/18 23:35, Hugo "Bonstra" Grostabussiat wrote: > Le 26/02/2018 à 15:12, Hans Verkuil a écrit : >> Thanks for this patch, but I am a bit hesitant to apply it. Did you test >> that PAL and NTSC still work after this change? > > I did test with both a PAL and a NTSC source before submitting

Re: [PATCH 1/2] usbtv: Use same decoder sequence as Windows driver

2018-02-27 Thread Hugo "Bonstra" Grostabussiat
Le 26/02/2018 à 15:12, Hans Verkuil a écrit : > Thanks for this patch, but I am a bit hesitant to apply it. Did you test > that PAL and NTSC still work after this change? I did test with both a PAL and a NTSC source before submitting the patch. It seemed to work fine. However, after reading your

Re: [PATCH 1/2] usbtv: Use same decoder sequence as Windows driver

2018-02-26 Thread Hans Verkuil
Hi Hugo, Thanks for this patch, but I am a bit hesitant to apply it. Did you test that PAL and NTSC still work after this change? Unless you've tested it then I'm inclined to just apply the second patch that adds the SECAM sequence. Regards, Hans On 02/24/2018 07:24 PM, Hugo

[PATCH 1/2] usbtv: Use same decoder sequence as Windows driver

2018-02-24 Thread Hugo Grostabussiat
Re-format the register {address, value} pairs so they follow the same order as the decoder configuration sequences in the Windows driver's .INF file. For instance, for PAL, the "AVPAL" sequence in the .INF file is: 0x04,0x68,0xD3,0x72,0xA2,0xB0,0x15,0x01,0x2C,0x10,0x20,0x2e,0x08,0x02,