gatos-devel Mailing List for GATOS

Have you tried google?

On Sun, 29 Feb 2004 16:01:02 -0500
"Claude Gelinas agr." <cl...@ph...> wrote:

> I'm trying to install avview-0.80.3 but it need tcl/tk 8.4.x
>=20
> I'm on fedora core 1 with tcl/tk 8.3.x
>=20
> where can I find an rpm ofr tcl/tk 8.4.x
>=20
> Thank you
>=20
> --=20
> Claude G=E9linas agr., D.T.A.
>   PHYTO Ressources
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>  Varennes, Qu=E9bec, Canada       T=E9l: (450) 652 9764 Fax : (450) 652 6=
182
>   Des questions sur les insectes et maladies des plantes ornementales ?
>             Want to know more about ornamental plant pest ?
>                        http://www.phyto.qc.ca
>=20
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
> ---
> [This E-mail scanned for viruses by Declude Virus]
>=20
>=20

Interesting..

It might well be that your cpu/motherboard has problems keeping up with
data flow. This seems to happen on my system (PIII-700+VIA KT133).

km has certainly been written with assumption that you have plenty of PCI
bandwidth (as I don't know enough about PCI to deal intellegently with the
opposite case and I do know that video cards like to lock up hard..)

What happens if you capture to /dev/null ?

                            best

                                Vladimir Dergachev

On Sun, 29 Feb 2004, Francisco L Fernandez wrote:

> Vladimir:
>
> This is a typical 370 motherboard with VIA chipset and SDRAM memory
> interface, VIA 694T is the last incarnation of VIA apollo pro chipset,
> with PIII /Celeron Tualatin support. The RAM clock is 133 MHz CL2.
> The CPU is a weak one, VIA C3 Nehemiah, a low power dissipation,
> but also low processing power, specially in FPU related tasks. The raw
> power is like a Celeron 600, but I consider the memory bandwith to be
> higher because of the bus speed. As with it's Intel relatives, the C3
> can't take advantage of DDR memory (less than 10% memory performance
> increase).
>
> I haven't measured it (memory bandwith) but a similar setup could be a VIA
> EPIA V1000, and from some review:
>
> Sandra 2004 Memory bandwith ALU:  492 MB/s
> Sandra 2004 Memory bandwith FPU: 339 MB/s
>
> Teorethycal max. is about 1 GB/s.
>
> I try to avoid having to use the FPU by capturing straight to yuv and wav
> formats (only half width/heigth PAL).
>
> Here I post CPU related results from an Unix benchmark
>
> bash-2.05b# ./nbench
>
> BYTEmark* Native Mode Benchmark ver. 2 (10/95)
> Index-split by Andrew D. Balsa (11/97)
> Linux/Unix* port by Uwe F. Mayer (12/96,11/97)
>
> TEST                : Iterations/sec.  : Old Index   : New Index
>                     :                  : Pentium 90* : AMD K6/233*
> --------------------:------------------:-------------:------------
> NUMERIC SORT        :          292.32  :       7.50  :       2.46
> STRING SORT         :          30.871  :      13.79  :       2.14
> BITFIELD            :       7.373e+07  :      12.65  :       2.64
> FP EMULATION        :          20.263  :       9.72  :       2.24
> FOURIER             :          1879.6  :       2.14  :       1.20
> ASSIGNMENT          :           3.992  :      15.19  :       3.94
> IDEA                :           588.7  :       9.00  :       2.67
> HUFFMAN             :          317.21  :       8.80  :       2.81
> NEURAL NET          :          3.2959  :       5.29  :       2.23
> LU DECOMPOSITION    :          218.48  :      11.32  :       8.17
> ==========================ORIGINAL BYTEMARK RESULTS==================
> INTEGER INDEX       : 10.626
> FLOATING-POINT INDEX: 5.041
> Baseline (MSDOS*)   : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
> ==============================LINUX DATA BELOW==========================
> CPU                 : CentaurHauls VIA Nehemiah 1003MHz
> L2 Cache            : 64 KB
> OS                  : Linux 2.4.24-ck1
> C compiler          : gcc version 3.2.3
> libc                : ld-2.3.2.so
> MEMORY INDEX        : 2.811
> INTEGER INDEX       : 2.538
> FLOATING-POINT INDEX: 2.796
> Baseline (LINUX)    : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3,
> libc-5.4.38
> * Trademarks are property of their respective holder.
>
> This was run from X (fvwm2) with the computer iddle and two X apps (mail
> client and Mozilla firefox) running.
>
> And here you are some hdparm benchmarks too:
>
>  bash-2.05b# for n in 1 2 3 4
> > do
> > hdparm -t /dev/hdc
> > hdparm -T /dev/hdc
> > done
>
> /dev/hdc:
>  Timing buffered disk reads:  64 MB in  1.54 seconds = 41.45 MB/sec
>
> /dev/hdc:
>  Timing buffer-cache reads:   128 MB in  0.96 seconds =133.06 MB/sec
>
> /dev/hdc:
>  Timing buffered disk reads:  64 MB in  1.38 seconds = 46.24 MB/sec
>
> /dev/hdc:
>  Timing buffer-cache reads:   128 MB in  1.02 seconds =125.49 MB/sec
>
> /dev/hdc:
>  Timing buffered disk reads:  64 MB in  1.45 seconds = 44.26 MB/sec
>
> /dev/hdc:
>  Timing buffer-cache reads:   128 MB in  1.26 seconds =101.59 MB/sec
>
> /dev/hdc:
>  Timing buffered disk reads:  64 MB in  1.47 seconds = 43.48 MB/sec
>
> /dev/hdc:
>  Timing buffer-cache reads:   128 MB in  0.98 seconds =131.15 MB/sec
>
>
> That is all I can tell you.
>
> BTW: I have another computer very similar (same processor, memory and chipset)
> in which I have installed my AIW 128 pro, now I'm going to try to
> reproduce the same steps on it.
> This way I can contribute with some more testing for the other need-to-test
> chip family.
>
> If I had purchased an AIW 7500 while I could!.
>
> Best Regards
>
>
> On Sat, 28 Feb 2004 13:59:24 -0500 (EST)
> Vladimir Dergachev <vo...@mi...> wrote:
>
> > a s
> > Fernando - what kind of motherboard do you have ? In particular, what is
> > the speed of cpu<->memory interface ?
> >
> >                           best
> >
> >                             Vladimir Dergachev
> >
> > On Sat, 28 Feb 2004, Francisco L Fernandez wrote:
> >
> > > Hello,
> > >
> > > The problem with sound is now solved. I launch aumix in
> > > non-interactive mode to select line-in capture and volume, i.e.:
> > >
> > > aumix -i R -i 20
> > >
> > > As ffmpeg can't grab video using alsa interface.
> > > I have been debugging a bit more my problems capturing video, that I
> > > can summarize up in that there are some frames badly grabbed (I'd even
> > > say that they aren't completely copied out) and afterwards the
> > > following frames are displaced upside-down (the upper part of the
> > > frame appears at the bottom).
> > >Nehemiah  In a matter of one second or so, the frames turn again to the
> > >right place,
> > > but the problem comes again after some seconds.
> > > That is not dependant on the selected codec or file format (AVI, raw
> > > video...). All the tests are done with ffmpeg 0.4.8, cli driven.
> > >
> > > At first, I was thinking about bad framerate or artifacts in the
> > > original tape, but this happens with any tape.
> > > Finally I realized that in the kernel messages there were some lockup
> > > related messages:
> > >
> > > Capture buf size=442368
> > > mach64_get_window_parameters: width=768 height=288
> > > mach64_get_window_parameters: width=768 height=288
> > > km: /dev/video0 uses frame format 768x288
> > > km: mach64 engine lock up
> > > km: mach64 engine lock up
> > > km: mach64 engine lock up
> > > km: mach64 engine lock up
> > > km: closed stream, 3003 buffers captured
> > > Purging transfer queue
> > >
> > > Now I tend to think that there are some lockups in the capture
> > > process, and grabbing of some frames gets interrupted, thus causing
> > > that frame displacement effect.
> > >
> > > What could I do to avoid it?
> > >
> > > BTW: I remember similar messages with my AIW 128 pro, that exhibited
> > > the same problem.
> > >
> > > Best Regards
> > >
> > > On Tue, 24 Feb 2004 11:49:06 +0100
> > > Francisco L Fernandez <flu...@ja...> wrote:
> > >
> > > > I have other different problem with my setup and avview.
> > > > When I start the system I have some calls to amixer in ther rc.local
> > > > startup script. That select line in as the capture device and unmute
> > > > it. Then I can hear the sound coming from my VCR.
> > > > When I start X, the sound gets off.
> > > > Starting avview and switching the mute control gets the sound again,
> > > > but this time in mono. No matter which control I set I can't switch
> > > > to stereo output. Recorded sound is in mono mode also.
> > > >
> > > > This happens with avview v0.7.13 and 0.80.3 (last two versions).
> > > >
> > > > My Setup:
> > > >
> > > > Via Nehemiah 1GHz, Apollo pro 133 (VIA 694T) 512 MB RAM, AIW PRO 8MB
> > > > (3D Rage pro chip & BT829). Linux Slackware 9.1, kernel 2.4.24 with
> > > > Con Kolivas patches. km module from CVS (2004-02-15). Ati.2
> > > > experimental 14.
> > > >
> > > >
> > > > I have more problems that I'll post later, but this is the most
> > > > annoying now.
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > > Build and deploy apps & Web services for Linux with
> > > a free DVD software kit from IBM. Click Now!
> > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > > _______________________________________________
> > > Gatos-devel mailing list
> > > Gat...@li...
> > > https://lists.sourceforge.net/lists/listinfo/gatos-devel
> > >
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Gatos-devel mailing list
> > Gat...@li...
> > https://lists.sourceforge.net/lists/listinfo/gatos-devel
> >
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

I'm trying to install avview-0.80.3 but it need tcl/tk 8.4.x

I'm on fedora core 1 with tcl/tk 8.3.x

where can I find an rpm ofr tcl/tk 8.4.x

Thank you

--=20
Claude G=E9linas agr., D.T.A.
  PHYTO Ressources
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 Varennes, Qu=E9bec, Canada       T=E9l: (450) 652 9764 Fax : (450) 652 618=
2
  Des questions sur les insectes et maladies des plantes ornementales ?
            Want to know more about ornamental plant pest ?
                       http://www.phyto.qc.ca

Vladimir:

This is a typical 370 motherboard with VIA chipset and SDRAM memory
interface, VIA 694T is the last incarnation of VIA apollo pro chipset,
with PIII /Celeron Tualatin support. The RAM clock is 133 MHz CL2. 
The CPU is a weak one, VIA C3 Nehemiah, a low power dissipation,
but also low processing power, specially in FPU related tasks. The raw
power is like a Celeron 600, but I consider the memory bandwith to be
higher because of the bus speed. As with it's Intel relatives, the C3
can't take advantage of DDR memory (less than 10% memory performance
increase).

I haven't measured it (memory bandwith) but a similar setup could be a VIA
EPIA V1000, and from some review:

Sandra 2004 Memory bandwith ALU:  492 MB/s
Sandra 2004 Memory bandwith FPU: 339 MB/s

Teorethycal max. is about 1 GB/s.

I try to avoid having to use the FPU by capturing straight to yuv and wav
formats (only half width/heigth PAL).

Here I post CPU related results from an Unix benchmark

bash-2.05b# ./nbench

BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)

TEST                : Iterations/sec.  : Old Index   : New Index
                    :                  : Pentium 90* : AMD K6/233*
--------------------:------------------:-------------:------------
NUMERIC SORT        :          292.32  :       7.50  :       2.46
STRING SORT         :          30.871  :      13.79  :       2.14
BITFIELD            :       7.373e+07  :      12.65  :       2.64
FP EMULATION        :          20.263  :       9.72  :       2.24
FOURIER             :          1879.6  :       2.14  :       1.20
ASSIGNMENT          :           3.992  :      15.19  :       3.94
IDEA                :           588.7  :       9.00  :       2.67
HUFFMAN             :          317.21  :       8.80  :       2.81
NEURAL NET          :          3.2959  :       5.29  :       2.23
LU DECOMPOSITION    :          218.48  :      11.32  :       8.17
==========================ORIGINAL BYTEMARK RESULTS==================
INTEGER INDEX       : 10.626
FLOATING-POINT INDEX: 5.041
Baseline (MSDOS*)   : Pentium* 90, 256 KB L2-cache, Watcom* compiler 10.0
==============================LINUX DATA BELOW==========================
CPU                 : CentaurHauls VIA Nehemiah 1003MHz
L2 Cache            : 64 KB
OS                  : Linux 2.4.24-ck1
C compiler          : gcc version 3.2.3
libc                : ld-2.3.2.so
MEMORY INDEX        : 2.811
INTEGER INDEX       : 2.538
FLOATING-POINT INDEX: 2.796
Baseline (LINUX)    : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3,
libc-5.4.38
* Trademarks are property of their respective holder.

This was run from X (fvwm2) with the computer iddle and two X apps (mail
client and Mozilla firefox) running.

And here you are some hdparm benchmarks too:

 bash-2.05b# for n in 1 2 3 4
> do
> hdparm -t /dev/hdc                   
> hdparm -T /dev/hdc
> done

/dev/hdc:
 Timing buffered disk reads:  64 MB in  1.54 seconds = 41.45 MB/sec

/dev/hdc:
 Timing buffer-cache reads:   128 MB in  0.96 seconds =133.06 MB/sec

/dev/hdc:
 Timing buffered disk reads:  64 MB in  1.38 seconds = 46.24 MB/sec

/dev/hdc:
 Timing buffer-cache reads:   128 MB in  1.02 seconds =125.49 MB/sec

/dev/hdc:
 Timing buffered disk reads:  64 MB in  1.45 seconds = 44.26 MB/sec

/dev/hdc:
 Timing buffer-cache reads:   128 MB in  1.26 seconds =101.59 MB/sec

/dev/hdc:
 Timing buffered disk reads:  64 MB in  1.47 seconds = 43.48 MB/sec

/dev/hdc:
 Timing buffer-cache reads:   128 MB in  0.98 seconds =131.15 MB/sec


That is all I can tell you.

BTW: I have another computer very similar (same processor, memory and chipset)
in which I have installed my AIW 128 pro, now I'm going to try to
reproduce the same steps on it.
This way I can contribute with some more testing for the other need-to-test
chip family.

If I had purchased an AIW 7500 while I could!.

Best Regards


On Sat, 28 Feb 2004 13:59:24 -0500 (EST)
Vladimir Dergachev <vo...@mi...> wrote:

> a s
> Fernando - what kind of motherboard do you have ? In particular, what is
> the speed of cpu<->memory interface ?
> 
>                           best
> 
>                             Vladimir Dergachev
> 
> On Sat, 28 Feb 2004, Francisco L Fernandez wrote:
> 
> > Hello,
> >
> > The problem with sound is now solved. I launch aumix in
> > non-interactive mode to select line-in capture and volume, i.e.:
> >
> > aumix -i R -i 20
> >
> > As ffmpeg can't grab video using alsa interface.
> > I have been debugging a bit more my problems capturing video, that I
> > can summarize up in that there are some frames badly grabbed (I'd even
> > say that they aren't completely copied out) and afterwards the
> > following frames are displaced upside-down (the upper part of the
> > frame appears at the bottom).
> >Nehemiah  In a matter of one second or so, the frames turn again to the
> >right place,
> > but the problem comes again after some seconds.
> > That is not dependant on the selected codec or file format (AVI, raw
> > video...). All the tests are done with ffmpeg 0.4.8, cli driven.
> >
> > At first, I was thinking about bad framerate or artifacts in the
> > original tape, but this happens with any tape.
> > Finally I realized that in the kernel messages there were some lockup
> > related messages:
> >
> > Capture buf size=442368
> > mach64_get_window_parameters: width=768 height=288
> > mach64_get_window_parameters: width=768 height=288
> > km: /dev/video0 uses frame format 768x288
> > km: mach64 engine lock up
> > km: mach64 engine lock up
> > km: mach64 engine lock up
> > km: mach64 engine lock up
> > km: closed stream, 3003 buffers captured
> > Purging transfer queue
> >
> > Now I tend to think that there are some lockups in the capture
> > process, and grabbing of some frames gets interrupted, thus causing
> > that frame displacement effect.
> >
> > What could I do to avoid it?
> >
> > BTW: I remember similar messages with my AIW 128 pro, that exhibited
> > the same problem.
> >
> > Best Regards
> >
> > On Tue, 24 Feb 2004 11:49:06 +0100
> > Francisco L Fernandez <flu...@ja...> wrote:
> >
> > > I have other different problem with my setup and avview.
> > > When I start the system I have some calls to amixer in ther rc.local
> > > startup script. That select line in as the capture device and unmute
> > > it. Then I can hear the sound coming from my VCR.
> > > When I start X, the sound gets off.
> > > Starting avview and switching the mute control gets the sound again,
> > > but this time in mono. No matter which control I set I can't switch
> > > to stereo output. Recorded sound is in mono mode also.
> > >
> > > This happens with avview v0.7.13 and 0.80.3 (last two versions).
> > >
> > > My Setup:
> > >
> > > Via Nehemiah 1GHz, Apollo pro 133 (VIA 694T) 512 MB RAM, AIW PRO 8MB
> > > (3D Rage pro chip & BT829). Linux Slackware 9.1, kernel 2.4.24 with
> > > Con Kolivas patches. km module from CVS (2004-02-15). Ati.2
> > > experimental 14.
> > >
> > >
> > > I have more problems that I'll post later, but this is the most
> > > annoying now.
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Gatos-devel mailing list
> > Gat...@li...
> > https://lists.sourceforge.net/lists/listinfo/gatos-devel
> >
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
> 

Do you have TV picture running in AVview window ?

                    best

                        Vladimir Dergachev

On Sun, 29 Feb 2004, Pascal wrote:

> Hi,
>
> Here are the symptoms:
>   - km kernel module is inserted correctly and I get the following log info:
>
> Feb 29 11:30:35 belette kernel: Linux video capture interface: v1.00
> Feb 29 11:30:35 belette kernel: Kmultimedia API module version alpha-5.0
> loaded
> Feb 29 11:30:35 belette modprobe: modprobe: Can't locate module km_api_drv
> Feb 29 11:30:35 belette kernel: Kmultimedia module version alpha-3.0 loaded
> Feb 29 11:30:35 belette kernel: Page size is 4096
> sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=956
> Feb 29 11:30:35 belette kernel: km: using irq 11
> Feb 29 11:30:35 belette kernel: PCI: Found IRQ 11 for device 01:00.0
> Feb 29 11:30:35 belette kernel: PCI: Sharing IRQ 11 with 00:1d.0
> Feb 29 11:30:35 belette kernel: Register aperture is 0xeb000000 0x00010000
> Feb 29 11:30:35 belette kernel: kms variables: reg_aperture=0xe09cd000
> Feb 29 11:30:35 belette kernel: km: DMA_GUI_STATUS=0x00000002 entries=2
> Feb 29 11:30:35 belette kernel: sizeof(kmfl_template)=780
> sizeof(KM_FIELD)=52
> Feb 29 11:30:35 belette kernel: Device ATI Technologies Inc Radeon R250
> If [Radeon 9000] 01:00.0 (0x1002:0
> x4966) corresponds to /dev/video0
> Feb 29 11:30:35 belette kernel: kms variables: reg_aperture=0xe09cd000
>
> Then I run avview (0.12.0) which traces the wollowing:
>
> libzvbi available export modules:
>          HTML:keyword "html" mimetype "text/html" extension "html,htm"
>          PNG:keyword "png" mimetype "image/png" extension "png"
>          PPM:keyword "ppm" mimetype "image/x-portable-pixmap" extension
> "ppm"
>          Text:keyword "text" mimetype "text/plain" extension "txt"
>          VTX:keyword "vtx" mimetype "application/videotext" extension "vtx"
> This only works with km from CVS at the moment
> .setup.f.pane1.f.canvas.f.optionmenu0.menu
> NUM_ADAPTORS=1
> Adaptor 0: ATI Radeon Video Adapter
>                  type input video image
>                  ports 53
> 53 ATI Radeon Video Adapter
> master=.controlwin row=1 column=0
> Looking for km device that corresponds to PCI:01:00.0
> km_devs=control0
> read line=+STATUS
> read line=DEVICE_ID=ATI Technologies Inc Radeon R250 If [Radeon 9000]
> read line=LOCATION_ID=PCI:01:00.0
> read line=INSTANCE_ID=KM_DEVICE:0
> read line=VSYNC_COUNT=0
> read line=VBLANK_COUNT=0
> read line=VLINE_COUNT=0
> read line=V4L_DEVICE=0
> read line=VIDEO_STREAM_ACTIVE=0
> read line=VIDEO_STREAM_DATA_UNIT=4294967295
> read line=VIDEO_STREAM_INFO_DATA_UNIT=4294967295
> read line=VBI_DEVICE=224
> read line=VBI_STREAM_DATA_UNIT=4294967295
> read line=VBI_STREAM_INFO_DATA_UNIT=4294967295
> read line=VBI_STREAM_ACTIVE=0
> read line=+END_STATUS
> Current picture parameters: depth=16 palette=7
>
>
> Everything looks ok. Then in avview menu, I select the capture (V4L)
> submenu and I get the following trace in the syslog:
>
> Feb 29 13:49:52 belette kernel: Processing "VIDEO_STREAM_ACTIVE"="1"
> int_value=1
> Feb 29 13:49:52 belette kernel: Purging transfer queue
> Feb 29 13:49:52 belette kernel: radeon_get_window_parameters: width=640
> height=0
> Feb 29 13:49:52 belette kernel: Capture buf size=0
> Feb 29 13:49:52 belette kernel: km: vmalloc_32(0) failed
> Feb 29 13:49:52 belette last message repeated 4 times
> Feb 29 13:49:52 belette kernel: RADEON_BUS_CNTL=0x5133a3b0
> Feb 29 13:49:52 belette kernel: Starting GUIDMA queue
> Feb 29 13:49:52 belette kernel: radeon_get_window_parameters: width=640
> height=0
> Feb 29 13:49:52 belette kernel: Stopping GUIDMA queue
> Feb 29 13:49:52 belette kernel: km: closed stream, 0 buffers captured
> Feb 29 13:49:52 belette kernel: Purging transfer queue
>
>
> And of course I get nothing on the screen. Any hints ? Where are coming
> from this "height=0" ???
>
> Thanks in advance.
>
> --Pascal
>
> PS: Of course, I run the ati.2 XFree driver which correctly works for TV
> output.
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Hi,

Here are the symptoms:
  - km kernel module is inserted correctly and I get the following log info:

Feb 29 11:30:35 belette kernel: Linux video capture interface: v1.00
Feb 29 11:30:35 belette kernel: Kmultimedia API module version alpha-5.0 
loaded
Feb 29 11:30:35 belette modprobe: modprobe: Can't locate module km_api_drv
Feb 29 11:30:35 belette kernel: Kmultimedia module version alpha-3.0 loaded
Feb 29 11:30:35 belette kernel: Page size is 4096 
sizeof(bm_list_descriptor)=16 sizeof(KM_STRUCT)=956
Feb 29 11:30:35 belette kernel: km: using irq 11
Feb 29 11:30:35 belette kernel: PCI: Found IRQ 11 for device 01:00.0
Feb 29 11:30:35 belette kernel: PCI: Sharing IRQ 11 with 00:1d.0
Feb 29 11:30:35 belette kernel: Register aperture is 0xeb000000 0x00010000
Feb 29 11:30:35 belette kernel: kms variables: reg_aperture=0xe09cd000
Feb 29 11:30:35 belette kernel: km: DMA_GUI_STATUS=0x00000002 entries=2
Feb 29 11:30:35 belette kernel: sizeof(kmfl_template)=780 
sizeof(KM_FIELD)=52
Feb 29 11:30:35 belette kernel: Device ATI Technologies Inc Radeon R250 
If [Radeon 9000] 01:00.0 (0x1002:0
x4966) corresponds to /dev/video0
Feb 29 11:30:35 belette kernel: kms variables: reg_aperture=0xe09cd000

Then I run avview (0.12.0) which traces the wollowing:

libzvbi available export modules:
         HTML:keyword "html" mimetype "text/html" extension "html,htm"
         PNG:keyword "png" mimetype "image/png" extension "png"
         PPM:keyword "ppm" mimetype "image/x-portable-pixmap" extension 
"ppm"
         Text:keyword "text" mimetype "text/plain" extension "txt"
         VTX:keyword "vtx" mimetype "application/videotext" extension "vtx"
This only works with km from CVS at the moment
.setup.f.pane1.f.canvas.f.optionmenu0.menu
NUM_ADAPTORS=1
Adaptor 0: ATI Radeon Video Adapter
                 type input video image
                 ports 53
53 ATI Radeon Video Adapter
master=.controlwin row=1 column=0
Looking for km device that corresponds to PCI:01:00.0
km_devs=control0
read line=+STATUS
read line=DEVICE_ID=ATI Technologies Inc Radeon R250 If [Radeon 9000]
read line=LOCATION_ID=PCI:01:00.0
read line=INSTANCE_ID=KM_DEVICE:0
read line=VSYNC_COUNT=0
read line=VBLANK_COUNT=0
read line=VLINE_COUNT=0
read line=V4L_DEVICE=0
read line=VIDEO_STREAM_ACTIVE=0
read line=VIDEO_STREAM_DATA_UNIT=4294967295
read line=VIDEO_STREAM_INFO_DATA_UNIT=4294967295
read line=VBI_DEVICE=224
read line=VBI_STREAM_DATA_UNIT=4294967295
read line=VBI_STREAM_INFO_DATA_UNIT=4294967295
read line=VBI_STREAM_ACTIVE=0
read line=+END_STATUS
Current picture parameters: depth=16 palette=7


Everything looks ok. Then in avview menu, I select the capture (V4L) 
submenu and I get the following trace in the syslog:

Feb 29 13:49:52 belette kernel: Processing "VIDEO_STREAM_ACTIVE"="1" 
int_value=1
Feb 29 13:49:52 belette kernel: Purging transfer queue
Feb 29 13:49:52 belette kernel: radeon_get_window_parameters: width=640 
height=0
Feb 29 13:49:52 belette kernel: Capture buf size=0
Feb 29 13:49:52 belette kernel: km: vmalloc_32(0) failed
Feb 29 13:49:52 belette last message repeated 4 times
Feb 29 13:49:52 belette kernel: RADEON_BUS_CNTL=0x5133a3b0
Feb 29 13:49:52 belette kernel: Starting GUIDMA queue
Feb 29 13:49:52 belette kernel: radeon_get_window_parameters: width=640 
height=0
Feb 29 13:49:52 belette kernel: Stopping GUIDMA queue
Feb 29 13:49:52 belette kernel: km: closed stream, 0 buffers captured
Feb 29 13:49:52 belette kernel: Purging transfer queue


And of course I get nothing on the screen. Any hints ? Where are coming 
from this "height=0" ???

Thanks in advance.

--Pascal

PS: Of course, I run the ati.2 XFree driver which correctly works for TV 
output.

Applied.

      Thank you !

                Vladimir Dergachev

On Tue, 24 Feb 2004, Konstantin A. Lepikhov wrote:

> Hi!
>
> This patch eliminates two problems:
>
> 1) km don't know about R200QL chips (some cheap 8500LE VIVO cards), so I
> added definitions for this chip.
>
> 2) km redefine irqreturn_t for 2.4. Kernels from 2.4.22 have this
> typedef in <linux/interrupt.h> for compatibility with 2.6 and with
> definition don't needed. Also I add checking for right version (>=2.4.22)
>
> In my case, this patch solved all build and detection problems with km.
>
> --
> WBR, Konstantin	      chat with ==>ICQ: 109916175
>      Lepikhov,	      speak  to ==>JID: lak...@ja...
> aka L.A. Kostis       write  to ==>mailto:lak...@pi...
>
> ...The information is like the bank... 			  (c) EC8OR
>

> >  have Radeon 7500, how did the install the Gatos drivers.
> > BTW, the only thing I want from the Gatos drivers is the Tvout. So, if
> > there  is a shortcut I am willing to take it. Just to remind you, I have
> > xfree  4.3.99.902 installed.
            ^^^^^^^^^^^^^^^

This is really XFree86 4.4.0 prerelease, while the driver source is
against 4.3.0. Try compiling against 4.3.0 source.

                    best

                      Vladimir Dergachev

> >
> > Thank you,
> > Vasilis
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Gatos-devel mailing list
> > Gat...@li...
> > https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Fernando - what kind of motherboard do you have ? In particular, what is
the speed of cpu<->memory interface ?

                          best

                            Vladimir Dergachev

On Sat, 28 Feb 2004, Francisco L Fernandez wrote:

> Hello,
>
> The problem with sound is now solved. I launch aumix in non-interactive
> mode to select line-in capture and volume, i.e.:
>
> aumix -i R -i 20
>
> As ffmpeg can't grab video using alsa interface.
> I have been debugging a bit more my problems capturing video, that I can
> summarize up in that there are some frames badly grabbed (I'd even say
> that they aren't completely copied out) and afterwards the following
> frames are displaced upside-down (the upper part of the frame appears at
> the bottom).
> In a matter of one second or so, the frames turn again to the right place,
> but the problem comes again after some seconds.
> That is not dependant on the selected codec or file format (AVI, raw
> video...). All the tests are done with ffmpeg 0.4.8, cli driven.
>
> At first, I was thinking about bad framerate or artifacts in the original
> tape, but this happens with any tape.
> Finally I realized that in the kernel messages there were some lockup
> related messages:
>
> Capture buf size=442368
> mach64_get_window_parameters: width=768 height=288
> mach64_get_window_parameters: width=768 height=288
> km: /dev/video0 uses frame format 768x288
> km: mach64 engine lock up
> km: mach64 engine lock up
> km: mach64 engine lock up
> km: mach64 engine lock up
> km: closed stream, 3003 buffers captured
> Purging transfer queue
>
> Now I tend to think that there are some lockups in the capture process,
> and grabbing of some frames gets interrupted, thus causing that frame
> displacement effect.
>
> What could I do to avoid it?
>
> BTW: I remember similar messages with my AIW 128 pro, that exhibited the
> same problem.
>
> Best Regards
>
> On Tue, 24 Feb 2004 11:49:06 +0100
> Francisco L Fernandez <flu...@ja...> wrote:
>
> > I have other different problem with my setup and avview.
> > When I start the system I have some calls to amixer in ther rc.local
> > startup script. That select line in as the capture device and unmute it.
> > Then I can hear the sound coming from my VCR.
> > When I start X, the sound gets off.
> > Starting avview and switching the mute control gets the sound again, but
> > this time in mono. No matter which control I set I can't switch to
> > stereo output. Recorded sound is in mono mode also.
> >
> > This happens with avview v0.7.13 and 0.80.3 (last two versions).
> >
> > My Setup:
> >
> > Via Nehemiah 1GHz, Apollo pro 133 (VIA 694T) 512 MB RAM, AIW PRO 8MB (3D
> > Rage pro chip & BT829). Linux Slackware 9.1, kernel 2.4.24 with Con
> > Kolivas patches. km module from CVS (2004-02-15). Ati.2 experimental 14.
> >
> >
> > I have more problems that I'll post later, but this is the most annoying
> > now.
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Hello,

The problem with sound is now solved. I launch aumix in non-interactive
mode to select line-in capture and volume, i.e.:

aumix -i R -i 20

As ffmpeg can't grab video using alsa interface.
I have been debugging a bit more my problems capturing video, that I can
summarize up in that there are some frames badly grabbed (I'd even say
that they aren't completely copied out) and afterwards the following
frames are displaced upside-down (the upper part of the frame appears at
the bottom). 
In a matter of one second or so, the frames turn again to the right place,
but the problem comes again after some seconds.
That is not dependant on the selected codec or file format (AVI, raw
video...). All the tests are done with ffmpeg 0.4.8, cli driven.

At first, I was thinking about bad framerate or artifacts in the original
tape, but this happens with any tape.
Finally I realized that in the kernel messages there were some lockup
related messages:

Capture buf size=442368
mach64_get_window_parameters: width=768 height=288
mach64_get_window_parameters: width=768 height=288
km: /dev/video0 uses frame format 768x288
km: mach64 engine lock up
km: mach64 engine lock up
km: mach64 engine lock up
km: mach64 engine lock up
km: closed stream, 3003 buffers captured
Purging transfer queue

Now I tend to think that there are some lockups in the capture process,
and grabbing of some frames gets interrupted, thus causing that frame
displacement effect.

What could I do to avoid it?

BTW: I remember similar messages with my AIW 128 pro, that exhibited the
same problem.

Best Regards
 
On Tue, 24 Feb 2004 11:49:06 +0100
Francisco L Fernandez <flu...@ja...> wrote:

> I have other different problem with my setup and avview.
> When I start the system I have some calls to amixer in ther rc.local
> startup script. That select line in as the capture device and unmute it.
> Then I can hear the sound coming from my VCR.
> When I start X, the sound gets off.
> Starting avview and switching the mute control gets the sound again, but
> this time in mono. No matter which control I set I can't switch to
> stereo output. Recorded sound is in mono mode also.
> 
> This happens with avview v0.7.13 and 0.80.3 (last two versions).
> 
> My Setup:
> 
> Via Nehemiah 1GHz, Apollo pro 133 (VIA 694T) 512 MB RAM, AIW PRO 8MB (3D
> Rage pro chip & BT829). Linux Slackware 9.1, kernel 2.4.24 with Con
> Kolivas patches. km module from CVS (2004-02-15). Ati.2 experimental 14.
> 
> 
> I have more problems that I'll post later, but this is the most annoying
> now.

On Fri, 2004-02-27 at 09:47, Lee Parmeter wrote:
> What version of avview and etc will compile on Fedora
> Core 1 with stock kernels?
>=20
> I will be upgrading to Fedora Core 2 in April and
> would also like to get avview working.=20
>=20
> I do not have to have capture support immediately, but
> would like to have the remote working on both
> installations.
>=20
> I have an ati AIW7500 ACP video board. I have it fully
> working with avview on RH9 now.
>=20
> LMK
> Lee
>=20
> =3D=3D=3D=3D=3D
> --
> Linux Registered User #337161=20
> 'It's free. It works. Duh.'" - Eric Harrison
> God is not a republican or a democrat nor is His government a democracy! =
- Lee Parmeter


Hello Lee,

I'm using Fedora Core1 and this is what I installed:

ATI-4.3.0-14.i386
drm-kernel-1.100.0-14
km-0.5.0
ffmpeg-0.4.8
avview-0.80.3

You'll need to install a few other programs for full functionality.  I
downloaded most from http://yarrow.freshrpms.net

I also had to set the LD_LIBRARY_PATH variable for Tcl/Tk 8.4 which I
compiled from source.

Hope this helps.
Anne =C2=A7:-)

Hi, 
How is the status of the radeon all in wonder 9800 se support. 
As far as I recall it has a Radeon or Rage Theatre 200 chipset.
How can I help to improve the support for that chipset?

Greetings, 
Andreas Pokorny

What version of avview and etc will compile on Fedora
Core 1 with stock kernels?

I will be upgrading to Fedora Core 2 in April and
would also like to get avview working. 

I do not have to have capture support immediately, but
would like to have the remote working on both
installations.

I have an ati AIW7500 ACP video board. I have it fully
working with avview on RH9 now.

LMK
Lee

=====
--
Linux Registered User #337161 
'It's free. It works. Duh.'" - Eric Harrison
God is not a republican or a democrat nor is His government a democracy! - Lee Parmeter

__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

FYI:

Relieved to see that some Distro besides Mandrake has
an aVview package pre-compiled. Both Alsa and aVview
install flawlessly.

If you can just get passed getting Debian installed
(still working on this!), it is very well supported
with deb packages!

Lee

=====
--
Linux Registered User #337161 
'It's free. It works. Duh.'" - Eric Harrison
God is not a republican or a democrat nor is His government a democracy! - Lee Parmeter

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

SGVsbG8gdGhlcmUsDQpXaGVyZSBjYW4gSSBmaW5kIHRoZSBwYXRjaCBmb3IgdGhlIFJDNC40PyBU
aGFua3MuDQo=

I have other different problem with my setup and avview.
When I start the system I have some calls to amixer in ther rc.local startup script.
That select line in as the capture device and unmute it.
Then I can hear the sound coming from my VCR.
When I start X, the sound gets off.
Starting avview and switching the mute control gets the sound again, but this time in mono.
No matter which control I set I can't switch to stereo output.
Recorded sound is in mono mode also.

This happens with avview v0.7.13 and 0.80.3 (last two versions).

My Setup:

Via Nehemiah 1GHz, Apollo pro 133 (VIA 694T) 512 MB RAM, AIW PRO 8MB (3D Rage pro chip & BT829).
Linux Slackware 9.1, kernel 2.4.24 with Con Kolivas patches.
km module from CVS (2004-02-15). Ati.2 experimental 14. 

I have more problems that I'll post later, but this is the most annoying now.

On Thu, 19 Feb 2004 15:31:44 -0600
Andrew Gaffney <aga...@sk...> wrote:

> I've temporarily switched back to my 2.6.1 kernel since I can get the km module to build 
> against it. I'm playing with avview for watching TV. I can get it to switch channels and 
> everything, but there is no sound. I've checked to make sure the volume is up in the ALSA 
> mixer and my speakers are on. I've fiddled with the ALSA mixer settings in avview, but no 
> sound. Am I doing something wrong or missing a step?
> 
> -- 
> Andrew Gaffney
> Network Administrator
> Skyline Aeronautics, LLC.
> 636-357-1548
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
> 

Hi!

This patch eliminates two problems:

1) km don't know about R200QL chips (some cheap 8500LE VIVO cards), so I
added definitions for this chip.

2) km redefine irqreturn_t for 2.4. Kernels from 2.4.22 have this
typedef in <linux/interrupt.h> for compatibility with 2.6 and with
definition don't needed. Also I add checking for right version (>=2.4.22)

In my case, this patch solved all build and detection problems with km.

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lak...@ja...
aka L.A. Kostis       write  to ==>mailto:lak...@pi...

...The information is like the bank... 			  (c) EC8OR

20-Feb-04 at 13:50, Andrew Gaffney (aga...@sk...) wrote :
> Andrew Gaffney wrote:
> >Simon White wrote:
> >
> >>20-Feb-04 at 10:34, Andrew Gaffney (aga...@sk...) wrote :
> >>
> >>>Also, I tried watching TV with xawtv. I don't have any sound there 
> >>>either. I launched aumix and switched between all the recording 
> >>>sources. No TV sound. All the volumes are at around 84. No sound. I 
> >>>bang my head against the nearest wall. No sound.
> >>
> >>If banging your head makes no sound, either you have a soft head or
> >>you're stone deaf :-)
> >>
> >>More seriously, if your card is like mine, the sound comes out of the
> >>AIW card and finishes in a stereo 3.5mm jack which then plugs in to line
> >>in on the other card. Can you plug this in to something else and find
> >>out if it works (line in on a HiFi or something?) or plug some other
> >>source into your soundcard and see if you can hear that?
> >
> >Nope. From left to right on the card: VGA, S-video looking port labeled 
> >'A/V Out', coax labaled 'CATV', another S-video thingy labeled 'A/V In'. 
> >No standard audio jack.
> 
> I just found a PDF manual for my card on ATI's website. Apparently, I need 
> a '3-headed output adapter' to plug into the 'A/V Out' port on the card. It 
> splits into S-Video, RCA Video, and audio. Anyone know where I can get one 
> of these things?

Mine came with the card, I looked recently because of this thread and
it's indeed a sort of dongle thing which splits out into audio +
composite + svideo.

ATI used to have a link to a site that would sell the cables, because
they also sold the upgrade CD for their multimedia center and new DVD
software in Windows (which I thought was mighty cheap of them, asking
for ten bucks for a CD in order to be able to upgrade).

Regards,

-- 
Simon White. Internet Consultant, Linux/Windows Server Administration.
email, dns and web servers; php javascript perl asp; MySQL MSSQL Access
     Bridging the gap between management, HR and the tech team.

On 22-Feb-04 at 17:30, gk...@ce... (gk...@ce...) wrote:
> On Sunday 22 February 2004 02:09 pm, Nikolai Zhubr wrote:
> > Hi,
> > Sunday, 22 February, 2004, 0:37:58, gk...@ce... wrote:
> > [...]
> >
> > > radeon_probe.c:95: error: `PCI_CHIP_R200_Qh' undeclared here (not in a
> > > function)
> >
> > [...]
> >
> > > make: *** [radeon_probe.o] Error 1
> > >
> > >
> > > Now, what do I need to do?
> >
> > If I were you I'd simply add those
> > PCI_CHIP_R200_Qh ... PCI_CHIP_R200_Ql constants by hand to
> > the header file where other PCI_CHIP_xxx... are defined.
> > If your card is not one of those (Qh to Ql range) then you
> > probably don't even need to bother about their actual
> > values.
> 
> Because I do not know how to set the value (I know very few about C) I did 
> something else, I erased the lines. 
> There is one more error, however....
> In file included from atistruct.h:35,
>                  from atixv.c:25:
> atiregs.h:1078:1: warning: this is the location of the previous definition
> atixv.c: In function `ATIReadMM_TABLE':
> atixv.c:1126: warning: too many arguments for format
> atixv.c:1156: warning: too many arguments for format
> atixv.c: In function `ATIPutImage':
> atixv.c:2051: error: `pScreen' undeclared (first use in this function)
> atixv.c:2051: error: (Each undeclared identifier is reported only once
> atixv.c:2051: error: for each function it appears in.)
> atixv.c:2051: warning: left-hand operand of comma expression has no effect
> atixv.c:2051: warning: value computed is not used
> atixv.c: In function `ATIPutVideo':
> atixv.c:2499: error: `pScreen' undeclared (first use in this function)
> atixv.c:2499: warning: left-hand operand of comma expression has no effect
> atixv.c:2499: warning: value computed is not used
> atixv.c: At top level:
> atixv.c:571: warning: `MPP_ImpactTV_read32' defined but not used
> make: *** [atixv.o] Error 1
> 
> I could do the same thing here, i.e., erase the corresponding lines, but
> then  I do not know if this is going to work.
> 
> Am I the only one who has this problem? I am sure that there are people who

No, you are not the only one. I have mentioned the pScreen problem before. I
suspect the ones that have the ability to fix this don't see the problem,
probably because they are working from xfree 4.3.

>  have Radeon 7500, how did the install the Gatos drivers.
> BTW, the only thing I want from the Gatos drivers is the Tvout. So, if
> there  is a shortcut I am willing to take it. Just to remind you, I have
> xfree  4.3.99.902 installed.
> 
> Thank you,
> Vasilis
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

On Sunday 22 February 2004 02:09 pm, Nikolai Zhubr wrote:
> Hi,
> Sunday, 22 February, 2004, 0:37:58, gk...@ce... wrote:
> [...]
>
> > radeon_probe.c:95: error: `PCI_CHIP_R200_Qh' undeclared here (not in a
> > function)
>
> [...]
>
> > make: *** [radeon_probe.o] Error 1
> >
> >
> > Now, what do I need to do?
>
> If I were you I'd simply add those
> PCI_CHIP_R200_Qh ... PCI_CHIP_R200_Ql constants by hand to
> the header file where other PCI_CHIP_xxx... are defined.
> If your card is not one of those (Qh to Ql range) then you
> probably don't even need to bother about their actual
> values.

Because I do not know how to set the value (I know very few about C) I did 
something else, I erased the lines. 
There is one more error, however....
In file included from atistruct.h:35,
                 from atixv.c:25:
atiregs.h:1078:1: warning: this is the location of the previous definition
atixv.c: In function `ATIReadMM_TABLE':
atixv.c:1126: warning: too many arguments for format
atixv.c:1156: warning: too many arguments for format
atixv.c: In function `ATIPutImage':
atixv.c:2051: error: `pScreen' undeclared (first use in this function)
atixv.c:2051: error: (Each undeclared identifier is reported only once
atixv.c:2051: error: for each function it appears in.)
atixv.c:2051: warning: left-hand operand of comma expression has no effect
atixv.c:2051: warning: value computed is not used
atixv.c: In function `ATIPutVideo':
atixv.c:2499: error: `pScreen' undeclared (first use in this function)
atixv.c:2499: warning: left-hand operand of comma expression has no effect
atixv.c:2499: warning: value computed is not used
atixv.c: At top level:
atixv.c:571: warning: `MPP_ImpactTV_read32' defined but not used
make: *** [atixv.o] Error 1

I could do the same thing here, i.e., erase the corresponding lines, but then 
I do not know if this is going to work.

Am I the only one who has this problem? I am sure that there are people who 
have Radeon 7500, how did the install the Gatos drivers.
BTW, the only thing I want from the Gatos drivers is the Tvout. So, if there 
is a shortcut I am willing to take it. Just to remind you, I have xfree 
4.3.99.902 installed.

Thank you,
Vasilis

Hi,
Sunday, 22 February, 2004, 0:37:58, gk...@ce... wrote:
[...]
> radeon_probe.c:95: error: `PCI_CHIP_R200_Qh' undeclared here (not in a 
> function)
[...]
> make: *** [radeon_probe.o] Error 1


> Now, what do I need to do?
If I were you I'd simply add those
PCI_CHIP_R200_Qh ... PCI_CHIP_R200_Ql constants by hand to
the header file where other PCI_CHIP_xxx... are defined.
If your card is not one of those (Qh to Ql range) then you
probably don't even need to bother about their actual
values.
-- 
Best regards,
 Nikolai Zhubr
 
> Vasilis




> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

by default it is RGB output not YPBPR, so I thing 
a driver is necessary. or need special setting?
( change modeline in XF86Config-4 can't work for me)


 --- "William M. Quarles" <wa...@be...>
的訊息：> Hardy,
> 
> Seems not very necessary, since HDTVs are coming
> with DVI inputs now,
> which is better quality than the component inputs
> without the hassle of
> setting up the special drivers.  However, I'm not a
> developer on the
> project, I guess it's up to them
> 
> William
> 
> hardy.weng wrote:
> > Hi, 
> > 
> >    any plan to support HDTV adapter?(S-video
> output to
> > view internet is too bad)
> > 
> >    I can help at this, but need spec.
> > 
> > Hardy
> > 
> >
>
-----------------------------------------------------------------
> > 每天都 Yahoo!奇摩
> > 海的顏色、風的氣息、愛你的溫度，盡在信紙底圖
> >
>
http://tw.promo.yahoo.com/mail_premium/stationery.html
> > 
> > 
> >
>
-------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux
> Apps Now.
> > Build and deploy apps & Web services for Linux
> with
> > a free DVD software kit from IBM. Click Now!
> >
>
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Gatos-devel mailing list
> > Gat...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/gatos-devel
> > 
> 
> 
> 
>
-------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps
> Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
>
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
>
https://lists.sourceforge.net/lists/listinfo/gatos-devel 

-----------------------------------------------------------------
每天都 Yahoo!奇摩
海的顏色、風的氣息、愛你的溫度，盡在信紙底圖
http://tw.promo.yahoo.com/mail_premium/stationery.html

Hardy,

Seems not very necessary, since HDTVs are coming with DVI inputs now,
which is better quality than the component inputs without the hassle of
setting up the special drivers.  However, I'm not a developer on the
project, I guess it's up to them

William

hardy.weng wrote:
> Hi, 
> 
>    any plan to support HDTV adapter?(S-video output to
> view internet is too bad)
> 
>    I can help at this, but need spec.
> 
> Hardy
> 
> -----------------------------------------------------------------
> 每天都 Yahoo!奇摩
> 海的顏色、風的氣息、愛你的溫度，盡在信紙底圖
> http://tw.promo.yahoo.com/mail_premium/stationery.html
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
> 

On Sat, Feb 21, 2004 at 05:52:15PM +0300, Nikolai Zhubr wrote:
> Hi,
> Saturday, 21 February, 2004, 6:43:49, Andrew Gaffney wrote:
> [...]
> > Silly me. I need to RTFM. With no command line options, ffmpeg defaults to v4l input. I 
> > just needed to 'ffmpeg -s 320x240 file.mpg' with xawtv or avview running.
> 
> Note, there used to be some magic incorporated into ffmpeg
> to automatically take care of interlaced input when fed from
> km device. I don't have latest version here right now and I'm
> not sure if it is still there. If it doesn't, then you'll get
> "jumping" recordings.

Simplest way, if you're at 320x240.. always capture the same field, and
drop the other. Avoids deinterlacing problems, too.

R C

> You need to read the instructions in the X tarballs and configure the build
> like you were going to build all of X from source.

Ok,
I run make World in the folder of the X source. It compiled without any 
problem and then I went back to the ati.2 folder. I run xmkmf /tmp/xc it gave
mv -f Makefile Makefile.bak
imake -I/tmp/xc/config/cf -DTOPDIR=/tmp/xc -DCURDIR=.

and then I run make, which gave the following error

rm -f radeon_probe.o
gcc -m32 -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic -Wall 
-Wpointer-arith -Wstrict-prototypes                          
-Wmissing-prototypes -Wmissing-declarations                           
-Wredundant-decls -Wnested-externs -Wundef   -fno-stack-protector 
-fno-merge-constants -I. -I/tmp/xc/programs/Xserver/hw/xfree86/common 
-I/tmp/xc/programs/Xserver/hw/xfree86/os-support 
-I/tmp/xc/programs/Xserver/hw/xfree86            
-I/tmp/xc/programs/Xserver/hw/xfree86/vbe 
-I/tmp/xc/programs/Xserver/hw/xfree86/int10            
-I/tmp/xc/programs/Xserver/hw/xfree86/ddc 
-I/tmp/xc/programs/Xserver/hw/xfree86/i2c            
-I/tmp/xc/programs/Xserver/hw/xfree86/rac 
-I/tmp/xc/programs/Xserver/hw/xfree86/ramdac            
-I/tmp/xc/programs/Xserver/hw/xfree86/shadowfb 
-I/tmp/xc/programs/Xserver/hw/xfree86/xaa 
-I/tmp/xc/programs/Xserver/hw/xfree86/xf24_32bpp            
-I/tmp/xc/programs/Xserver/hw/xfree86/xf4bpp 
-I/tmp/xc/programs/Xserver/hw/xfree86/xf1bpp            
-I/tmp/xc/programs/Xserver/hw/xfree86/vgahw 
-I/tmp/xc/programs/Xserver/hw/xfree86/fbdevhw            
-I/tmp/xc/programs/Xserver/cfb -I/tmp/xc/programs/Xserver/mfb            
-I/tmp/xc/programs/Xserver/fb -I/tmp/xc/programs/Xserver/mi            
-I/tmp/xc/programs/Xserver/miext/shadow            
-I/tmp/xc/programs/Xserver/render -I/tmp/xc/programs/Xserver/Xext 
-I/tmp/xc/programs/Xserver/include            
-I/tmp/xc/programs/Xserver/GL/dri -I/tmp/xc/lib/GL/dri -I/tmp/xc/include 
-I/tmp/xc/include/fonts -I/tmp/xc/include/extensions 
-I/tmp/xc/exports/include/X11  -I/tmp/xc -I/tmp/xc/exports/include   -Dlinux 
-D__i386__ -D_POSIX_C_SOURCE=199309L                             
-D_POSIX_SOURCE -D_XOPEN_SOURCE              -D_BSD_SOURCE -D_SVID_SOURCE                              
-D_GNU_SOURCE                           -DSHAPE -DXINPUT -DXKB -DLBX 
-DXAPPGROUP    -DXCSECURITY -DTOGCUP    -DXF86BIGFONT -DDPMSExtension    
-DPIXPRIV -DPANORAMIX   -DRENDER -DRANDR -DGCCUSESGAS -DAVOID_GLYPHBLT 
-DPIXPRIV -DSINGLEDEPTH                               -DXFreeXDGA 
-DXvExtension                               -DXFree86LOADER  -DXFree86Server             
-DXF86VIDMODE                            -DXvMCExtension                                 
-DSMART_SCHEDULE                                -DBUILDDEBUG -DXResExtension                          
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG   -DFUNCPROTO=15 -DNARROWPROTO  
-DIN_MODULE -DXFree86Module    -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING 
-DGLX_USE_DLOPEN -DGLX_USE_MESA   -c radeon_probe.c
radeon_probe.c:95: error: `PCI_CHIP_R200_Qh' undeclared here (not in a 
function)
radeon_probe.c:95: error: initializer element is not constant
radeon_probe.c:95: error: (near initialization for `RADEONChipsets[18].token')
radeon_probe.c:95: error: initializer element is not constant
radeon_probe.c:95: error: (near initialization for `RADEONChipsets[18]')
radeon_probe.c:96: error: `PCI_CHIP_R200_Qi' undeclared here (not in a 
function)
radeon_probe.c:96: error: initializer element is not constant
radeon_probe.c:96: error: (near initialization for `RADEONChipsets[19].token')
radeon_probe.c:96: error: initializer element is not constant
radeon_probe.c:96: error: (near initialization for `RADEONChipsets[19]')
radeon_probe.c:97: error: `PCI_CHIP_R200_Qj' undeclared here (not in a 
function)
radeon_probe.c:97: error: initializer element is not constant
radeon_probe.c:97: error: (near initialization for `RADEONChipsets[20].token')
radeon_probe.c:97: error: initializer element is not constant
radeon_probe.c:97: error: (near initialization for `RADEONChipsets[20]')
radeon_probe.c:98: error: `PCI_CHIP_R200_Qk' undeclared here (not in a 
function)
radeon_probe.c:98: error: initializer element is not constant
radeon_probe.c:98: error: (near initialization for `RADEONChipsets[21].token')
radeon_probe.c:98: error: initializer element is not constant
radeon_probe.c:98: error: (near initialization for `RADEONChipsets[21]')
radeon_probe.c:99: error: `PCI_CHIP_R200_Ql' undeclared here (not in a 
function)
radeon_probe.c:99: error: initializer element is not constant
radeon_probe.c:99: error: (near initialization for `RADEONChipsets[22].token')
radeon_probe.c:99: error: initializer element is not constant
radeon_probe.c:99: error: (near initialization for `RADEONChipsets[22]')
radeon_probe.c:100: error: initializer element is not constant
radeon_probe.c:100: error: (near initialization for `RADEONChipsets[23]')
radeon_probe.c:101: error: initializer element is not constant
radeon_probe.c:101: error: (near initialization for `RADEONChipsets[24]')
radeon_probe.c:102: error: initializer element is not constant
radeon_probe.c:102: error: (near initialization for `RADEONChipsets[25]')
radeon_probe.c:103: error: initializer element is not constant
radeon_probe.c:103: error: (near initialization for `RADEONChipsets[26]')
radeon_probe.c:104: error: initializer element is not constant
radeon_probe.c:104: error: (near initialization for `RADEONChipsets[27]')
radeon_probe.c:105: error: initializer element is not constant
radeon_probe.c:105: error: (near initialization for `RADEONChipsets[28]')
radeon_probe.c:106: error: initializer element is not constant
radeon_probe.c:106: error: (near initialization for `RADEONChipsets[29]')
radeon_probe.c:107: error: initializer element is not constant
radeon_probe.c:107: error: (near initialization for `RADEONChipsets[30]')
radeon_probe.c:108: error: initializer element is not constant
radeon_probe.c:108: error: (near initialization for `RADEONChipsets[31]')
radeon_probe.c:109: error: initializer element is not constant
radeon_probe.c:109: error: (near initialization for `RADEONChipsets[32]')
radeon_probe.c:110: error: initializer element is not constant
radeon_probe.c:110: error: (near initialization for `RADEONChipsets[33]')
radeon_probe.c:111: error: initializer element is not constant
radeon_probe.c:111: error: (near initialization for `RADEONChipsets[34]')
radeon_probe.c:112: error: initializer element is not constant
radeon_probe.c:112: error: (near initialization for `RADEONChipsets[35]')
radeon_probe.c:113: error: initializer element is not constant
radeon_probe.c:113: error: (near initialization for `RADEONChipsets[36]')
radeon_probe.c:114: error: initializer element is not constant
radeon_probe.c:114: error: (near initialization for `RADEONChipsets[37]')
radeon_probe.c:115: error: initializer element is not constant
radeon_probe.c:115: error: (near initialization for `RADEONChipsets[38]')
radeon_probe.c:116: error: initializer element is not constant
radeon_probe.c:116: error: (near initialization for `RADEONChipsets[39]')
radeon_probe.c:117: error: initializer element is not constant
radeon_probe.c:117: error: (near initialization for `RADEONChipsets[40]')
radeon_probe.c:118: error: initializer element is not constant
radeon_probe.c:118: error: (near initialization for `RADEONChipsets[41]')
radeon_probe.c:119: error: initializer element is not constant
radeon_probe.c:119: error: (near initialization for `RADEONChipsets[42]')
radeon_probe.c:141: error: `PCI_CHIP_R200_Qh' undeclared here (not in a 
function)
radeon_probe.c:141: error: initializer element is not constant
radeon_probe.c:141: error: (near initialization for 
`RADEONPciChipsets[18].numChipset')
radeon_probe.c:141: error: `PCI_CHIP_R200_Qh' undeclared here (not in a 
function)
radeon_probe.c:141: error: initializer element is not constant
radeon_probe.c:141: error: (near initialization for 
`RADEONPciChipsets[18].PCIid')
radeon_probe.c:141: error: initializer element is not constant
radeon_probe.c:141: error: (near initialization for `RADEONPciChipsets[18]')
radeon_probe.c:142: error: `PCI_CHIP_R200_Qi' undeclared here (not in a 
function)
radeon_probe.c:142: error: initializer element is not constant
radeon_probe.c:142: error: (near initialization for 
`RADEONPciChipsets[19].numChipset')
radeon_probe.c:142: error: `PCI_CHIP_R200_Qi' undeclared here (not in a 
function)
radeon_probe.c:142: error: initializer element is not constant
radeon_probe.c:142: error: (near initialization for 
`RADEONPciChipsets[19].PCIid')
radeon_probe.c:142: error: initializer element is not constant
radeon_probe.c:142: error: (near initialization for `RADEONPciChipsets[19]')
radeon_probe.c:143: error: `PCI_CHIP_R200_Qj' undeclared here (not in a 
function)
radeon_probe.c:143: error: initializer element is not constant
radeon_probe.c:143: error: (near initialization for 
`RADEONPciChipsets[20].numChipset')
radeon_probe.c:143: error: `PCI_CHIP_R200_Qj' undeclared here (not in a 
function)
radeon_probe.c:143: error: initializer element is not constant
radeon_probe.c:143: error: (near initialization for 
`RADEONPciChipsets[20].PCIid')
radeon_probe.c:143: error: initializer element is not constant
radeon_probe.c:143: error: (near initialization for `RADEONPciChipsets[20]')
radeon_probe.c:144: error: `PCI_CHIP_R200_Qk' undeclared here (not in a 
function)
radeon_probe.c:144: error: initializer element is not constant
radeon_probe.c:144: error: (near initialization for 
`RADEONPciChipsets[21].numChipset')
radeon_probe.c:144: error: `PCI_CHIP_R200_Qk' undeclared here (not in a 
function)
radeon_probe.c:144: error: initializer element is not constant
radeon_probe.c:144: error: (near initialization for 
`RADEONPciChipsets[21].PCIid')
radeon_probe.c:144: error: initializer element is not constant
radeon_probe.c:144: error: (near initialization for `RADEONPciChipsets[21]')
radeon_probe.c:145: error: `PCI_CHIP_R200_Ql' undeclared here (not in a 
function)
radeon_probe.c:145: error: initializer element is not constant
radeon_probe.c:145: error: (near initialization for 
`RADEONPciChipsets[22].numChipset')
radeon_probe.c:145: error: `PCI_CHIP_R200_Ql' undeclared here (not in a 
function)
radeon_probe.c:145: error: initializer element is not constant
radeon_probe.c:145: error: (near initialization for 
`RADEONPciChipsets[22].PCIid')
radeon_probe.c:145: error: initializer element is not constant
radeon_probe.c:145: error: (near initialization for `RADEONPciChipsets[22]')
radeon_probe.c:146: error: initializer element is not constant
radeon_probe.c:146: error: (near initialization for `RADEONPciChipsets[23]')
radeon_probe.c:147: error: initializer element is not constant
radeon_probe.c:147: error: (near initialization for `RADEONPciChipsets[24]')
radeon_probe.c:148: error: initializer element is not constant
radeon_probe.c:148: error: (near initialization for `RADEONPciChipsets[25]')
radeon_probe.c:149: error: initializer element is not constant
radeon_probe.c:149: error: (near initialization for `RADEONPciChipsets[26]')
radeon_probe.c:150: error: initializer element is not constant
radeon_probe.c:150: error: (near initialization for `RADEONPciChipsets[27]')
radeon_probe.c:151: error: initializer element is not constant
radeon_probe.c:151: error: (near initialization for `RADEONPciChipsets[28]')
radeon_probe.c:152: error: initializer element is not constant
radeon_probe.c:152: error: (near initialization for `RADEONPciChipsets[29]')
radeon_probe.c:153: error: initializer element is not constant
radeon_probe.c:153: error: (near initialization for `RADEONPciChipsets[30]')
radeon_probe.c:154: error: initializer element is not constant
radeon_probe.c:154: error: (near initialization for `RADEONPciChipsets[31]')
radeon_probe.c:155: error: initializer element is not constant
radeon_probe.c:155: error: (near initialization for `RADEONPciChipsets[32]')
radeon_probe.c:156: error: initializer element is not constant
radeon_probe.c:156: error: (near initialization for `RADEONPciChipsets[33]')
radeon_probe.c:157: error: initializer element is not constant
radeon_probe.c:157: error: (near initialization for `RADEONPciChipsets[34]')
radeon_probe.c:158: error: initializer element is not constant
radeon_probe.c:158: error: (near initialization for `RADEONPciChipsets[35]')
radeon_probe.c:159: error: initializer element is not constant
radeon_probe.c:159: error: (near initialization for `RADEONPciChipsets[36]')
radeon_probe.c:160: error: initializer element is not constant
radeon_probe.c:160: error: (near initialization for `RADEONPciChipsets[37]')
radeon_probe.c:161: error: initializer element is not constant
radeon_probe.c:161: error: (near initialization for `RADEONPciChipsets[38]')
radeon_probe.c:162: error: initializer element is not constant
radeon_probe.c:162: error: (near initialization for `RADEONPciChipsets[39]')
radeon_probe.c:163: error: initializer element is not constant
radeon_probe.c:163: error: (near initialization for `RADEONPciChipsets[40]')
radeon_probe.c:164: error: initializer element is not constant
radeon_probe.c:164: error: (near initialization for `RADEONPciChipsets[41]')
radeon_probe.c:165: error: initializer element is not constant
radeon_probe.c:165: error: (near initialization for `RADEONPciChipsets[42]')
make: *** [radeon_probe.o] Error 1


Now, what do I need to do?
Vasilis