Bug 4769
| Summary: | PC104plus BT848 card stop working in PAL mode when 2.4 -> 2.6 switch | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Laurent Pointal (laurent.pointal) |
| Component: | Video(Other) | Assignee: | Nickolay V. Shmyrev (nshmyrev) |
| Status: | REJECTED DOCUMENTED | ||
| Severity: | normal | CC: | akpm, mchehab, nshmyrev |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.8 and 2.6.12-rc4 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5002 | ||
| Attachments: |
Messages log for test with 2.6.12.1
Messages log for test with 2.6.12.1 kern.log with trace/debug bttv and tuner options |
||
|
Description
Laurent Pointal
2005-06-21 01:27:31 UTC
Laurent. Your problem is interesing. First, can you try v4l cvs from linuxtv.org. Second, are you sure that only PAL channels are broken? And what country do you live, can't it be problem with standard detection/setting? Thanks for your interrest. I will try v4l from CVS (I have only this week to test, after I be back in august). I dont know if other channels are broken as I only used PAL because the camera we use seem to provide a PAL video signal (its the configuration I used with 2.4). I live in france, but I thought detection/settings only apply to tuner and the digital logic frame grabber card has no tuner, video signal goes directly to BT chip. Does location frequencies deal with BT chip too? Laurent. Nice, we are waiting for results. Actually it looks like wrong standard selection/detection. Probably enabling debug output and collection of some info can help. Created attachment 5227 [details]
Messages log for test with 2.6.12.1
I added built the kernel from 2.6.12.1 to have a recent one (previous tests was
with 2.6.12-rc4). And I activated trace/debug with module options.
Same problem, see messages log file attached.
I tried to go with V4L from CVS repository. But as I must cross compile using a
more powerful computer (embedded system has only 64MB of RAM and a PII266
processor), I mount the embedded system disk in my desktop and chroot to this
mounted system.
But I have problems to compile V4L. Eexporting KERNELRELEASE before calling
make is better (else makefile identify my host desktop linux as kernel version)
but dont achieve compilation (sources tries to get includes from
/usr/include/linux & Co which are base 2.6.8 includes of debian sarge, and some
symbols are missing).
Is ther a simple hack ?
Or, can I copy my entire sources tree of Linux and overwrite files in this
sources tree with ones from V4L CVS ?
Thanks.
Laurent.
Created attachment 5228 [details]
Messages log for test with 2.6.12.1
I added built the kernel from 2.6.12.1 to have a recent one (previous tests was
with 2.6.12-rc4). And I activated trace/debug with module options.
Same problem, see messages log file attached.
I tried to go with V4L from CVS repository. But as I must cross compile using a
more powerful computer (embedded system has only 64MB of RAM and a PII266
processor), I mount the embedded system disk in my desktop and chroot to this
mounted system.
But I have problems to compile V4L. Eexporting KERNELRELEASE before calling
make is better (else makefile identify my host desktop linux as kernel version)
but dont achieve compilation (sources tries to get includes from
/usr/include/linux & Co which are base 2.6.8 includes of debian sarge, and some
symbols are missing).
Is ther a simple hack ?
Or, can I copy my entire sources tree of Linux and overwrite files in this
sources tree with ones from V4L CVS ?
Thanks.
Laurent.
Finally I tried to compile directly on the embedded system, there were no so much files as I thought, compile and install well. But no better result. Laurent, thanks. I think since it's hard to build CVS for you, you need not to do that. But the goal is to collect debugging logs from bttv driver. This can be done by passing module option for bttv, like bttv_debug=1, bttv_irq=1 and so on. You can get full list of options with 'modinfo'. There are also some options related to color management, like chroma_ctl, you can also try to adjust them. Created attachment 5237 [details]
kern.log with trace/debug bttv and tuner options
kern.log with following modules options:
bttv: tuner=4 card=0 bttv_verbose=2 bttv_debug=1 bttv_gpio=1 irq_debug=1
tuner: type=4 debug=1 tuner_debug=1
Is this problem still present in 2.6.13-rc4? Btw, Laurent, can you confirm that hue/saturation settings in v4l application affect nothing? "can you confirm that hue/saturation settings in v4l application affect nothing" Yes (tested with xawtv) Laurent, from the picture, I noticed the board has a 28 MHz xtal. Please try to use pll=28 as insmod option for bttv. Mauro. Hi, Hi, this picture distortion (see http://www.limsi.fr/Individu/pointal/koala/capture-PAL.jpeg ) is caused by using wrong (or no) pll. You need "modprobe bttv pll=28" (alternatively "modprobe bttv pll=35" depending on your hardware). Btw. you don't need to compile a newer driver, this option has always been there. - Gunther I added pll=28 option for the btttv module... and all works well. Thanks a lot. Still dont know why it worked with 2.4 kernel... but now I can continue with the Koala robot. I will transmit information to other places where I asked for help. Note: I mark the bug as reject (documented), but I dont know what is exactly kernel managers policy about bug attributes management. |
