osdir.com
mailing list archive

Subject: Radeon 8500 128MB AGP -- tuner not detected when using ati.2 on top of XFree86-4.3.0.dfsg.1-8 - msg#00159

List: video.gatos.devel

Date: Prev Next Index Thread: Prev Next Index
I'm running Debian sid, trying to get TV-in to work on a Radeon 8500 128MB AGP card.
When I use XFree86-4.3.0-5 (built on 2.6.4), my tuner is detected as follows:

(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Reloading /usr/X11R6/lib/modules/libi2c.a
(II) RADEON(0): Using R200 i2c bus access method
(II) RADEON(0): I2C bus "Radeon multimedia bus" initialized.
(II) RADEON(0): *** 0x835cc20 versus 0x835cc20
(II) RADEON(0): ref=2700 M=0x0b N=0x0c timing=0x18
(II) Loading sub module "fi1236"
(II) LoadModule: "fi1236"
(II) Loading /usr/X11R6/lib/modules/multimedia/fi1236_drv.o
(II) Module fi1236: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) RADEON(0): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6.
(II) RADEON(0): Detected FI1236W device at 0xc6

But when I use the current release, XFree86-4.3.0.dfsg.1-8 (built on 2.4.26), the tuner isn't detected.
Everything else is just the same, but the last two lines above are missing.

Should I revert, or is this a bug in ati.2?

Cheers,
David

The 8500DV card has the MT2032 digital tuner, while my card has the analog FI1236W tuner.
I had intended to buy the 8500DV and for some reason thought I had it, but it's a 8500 128MB -- a faster gaming card.

http://www.anandtech.com/video/showdoc.aspx?i=1609&p=13 says,

While the vast majority of TV tuners are analog based meaning they use analog components such as resistors, inductors and capacitors to create band-pass filters that allow certain frequencies to pass through thus "tuning" to those channels, the AIW Radeon 8500DV implements virtually all of those analog components into a single piece of silicon. This gives the 8500DV a digital TV tuner (this doesn't mean it can receive HDTV channels, it just means it uses digital circuitry instead of analog) which in theory can offer better quality as a result of decreased interference and faster tuning. The quality argument is generally one that isn't noticeable because of the poor quality of cable TV however on an extremely high quality cable TV feeds you may notice a quality improvement courtesy of the silicon based tuner. While it also gives you faster tuning abilities (meaning you can surf as fast as humanly possible), ATI has always had relatively fast TV tuners on their cards, including their analog tuners.


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: [SPAM] Re: Video capture, AIW 128 PCI, KM, Avview

I turns out i needed the alsa-devel package. The alsa-devel package  with Debian Sarge did not have the file asoundlib.h which was needed. I installed alsa-dev-1.0.6 and it found alsa. If i click on avview it says "volume unsupported" but sound recording works now. Will work on KM when i get more time. James > james wrote: > >I am trying to get video capture working using > >Sarge on a p4 2 GHZ / w 1GB ram > >ATI All in wonder PCI 128 > >GCC 2.95 (degraded from 3.3.3), > >Custom 2.6.5 i686 kernel, Compiled with GCC-2.95 > >ALSA 1.04 (Came with kernel) FFMPEG 0.4.8 , CVS KM, CVS avview. > >Tcl/Tk 8.4.6 , Libzvbi .0.2.8, Autoconf 2.59 , automake 1.9.2, LIRC .0.6.2 > > > >problems are > >The Avview config. script cant find ALSA. > >The error message was ** Avview requires ALSA version 0.9.x > >Maybe it wont work with 1.04 ?. > > Creating a symlink in /etc/alsa/modutils from 1.0 to a file representing > my audio card seems to fixed that for me. > I don't remember though if I did anything else. > > Igor > > >If it will, where is it looking ?. Debian puts stuff in weird palces. > >Else it works. Can see video, capture snapshots. > > > >KM compiled with allot of errors. > >I renamed the 2.6 makefile. > >Did the make -C /usr/src/kernel-source-2.6.5 SUBDIRS=$PWD modules > > The error messages are at the end of file. > > > >Loaded the KM modules anyway. Complained about tainted kernel. > > Avview found KM. Could capture video (no audio) but Avview seg > > faulted and > >crashed when stop was pressed no matter what quality setting i use. > > > > v4l_encoding pid 5999 > > v4l_reader_thread finished > > Video encoding finished > > Segmentation fault > > james@jameslinux:~/avview$ > > > >. The video was saved, but slightly jumpy, not surprised. Could be my > > player XINE. Top reports 32% CPU free when recording. Unless Natulus > > file manager is open then FAMD eats the 32% and top shows 00. > > > >Tried to compile KM with GCC-3.3. Had to change to root .Avview found it > > but crashed. Had to force quit avview. > > > > > > > >Any other suggestions ? > > > >James > > > > > >The KM error message follows. > >*** Warning: Overriding SUBDIRS on the command line can cause > >*** inconsistencies > >make[1]: `arch/i386/kernel/asm-offsets.s' is up to date. > > CC [M] /home/james/km/km_api.o > >/home/james/km/km_api.c: In function `km_fo_control_perform_command': > >/home/james/km/km_api.c:395: warning: assignment discards qualifiers from > >pointer target type > >/home/james/km/km_api.c: At top level: > >/home/james/km/km_api.c:584: warning: static declaration for `init_module' > >follows non-static > >/home/james/km/km_api.c: In function `init_module': > >/home/james/km/km_api.c:586: warning: unused variable `i' > > CC [M] /home/james/km/km_api_data.o > >/home/james/km/km_api_data.c: In function `km_fo_data_open': > >/home/james/km/km_api_data.c:207: warning: unused variable `kdu' > >/home/james/km/km_api_data.c: In function `km_fo_data_release': > >/home/james/km/km_api_data.c:228: warning: unused variable `kdu' > >/home/james/km/km_api_data.c: In function `km_dvb_mmap': > >/home/james/km/km_api_data.c:274: warning: passing arg 1 of `kvirt_to_pa' > >makes integer from pointer without a cast > > CC [M] /home/james/km/km_memory.o > > CC [M] /home/james/km/km.o > >In file included from /home/james/km/km.c:39: > >/home/james/km/km.h:175: warning: `KM_CHECKPOINT' redefined > >/home/james/km/km_api.h:156: warning: this is the location of the previous > >definition > >/home/james/km/km.c: In function `km_probe': > >/home/james/km/km.c:732: warning: assignment from incompatible pointer > > type /home/james/km/km.c:733: warning: assignment from incompatible > > pointer type /home/james/km/km.c:746: warning: assignment from > > incompatible pointer type /home/james/km/km.c:747: warning: assignment > > from incompatible pointer type CC [M] /home/james/km/km_v4l.o > >In file included from /home/james/km/km_v4l.c:27: > >/home/james/km/km.h:175: warning: `KM_CHECKPOINT' redefined > >/home/james/km/km_api.h:156: warning: this is the location of the previous > >definition > >/home/james/km/km_v4l.c: In function `km_v4l_mmap': > >/home/james/km/km_v4l.c:182: warning: unused variable `kdufpd' > >/home/james/km/km_v4l.c:181: warning: unused variable `pos' > >/home/james/km/km_v4l.c:181: warning: unused variable `page' > > CC [M] /home/james/km/radeon.o > >In file included from /home/james/km/radeon.c:35: > >/home/james/km/km.h:175: warning: `KM_CHECKPOINT' redefined > >/home/james/km/km_api.h:156: warning: this is the location of the previous > >definition > >/home/james/km/radeon.c: In function `radeon_check_mc_settings': > >/home/james/km/radeon.c:81: warning: unused variable `new_mc_agp_location' > >/home/james/km/radeon.c: In function `radeon_start_request_transfer': > >/home/james/km/radeon.c:350: warning: long unsigned int format, u32 arg > > (arg 2) > >/home/james/km/radeon.c: In function `radeon_schedule_request': > >/home/james/km/radeon.c:390: warning: passing arg 5 of > >`km_add_transfer_request' from incompatible pointer type > >/home/james/km/radeon.c: In function `radeon_verify_page': > >/home/james/km/radeon.c:579: warning: unsigned int format, long unsigned > > int arg (arg 2) > >/home/james/km/radeon.c:583: warning: unsigned int format, long unsigned > > int arg (arg 2) > > CC [M] /home/james/km/mach64.o > >In file included from /home/james/km/mach64.c:34: > >/home/james/km/km.h:175: warning: `KM_CHECKPOINT' redefined > >/home/james/km/km_api.h:156: warning: this is the location of the previous > >definition > >/home/james/km/mach64.c: In function `mach64_start_request_transfer': > >/home/james/km/mach64.c:135: warning: unused variable `status' > >/home/james/km/mach64.c: In function `mach64_schedule_request': > >/home/james/km/mach64.c:169: warning: passing arg 5 of > >`km_add_transfer_request' from incompatible pointer type > >/home/james/km/mach64.c: In function `mach64_km_irq': > >/home/james/km/mach64.c:196: warning: unsigned int format, long unsigned > > int arg (arg 2) > >/home/james/km/mach64.c:214: warning: `return' with no value, in function > >returning non-void > >/home/james/km/mach64.c:175: warning: unused variable `mask' > >/home/james/km/mach64.c:175: warning: unused variable `status_cap' > > CC [M] /home/james/km/rage128.o > >In file included from /home/james/km/rage128.c:34: > >/home/james/km/km.h:175: warning: `KM_CHECKPOINT' redefined > >/home/james/km/km_api.h:156: warning: this is the location of the previous > >definition > >/home/james/km/rage128.c: In function `rage128_start_request_transfer': > >/home/james/km/rage128.c:145: warning: unused variable `status' > >/home/james/km/rage128.c: In function `rage128_schedule_request': > >/home/james/km/rage128.c:179: warning: passing arg 5 of > >`km_add_transfer_request' from incompatible pointer type > > LD [M] /home/james/km/km_drv.o > > LD [M] /home/james/km/km_api_drv.o > > Building modules, stage 2. > > MODPOST > > CC /home/james/km/km_api_drv.mod.o > > LD [M] /home/james/km/km_api_drv.ko > > CC /home/james/km/km_drv.mod.o > > LD [M] /home/james/km/km_drv.ko > >make: Leaving directory `/usr/src/kernel-source-2.6.5' > > > > > >------------------------------------------------------- > >This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > >Use IT products in your business? Tell us what you think of them. Give us > >Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > > more http://productguide.itmanagersjournal.com/guidepromo.tmpl > >_______________________________________________ > >Gatos-devel mailing list > >Gatos-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > >https://lists.sourceforge.net/lists/listinfo/gatos-devel > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Gatos-devel mailing list > Gatos-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/gatos-devel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Next Message by Date: click to view message preview

Re: Radeon 8500 128MB AGP -- tuner not detected when using ati.2 on top of XFree86-4.3.0.dfsg.1-8

I've reverted to XFree86-4.3.0-5 and the chip gets detected as before -- but I noticed that even the XFree86-4.3.0.dfsg.1-8 has the following evidence of detection: (II) Loading sub module "saa7114" (II) LoadModule: "saa7114" (II) Loading /usr/X11R6/lib/modules/multimedia/saa7114_drv.o (II) Module saa7114: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): 0x55 0xaa (II) RADEON(0): video decoder type is 0x6b6c versus 0x6b6c (II) RADEON(0): Tuner is on port 0 (II) RADEON(0): Composite connector is port 2 (II) RADEON(0): SVideo connector is port 6 (II) RADEON(0): Rage Theatre: Connectors (detected): tuner=0, composite=2, svideo=6 (II) RADEON(0): RageTheatre: Connectors (using): tuner=0, composite=2, svideo=6 (II) RADEON(0): video decoder type used: 0x0006 So "Tuner is on port 0" is still detected. I guess I drop my question until further testing. Cheers, Dave David Liontooth wrote: I'm running Debian sid, trying to get TV-in to work on a Radeon 8500 128MB AGP card. When I use XFree86-4.3.0-5 (built on 2.6.4), my tuner is detected as follows: (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Reloading /usr/X11R6/lib/modules/libi2c.a (II) RADEON(0): Using R200 i2c bus access method (II) RADEON(0): I2C bus "Radeon multimedia bus" initialized. (II) RADEON(0): *** 0x835cc20 versus 0x835cc20 (II) RADEON(0): ref=2700 M=0x0b N=0x0c timing=0x18 (II) Loading sub module "fi1236" (II) LoadModule: "fi1236" (II) Loading /usr/X11R6/lib/modules/multimedia/fi1236_drv.o (II) Module fi1236: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6. (II) RADEON(0): Detected FI1236W device at 0xc6 But when I use the current release, XFree86-4.3.0.dfsg.1-8 (built on 2.4.26), the tuner isn't detected. Everything else is just the same, but the last two lines above are missing. Should I revert, or is this a bug in ati.2? Cheers, David The 8500DV card has the MT2032 digital tuner, while my card has the analog FI1236W tuner. I had intended to buy the 8500DV and for some reason thought I had it, but it's a 8500 128MB -- a faster gaming card. http://www.anandtech.com/video/showdoc.aspx?i=1609&p=13 says, While the vast majority of TV tuners are analog based meaning they use analog components such as resistors, inductors and capacitors to create band-pass filters that allow certain frequencies to pass through thus "tuning" to those channels, the AIW Radeon 8500DV implements virtually all of those analog components into a single piece of silicon. This gives the 8500DV a digital TV tuner (this doesn't mean it can receive HDTV channels, it just means it uses digital circuitry instead of analog) which in theory can offer better quality as a result of decreased interference and faster tuning. The quality argument is generally one that isn't noticeable because of the poor quality of cable TV however on an extremely high quality cable TV feeds you may notice a quality improvement courtesy of the silicon based tuner. While it also gives you faster tuning abilities (meaning you can surf as fast as humanly possible), ATI has always had relatively fast TV tuners on their cards, including their analog tuners. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Gatos-devel mailing list Gatos-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/gatos-devel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Previous Message by Thread: click to view message preview

Re: Is dri required for ati.2?

On Mon, 18 Oct 2004, David Liontooth wrote: I just installed the ati.2 tarball on a Debian sid XFree 4.3.0 system to get TV-in on a Radeon AIW 8500DV. Question: do I need DRI for this to work? No. Just install AVview and check whether it works. best Vladimir Dergachev PS You don't absolutely need km either. Details below. I get this in the X11 log: (II) RADEON(0): VBI data capture is only supported for NTSC Tuner at the moment (II) RADEON(0): VIDEO BIOS TABLE OFFSETS: bios_header=0x0118 mm_table=0x048e (II) RADEON(0): MM_TABLE: 01-0c-0f-18-06-80-2b-66-02-01-00-06-00-07 (II) Loading sub module "theatre" (II) LoadModule: "theatre" (II) Loading /usr/X11R6/lib/modules/multimedia/theatre_drv.o (II) Module theatre: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): No response from device 0 on VIP bus (II) RADEON(0): Device 1 on VIP bus ids as 0x4d541002 (II) RADEON(0): No response from device 2 on VIP bus (II) RADEON(0): No response from device 3 on VIP bus (II) RADEON(0): Detected Rage Theatre as device 1 on VIP bus with id 0x4d541002 (II) RADEON(0): Detected Rage Theatre revision 00000003 So the Rage Theatre chip is detected, it goes through a slew of registers, everything looks fine, and then: (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Reloading /usr/X11R6/lib/modules/libi2c.a (II) RADEON(0): Using R200 i2c bus access method (II) RADEON(0): I2C bus "Radeon multimedia bus" initialized. (II) RADEON(0): *** 0x835cc20 versus 0x835cc20 (II) RADEON(0): ref=2700 M=0x0b N=0x0c timing=0x18 (II) Loading sub module "fi1236" (II) LoadModule: "fi1236" (II) Loading /usr/X11R6/lib/modules/multimedia/fi1236_drv.o (II) Module fi1236: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6. (II) RADEON(0): Detected FI1236W device at 0xc6 OK, so it finds the tuner. (II) Loading sub module "msp3430" (II) LoadModule: "msp3430" (II) Loading /usr/X11R6/lib/modules/multimedia/msp3430_drv.o (II) Module msp3430: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): Found MSP3445G, rom version 0x48, chip_id=0x072d (II) RADEON(0): I2C device "Radeon multimedia bus:MSP34xx" registered at address 0x80. (II) RADEON(0): Detected MSP3430 at 0x80 (II) Loading sub module "saa7114" (II) LoadModule: "saa7114" (II) Loading /usr/X11R6/lib/modules/multimedia/saa7114_drv.o (II) Module saa7114: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 Looks good, the v4l capture device is in place. (II) RADEON(0): 0x55 0xaa (II) RADEON(0): video decoder type is 0x6b6c versus 0x6b6c (II) RADEON(0): Tuner is on port 0 (II) RADEON(0): Composite connector is port 2 (II) RADEON(0): SVideo connector is port 6 (II) RADEON(0): Rage Theatre: Connectors (detected): tuner=0, composite=2, svideo=6 (II) RADEON(0): RageTheatre: Connectors (using): tuner=0, composite=2, svideo=6 (II) RADEON(0): video decoder type used: 0x0006 (II) RADEON(0): Rage Theatre setting standard 0x0000 (II) RADEON(0): Rage Theatre Checkpoint 1 (II) RADEON(0): Rage Theatre Checkpoint 2, counter=0 (65) (II) RADEON(0): Rage Theatre Checkpoint 3 (II) RADEON(0): Rage Theatre Checkpoint 4 i=90945 (II) RADEON(0): Rage Theatre Checkpoint 5 counter=22 (11) (II) RADEON(0): Rage Theatre setting standard 0x0000 So this all looks good -- but when I use AVView, it doesn't find a capture device. motv complains there is no /dev/vbi device -- I checked that the device points exist. DRI isn't working -- but should this matter? (II) RADEON(0): Direct rendering disabled [dri] radeon.o kernel module version is 1.11.0 but version 1.100.0 or newer is needed. I tried to compile but failed in two ways -- from one machine I had oodles of errors, from the other it couldn't find the kernel tree (I don't know why -- the kernel is built locally in both cases). 2.6.8 kernel, Debian sid flavor. All I need is tv-in -- what could be the problem? Cheers, David ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Gatos-devel mailing list Gatos-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/gatos-devel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Next Message by Thread: click to view message preview

Re: Radeon 8500 128MB AGP -- tuner not detected when using ati.2 on top of XFree86-4.3.0.dfsg.1-8

I've reverted to XFree86-4.3.0-5 and the chip gets detected as before -- but I noticed that even the XFree86-4.3.0.dfsg.1-8 has the following evidence of detection: (II) Loading sub module "saa7114" (II) LoadModule: "saa7114" (II) Loading /usr/X11R6/lib/modules/multimedia/saa7114_drv.o (II) Module saa7114: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): 0x55 0xaa (II) RADEON(0): video decoder type is 0x6b6c versus 0x6b6c (II) RADEON(0): Tuner is on port 0 (II) RADEON(0): Composite connector is port 2 (II) RADEON(0): SVideo connector is port 6 (II) RADEON(0): Rage Theatre: Connectors (detected): tuner=0, composite=2, svideo=6 (II) RADEON(0): RageTheatre: Connectors (using): tuner=0, composite=2, svideo=6 (II) RADEON(0): video decoder type used: 0x0006 So "Tuner is on port 0" is still detected. I guess I drop my question until further testing. Cheers, Dave David Liontooth wrote: I'm running Debian sid, trying to get TV-in to work on a Radeon 8500 128MB AGP card. When I use XFree86-4.3.0-5 (built on 2.6.4), my tuner is detected as follows: (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Reloading /usr/X11R6/lib/modules/libi2c.a (II) RADEON(0): Using R200 i2c bus access method (II) RADEON(0): I2C bus "Radeon multimedia bus" initialized. (II) RADEON(0): *** 0x835cc20 versus 0x835cc20 (II) RADEON(0): ref=2700 M=0x0b N=0x0c timing=0x18 (II) Loading sub module "fi1236" (II) LoadModule: "fi1236" (II) Loading /usr/X11R6/lib/modules/multimedia/fi1236_drv.o (II) Module fi1236: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) RADEON(0): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC6. (II) RADEON(0): Detected FI1236W device at 0xc6 But when I use the current release, XFree86-4.3.0.dfsg.1-8 (built on 2.4.26), the tuner isn't detected. Everything else is just the same, but the last two lines above are missing. Should I revert, or is this a bug in ati.2? Cheers, David The 8500DV card has the MT2032 digital tuner, while my card has the analog FI1236W tuner. I had intended to buy the 8500DV and for some reason thought I had it, but it's a 8500 128MB -- a faster gaming card. http://www.anandtech.com/video/showdoc.aspx?i=1609&p=13 says, While the vast majority of TV tuners are analog based meaning they use analog components such as resistors, inductors and capacitors to create band-pass filters that allow certain frequencies to pass through thus "tuning" to those channels, the AIW Radeon 8500DV implements virtually all of those analog components into a single piece of silicon. This gives the 8500DV a digital TV tuner (this doesn't mean it can receive HDTV channels, it just means it uses digital circuitry instead of analog) which in theory can offer better quality as a result of decreased interference and faster tuning. The quality argument is generally one that isn't noticeable because of the poor quality of cable TV however on an extremely high quality cable TV feeds you may notice a quality improvement courtesy of the silicon based tuner. While it also gives you faster tuning abilities (meaning you can surf as fast as humanly possible), ATI has always had relatively fast TV tuners on their cards, including their analog tuners. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Gatos-devel mailing list Gatos-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/gatos-devel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by