PATCH: v4l-experimental support for 6260 (3rd try)

[Alfonso Garcia]

This patch hopefully merges all the previous ones into a single change that can be applied over current v4l-experimental tree (the one whose last commit made it compliant with coding style guidelines). If you've left some time and patience test it and report the results.

Sorry for the exuberance of patches, but I'm still learning git and inasmuch as I tried I was not able to apply the three separate ones I sent over the latest commit (that had a lot of changes although only cosmetic) without a lot of manual editing. In the end, I preferred to send another patch that gathered all three and could be applicable on the top of the current tree.

[64BitJungle.com]

Alfonso,

This patch works so far on my system - mplayer successfully outputs
video from the webcam. However, I am getting a lot of Frame Buffer
Overflows in dmesg, followed by "Iso frame 1 of USB has error -71" :

[SNIP]
[ 4327.410485] microdia: Frame buffer overflow !
[ 4327.411731] microdia: Frame buffer overflow !
[ 4334.841658] microdia: Iso frame 1 of USB has error -71

System specs:

Acer Aspire 5052
AMD Turion 64x2
2Gb RAM
ATI Radeon Xpress series graphics
Ubuntu 8.04 64 Bit
ATI drivers are the latest Catalyst 8.5

>  0001-Added-support-for-6260-YUYV-and-more-verbose-debug-m.patch
> 7KDownload

[barbolani]

How long were you able to get video when these errors started to
appear? There's some people (including me) that are able to start
capturing but after 5-10 minutes we get only a black window. That
could be useful to diagnose if the problem is 64-bit specific, as I've
a 32 bit system and don't recall those errors in my log.

[64BitJungle.com]

The Frame buffer overflow error appeared immediately - I now have
another problem, in that my webcam isn't even being detected, and
don't even get any information from lsusb. I'll have to look further
into this before I can investigate the errors more :)

[64BitJungle.com]

OK, managed to get the camera detected once again. Interestingly, I'm
no longer getting frame buffer overflow errors to begin with, but
shortly after starting the camera, I'm getting Iso frame (n) of USB
has error -71

[ 3771.994349] microdia: Buffers Allocated 2
[ 3772.482243] microdia: I2C slave 0x50 returned error during write to
address 0x00
[ 3772.482250] microdia: No EEPROM found
[ 3786.773705] microdia: Iso frame 5 of USB has error -71
[ 3786.773713] microdia: Iso frame 6 of USB has error -71
[ 3786.773716] microdia: Iso frame 7 of USB has error -71
[ 3786.773718] microdia: Iso frame 8 of USB has error -71
[ 3786.773720] microdia: Iso frame 9 of USB has error -71
[ 3786.774324] microdia: Iso frame 3 of USB has error -71
[ 3786.774327] microdia: Iso frame 4 of USB has error -71
[ 3786.774329] microdia: Iso frame 5 of USB has error -71
[ 3786.774331] microdia: Iso frame 6 of USB has error -71
[ 3786.774333] microdia: Iso frame 7 of USB has error -71
[ 3786.774338] microdia: Iso frame 9 of USB has error -71

the errors appear continuously. The first Frame buffer overflow error
appears some time later:

[ 4018.090011] microdia: Frame buffer overflow !

The Iso frame... errors are by far more frequent. I've left the camera
running for about 20 minutes so far, and aside from flickers and
distortion every few seconds (and the above errors), it's still
running fine.

I'll run a few more tests and post the results :)

On Jun 1, 2:47 pm, barbolani <barbol...@gmail.com> wrote:

[Boris Borisov]

Hello

Can you test this patch for 6270 device for main tree of gid (not for
experimental).
This is patch provide turn on and of auto functions for device 6270. For
me improvement of picture quality is big.
To turn on auto functions after run the picture simply is do:
echo 1 > /sys/class/video4linux/video0/autotuning
To turn off
echo 0 > /sys/class/video4linux/video0/autotuning

Any proposal?

Bobby

[barbolani]

According to this http://kerneltrap.org/mailarchive/linux-kernel/2007/6/20/106716
source, the error -71 seems related to hardware . It's a low level
error associated with failures in communication across the bus, but
seems that it does not prevent devices to work. Could you try plugging
the cam on a different USB port or disconnecting other USB devices?

[barbolani]

Boris, I think that it will be better to post this as a new thread
rather than part of this conversation.

[JoJo jojo]

a device is getting unplugged & reconnected very often,
causing descriptors to be read, whats the o/p of dmesg ?

is your smps giving enuff juice ?

-JoJo

[64BitJungle.com]

Unfortunately, I can't plug the webcam into another USB port since
it's built in to the laptop (Acer Aspire 5052 - Acer OrbiCam), but I
should be able to unplug the only other device using USB (the wireless
card). Both devices are on different buses - the Microdia device is on
bus 3:

Bus 003 Device 002: ID 0c45:6260 Microdia

and the Broadcom wireless device on bus 1:

Bus 001 Device 004: ID 0a5c:2101 Broadcom Corp.

No other devices are using either Bus 1 or 3.

On Jun 2, 5:11 am, barbolani <barbol...@gmail.com> wrote:
> According to thishttp://kerneltrap.org/mailarchive/linux-kernel/2007/6/20/106716

[64BitJungle.com]

Hi JoJo,

It's a notebook (Acer Aspire 5052) so I'm hoping it's getting enough
power from the built in supply, lol! No other USB devices are plugged
in (except for the built in wireless)

dmesg output, from starting the camera via mplayer:

[34307.784255] microdia: Buffers Allocated 2
[34308.282296] microdia: I2C slave 0x50 returned error during write to
address 0x00
[34308.282304] microdia: No EEPROM found
[34308.397686] microdia: Frame buffer overflow !
[34308.397696] microdia: Frame buffer overflow !
[34308.397698] microdia: Frame buffer overflow !
[34308.397700] microdia: Frame buffer overflow !
[34308.397702] microdia: Frame buffer overflow !
[34308.398930] microdia: Frame buffer overflow !
[34308.398933] microdia: Frame buffer overflow !
[34308.398935] microdia: Frame buffer overflow !
[34308.398937] microdia: Frame buffer overflow !
[34308.398939] microdia: Frame buffer overflow !
[34308.398940] microdia: Frame buffer overflow !
[34308.398942] microdia: Frame buffer overflow !
[34308.398944] microdia: Frame buffer overflow !
[34308.498953] microdia: Frame buffer overflow !
[34308.498963] microdia: Frame buffer overflow !
[34308.500156] microdia: Frame buffer overflow !
[34308.566440] microdia: Frame buffer overflow !
[34308.566449] microdia: Frame buffer overflow !
[34308.598965] microdia: Frame buffer overflow !
[34308.665227] microdia: Frame buffer overflow !
[34308.666462] microdia: Frame buffer overflow !
[34308.703963] microdia: Frame buffer overflow !
[34308.717715] microdia: Frame buffer overflow !
[34310.228740] microdia: Iso frame 6 of USB has error -71
[34310.231242] microdia: Iso frame 9 of USB has error -71
[34310.237482] microdia: Iso frame 5 of USB has error -71
[34310.357488] microdia: Iso frame 3 of USB has error -71
[34310.357496] microdia: Iso frame 4 of USB has error -71
[34310.357502] microdia: Iso frame 7 of USB has error -71
[34310.357506] microdia: Iso frame 9 of USB has error -71
[34310.358750] microdia: Iso frame 7 of USB has error -71
[34310.359997] microdia: Iso frame 6 of USB has error -71
[34310.361233] microdia: Iso frame 0 of USB has error -71
[34310.361237] microdia: Iso frame 2 of USB has error -71
[34310.361243] microdia: Iso frame 5 of USB has error -71
[34310.361254] microdia: Iso frame 9 of USB has error -71
[34310.362482] microdia: Iso frame 0 of USB has error -71
[34310.362486] microdia: Iso frame 1 of USB has error -71
[34310.362488] microdia: Iso frame 2 of USB has error -71
[34310.362495] microdia: Iso frame 6 of USB has error -71
[34310.362498] microdia: Iso frame 7 of USB has error -71
[34310.362500] microdia: Iso frame 8 of USB has error -71
[34310.362502] microdia: Iso frame 9 of USB has error -71
[34310.363731] microdia: Iso frame 0 of USB has error -71
[SNIP]... continues until I stop mplayer, and thus the camera.

Cheers

On Jun 2, 7:59 am, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> a device is getting unplugged & reconnected very often,
> causing descriptors to be read, whats the o/p of dmesg ?
>
> is your smps giving enuff juice ?
>
> -JoJo
>
> On Sun, Jun 1, 2008 at 7:24 PM, 64BitJungle.com
>

[Boris Borisov]

See in threads before 1 month I describe this is hardware problem and
solution. This is problem is persist on low cost cameras (my is delux
dlv-b32).
barbolani написа:

[Boris Borisov]

Sorry my mistake.
barbolani написа:

[barbolani]

See this thread
http://groups.google.com/group/microdia/browse_frm/thread/45a1fe884fe9e49/ca8f5b0d23a3a9e6?lnk=gst&q=%22-71%22#ca8f5b0d23a3a9e6
for a more detailed explanation of the problem by Boris. It is
definitely a hardware error unrelated to the driver.

[64BitJungle.com]

Hi Boris and barbolani,

Thanks for the pointer - an interesting read, but since my camera is
built in to the notebook, I'll just have to live with the error until
I find the time to dismantle and try to repair it. In my case, it
could just as easily be a loose connection, since cables in notebooks
are pretty flimsy.

Deep down, I didn't think it was a driver problem, but thought to post
the errors just in case :)

I guess we can ignore "error -71", but how about the Frame Buffer
overflow? Could that be driver related, or related to the underlying H/
W issue?

On Jun 2, 7:58 pm, barbolani <barbol...@gmail.com> wrote:
> See this threadhttp://groups.google.com/group/microdia/browse_frm/thread/45a1fe884fe...

[barbolani]

Boris, I don't see any framebuffer errors, but the video in my system
freezes after 5-10 minutes with no dmesg output. Might be related to
this or not.

[Tiago Madeira]

Why isn't this patch applied to the repository yet?

[Boris Borisov]

barbolani написа:

> Boris, I don't see any framebuffer errors, but the video in my system
> freezes after 5-10 minutes with no dmesg output. Might be related to
> this or not.
> >
>
>

After freeze of picture can you put output from:
cat /proc/bus/usb/devices
If device is persist in this log, try to use USB expander cable about 1m
long and check again persistance of camera in
cat /proc/bus/usb/devices
If camera is not available in this log then the problem is in hardware.

Bobby