On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
On 07/01/13 15:26, Oliver Schinagl wrote:
On 01-07-13 15:23, Antti Palosaari wrote:
On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
On 01-07-13 08:53, Bogdan Oprea wrote:
this is a fix for this type of error
[18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
loading driver (-19)
[18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
deinitialized and disconnected
This isn't really a fix, I think i mentioned this on the ML ages ago,
Argh, I just replied that same. Oliver, do you has that same device? Is
it working? Could you tweak to see if I2C readings are working at all?
I have the same device, but mine works normally (though I haven't
checked for ages), I will try it tonight when I'm at home and don't
forget what happens with my current kernel.
Hard to test when it 'just works (tm)' :)
The bad firmware wories me, no clue where that error is from, using:
862604ab3fec0c94f4bf22b4cffd0d89 /lib/firmware/dvb-usb-af9035-02.fw
It means firmware is too short or long what is calculated. I added that
printing to notify users firmware is broken and could cause problems.
I suspect it is same issue what is with MxL5007t tuners too.
Maybe that kind of fix is needed:
https://patchwork.kernel.org/patch/2418471/
Someone should really find out whether or not these are coming with
register read operation with REPEATED START of STOP condition. Attach
hardware sniffer to device tuner I2C bus and look what kind of messages
there is actually.
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
