On 08/06/2012 11:37 AM, Andy Walls wrote:
James <bjloc...@lockie.ca> wrote:

On 08/04/12 13:42, Andy Walls wrote:
James <bjloc...@lockie.ca> wrote:

There's a big pause before the 'unable'

[    2.243856] usb 4-1: Manufacturer: Logitech
[   62.739097] cx25840 6-0044: unable to open firmware
v4l-cx23885-avcore-01.fw


I have a cx23885
cx23885[0]: registered device video0 [v4l2]

Is there any way to stop it from trying to load the firmware?
What is the firmware for, analog tv? Digital works fine and analog
is
useless to me.
I assume it is timing out there.
--
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

The firmware is for the analog broadcast audio standard (e.g. BTSC)
detection microcontroller.

The A/V core of the CX23885/7/8 chips is for analog vidoe and audio
processing (broadcast, CVBS, SVideo, audio L/R in).

The A/V core of the CX23885 provides the IR unit and the Video PLL
provides the timing for the IR unit.

The A/V core of the CX23888 provides the Video PLL which is the
timing for the IR unit in the CX23888.

Just grab the firmware and be done with it.  Don't waste time with
trying to make the cx23885 working properly but halfway.

Regards,
Andy

I already have the firmware.
# ls -l /lib/firmware/v4l-cx23885-avcore-01.fw
-rw-r--r-- 1 root root 16382 Oct 15  2011
/lib/firmware/v4l-cx23885-avcore-01.fw


--
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


Hmm.  The firmware file size and location look right.

The 60 second delay is the default kernel delay waiting for the userspace 
firmware loader to fetch th file amd provide it to the kernel via sysfs.

That doesn't appear to be happening.  I know udev runs some script to 
accomplish that.  I'm away from my development system, so I can't investigate 
further.

Regards,
Andy

I suspect it could be the firmware download issue with udev. Recent udev versions doesn't allow firmware download during module init path as module init should not be blocked such long period.

I did quite much work for resolving that issue for the dvb usb by deferring device init in probe using work-queue. It is not good looking solution and Mauro is still trying to found out more general solution.

regards
Antti

--
http://palosaari.fi/
--
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

Reply via email to