I have the problem with a avermedia twinstart.
07ca:0825
With first hardware revision the read works, but second hardware revision read
don’t work.
Jose Alberto
El 09/04/2016 19:38, Alessandro Radicati escribió:
>
> On Sat, Apr 9, 2016 at 7:07 PM, Antti Palosaari wrote:
> >
> >
> > On 04/09
On Sat, Apr 9, 2016 at 7:07 PM, Antti Palosaari wrote:
>
>
> On 04/09/2016 07:11 PM, Alessandro Radicati wrote:
>>
>> On Sat, Apr 9, 2016 at 4:25 PM, Antti Palosaari wrote:
>>>
>>> On 04/09/2016 11:13 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 4:17 AM, Antti Palosaari w
On 04/09/2016 07:11 PM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 4:25 PM, Antti Palosaari wrote:
On 04/09/2016 11:13 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 4:17 AM, Antti Palosaari wrote:
On 04/09/2016 04:52 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at
On Sat, Apr 9, 2016 at 4:25 PM, Antti Palosaari wrote:
> On 04/09/2016 11:13 AM, Alessandro Radicati wrote:
>>
>> On Sat, Apr 9, 2016 at 4:17 AM, Antti Palosaari wrote:
>>>
>>> On 04/09/2016 04:52 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 3:22 AM, Antti Palosaari wrote
On 04/09/2016 11:13 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 4:17 AM, Antti Palosaari wrote:
On 04/09/2016 04:52 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 3:22 AM, Antti Palosaari wrote:
Here is patches to test:
http://git.linuxtv.org/anttip/media_tree.git/log/?h=a
On Sat, Apr 9, 2016 at 4:17 AM, Antti Palosaari wrote:
> On 04/09/2016 04:52 AM, Alessandro Radicati wrote:
>>
>> On Sat, Apr 9, 2016 at 3:22 AM, Antti Palosaari wrote:
>>>
>>> Here is patches to test:
>>> http://git.linuxtv.org/anttip/media_tree.git/log/?h=af9035
>>>
>>
>> I've done this already
On 04/09/2016 04:52 AM, Alessandro Radicati wrote:
On Sat, Apr 9, 2016 at 3:22 AM, Antti Palosaari wrote:
Here is patches to test:
http://git.linuxtv.org/anttip/media_tree.git/log/?h=af9035
I've done this already in my testing, and it works for getting a
correct chip_id response, but only be
On Sat, Apr 9, 2016 at 3:22 AM, Antti Palosaari wrote:
> Here is patches to test:
> http://git.linuxtv.org/anttip/media_tree.git/log/?h=af9035
>
I've done this already in my testing, and it works for getting a
correct chip_id response, but only because it's avoiding the issue
with the write/read
Antti,
AF9035 I2C write/read is fine with the patch I proposed, like your
middle case. This issue is not specific to MXL5007T; it's something I
caught sniffing the I2C bus with a logic analyzer and stands on it's
own. I implemented it this way because the driver specifically
implements that write
Here is patches to test:
http://git.linuxtv.org/anttip/media_tree.git/log/?h=af9035
After that both af9015+mxl5007t and af9035+mxl5007t started working.
Earlier both were returning bogus values for chip id read.
Also I am interested to known which kind of communication there is
actually seen
uh, how it could be so hard?
I just made few tests and found 3 ways to read it. OK, one is that
Alessandro already pointed out and I don't feel it correct. But those 2
are one for look. CMD_I2C_WR / CMD_I2C_RD with 1st priority, then
CMD_GENERIC_I2C_WR / CMD_GENERIC_I2C_RD
{
u8 buf[MAX_X
Jose, Antti,
The no_probe option or similar is the only fix I could find (in fact i
was going to propose a similar patch to what you have). I've tried
all combinations of firmware and also tried issuing the read command
to the tuner in different states (e.g. sleep, just after soft/hard
reset) to n
I made a patch long time ago, but it was not accepted.
https://patchwork.linuxtv.org/patch/16242/
Jose Alberto
El 06/04/2016 01:00, Alessandro Radicati escribió:
>
> On Wed, Apr 6, 2016 at 12:33 AM, Antti Palosaari wrote:
> > I found one stick having AF9035 + MXL5007T. It is HP branded A867,
On Wed, Apr 6, 2016 at 12:33 AM, Antti Palosaari wrote:
> I found one stick having AF9035 + MXL5007T. It is HP branded A867, so it
> should be similar. It seems to work all three 12.13.15.0 6.20.15.0
> firmwares:
> http://palosaari.fi/linux/v4l-dvb/firmware/af9035/
>
> mxl5007t 5-0060: creating ne
I found one stick having AF9035 + MXL5007T. It is HP branded A867, so it
should be similar. It seems to work all three 12.13.15.0 6.20.15.0
firmwares:
http://palosaari.fi/linux/v4l-dvb/firmware/af9035/
mxl5007t 5-0060: creating new instance
mxl5007t_get_chip_id: unknown rev (3f)
mxl5007t_get_ch
On Tue, Apr 5, 2016 at 8:15 PM, Antti Palosaari wrote:
> On 04/02/2016 01:44 PM, Alessandro Radicati wrote:
>>
>> Hi,
>> In trying to understand why my DVB USB tuner doesn't work with stock
>> kernel drivers (4.2.0), I decided to pull out my logic analyser and
>> sniff the I2C bus between the AF90
On 04/02/2016 01:44 PM, Alessandro Radicati wrote:
Hi,
In trying to understand why my DVB USB tuner doesn't work with stock
kernel drivers (4.2.0), I decided to pull out my logic analyser and
sniff the I2C bus between the AF9035 and MXL5007T. I seem to have
uncovered a couple of issues:
1) Atta
Hi,
In trying to understand why my DVB USB tuner doesn't work with stock
kernel drivers (4.2.0), I decided to pull out my logic analyser and
sniff the I2C bus between the AF9035 and MXL5007T. I seem to have
uncovered a couple of issues:
1) Attach fails because MXL5007T driver I2C soft reset fails
18 matches
Mail list logo
