gatos-devel Mailing List for GATOS

> Hello,
>=0D
> I would like to know the status of the development for the RT200 ?
> I can help with testing or sending any relevant info.
> I own an ati aiw 9800SE.
>=0D
>=0D
> Reagrds,


**** DISCLAIMER ****
"This e-mail and any attachments thereto may contain information
which is confidential and/or protected by intellectual property
rights and are intended for the sole use of the recipient(s)named above.
Any use of the information contained herein (including, but not limited to,
total or partial reproduction, communication or distribution in any form)
by persons other than the designated recipient(s) is prohibited.
If you have received this e-mail in error, please notify the sender either
by telephone or by e-mail and delete the material from any computer.
Thank you for your cooperation."

On Sun, 2004-08-29 at 22:30 +0200, Yann Rouillard wrote:
> > 
> > This patch from last December that was never applied is supposed to fix
> > that problem.  I have no idea if it still works or not, but I think it
> > should get you on the right track at least.
> > 
> 
> Thanks ! This patch worked perfectly for me.
> Any reason this patch can't be applied on the CVS ?

I don't know.  I'll cast a vote for doing that though. I'm going to take
a shot at compiling Gatos against Xorg soon, and that would save me a
patch.  :)

I asked about that very question last January, and nobody replied.

--
Curtis Magyar

> 
> This patch from last December that was never applied is supposed to fix
> that problem.  I have no idea if it still works or not, but I think it
> should get you on the right track at least.
> 

Thanks ! This patch worked perfectly for me.
Any reason this patch can't be applied on the CVS ?

Yann

On Sun, 2004-08-29 at 13:26 +0200, Yann Rouillard wrote:
> I would like to know if someone found a solution to activate the tv 
> output with only the tv attached.
> 
> Yann


This patch from last December that was never applied is supposed to fix
that problem.  I have no idea if it still works or not, but I think it
should get you on the right track at least.

http://sourceforge.net/mailarchive/message.php?msg_id=6821588

Hopefully it will not be forgotten about, its a very useful feature
IMHO.

--
Curtis Magyar


> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

Hi,

I am trying to use my radeon 7000 VE with tv output only.
I compiled and installed ati.2 tv_output branch on my Debian unstable
(Xfree 4.3.0), installation went fine but when trying to start X I have
the following error message:

(EE) RADEON(0): No monitor detected!!!

After having read the message:
http://sourceforge.net/mailarchive/message.php?msg_id=7047025
I solved the problem by connecting my standard monitor at boot time but 
I would like to know if someone found a solution to activate the tv 
output with only the tv attached.

Yann

On Fri 27 August 2004 21:30, Hugues Belanger wrote:
> Ok This is just driving me nuts now.
>
> I'm trying to get my TVout to work properly and I can't seem to
> get things right. I'm terrible configuring X and need all the
> help I can get.
>
> I downloaded the latest ati.2 binary drivers and now my tvout
> seems to work, well I get garbel out of sync screen.
> I'm trying to set two resolution on for my monitor and one for my
> 40" rca NTCS  Tv.  Please let me know what I'm doing wrong.

Are you sure you are using the tv_output branch? Which version of X=20
do you have? SourceForge seems a bit dead right now so I can't=20
check, but I'm not sure there are any tv_output binaries.

As for your config file, the tv_output branch currently 
supports 800x600, as the README says. Try using that instead of=20
640x480.

Lourens
--=20
GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key

On Fri, 27 Aug 2004, Bryan D. Stine wrote:

> I tried the diff plan originally, but it doesn't apply cleanly. It produced an
> ~80KB radeon_video.c.rej and in my attempts to merge the stuff manually, I
> couldn't get the driver to run without segfaulting, which seems to happen
> right after finding the tuner. My knowledge of the code involved is next to
> nothing, so I don't really know where to start looking for problems. It could
> just be a null pointer somewhere or it could be a big conflict with some new
> code introduced in the xorg snapshot.

It appears there have been some changes due to inclusion of MergedFB code.
If you have a lot of patience you can just wait for most of GATOS driver 
stuff to make it into X.Org CVS.

I have applied for write access and hopefully it would be there in a few 
months. Just to be clear - it is not meant to be included in the upcoming 
release.

                           best

                             Vladimir Dergachev

>
> On Wednesday August 25, 2004 8:05 pm, Vladimir Dergachev wrote:
>> Hi Bryan,
>>
>>    Thank you for the patch :)
>>
>>    As you note the better solution is to merge with latest X.org code.
>> Could you try making a diff as follows:
>>
>>      cd ati.4.4.0
>>      cvs diff -u -r orig -r HEAD
>>
>> This will produce a diff of GATOS-specific changes, perhaps they will
>> apply cleanly to 6.7.99 code ?
>>
>>                      thank you !
>>
>>                            Vladimir Dergachev
>>
>> On Sun, 22 Aug 2004, Bryan D. Stine wrote:
>>> Hello everyone.
>>>
>>> I've attached a patch that allows GATOS to build against the
>>> in-development Xorg. This is tested against 6.7.99.2 (specifically, the
>>> SDK) and seems to require drm.h (from the extras/drm shared stuff) in one
>>> of the include dirs. As you can see, this does not merge the ati changes
>>> from 6.7.99 in, but only allows it to build. In my basic testing, it
>>> appears to work. The better solution is to merge the GATOS stuff into the
>>> upcoming release, though, so I consider this a temporary solution.
>>>
>>> (patch -p1 in the gatos src dir)
>>>
>>> --
>>> Bryan D. Stine
>>> <bat...@ge...>
>>>
>>> "Wade Boggs...goes down smooth."
>>> --Hank Aaron XXIV, 998 years from now
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
>> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
>> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
>> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
>> _______________________________________________
>> Gatos-devel mailing list
>> Gat...@li...
>> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
> -- 
> Bryan D. Stine
> <bat...@ge...>
>
> "Wade Boggs...goes down smooth."
> --Hank Aaron XXIV, 998 years from now
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

I tried the diff plan originally, but it doesn't apply cleanly. It produced an 
~80KB radeon_video.c.rej and in my attempts to merge the stuff manually, I 
couldn't get the driver to run without segfaulting, which seems to happen 
right after finding the tuner. My knowledge of the code involved is next to 
nothing, so I don't really know where to start looking for problems. It could 
just be a null pointer somewhere or it could be a big conflict with some new 
code introduced in the xorg snapshot.

On Wednesday August 25, 2004 8:05 pm, Vladimir Dergachev wrote:
> Hi Bryan,
>
>    Thank you for the patch :)
>
>    As you note the better solution is to merge with latest X.org code.
> Could you try making a diff as follows:
>
>      cd ati.4.4.0
>      cvs diff -u -r orig -r HEAD
>
> This will produce a diff of GATOS-specific changes, perhaps they will
> apply cleanly to 6.7.99 code ?
>
>                      thank you !
>
>                            Vladimir Dergachev
>
> On Sun, 22 Aug 2004, Bryan D. Stine wrote:
> > Hello everyone.
> >
> > I've attached a patch that allows GATOS to build against the
> > in-development Xorg. This is tested against 6.7.99.2 (specifically, the
> > SDK) and seems to require drm.h (from the extras/drm shared stuff) in one
> > of the include dirs. As you can see, this does not merge the ati changes
> > from 6.7.99 in, but only allows it to build. In my basic testing, it
> > appears to work. The better solution is to merge the GATOS stuff into the
> > upcoming release, though, so I consider this a temporary solution.
> >
> > (patch -p1 in the gatos src dir)
> >
> > --
> > Bryan D. Stine
> > <bat...@ge...>
> >
> > "Wade Boggs...goes down smooth."
> > --Hank Aaron XXIV, 998 years from now
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel

-- 
Bryan D. Stine
<bat...@ge...>

"Wade Boggs...goes down smooth."
 --Hank Aaron XXIV, 998 years from now

Ok This is just driving me nuts now.

I'm trying to get my TVout to work properly and I can't seem to get 
things right. I'm terrible configuring X and need all the help I can get.

I downloaded the latest ati.2 binary drivers and now my tvout seems to 
work, well I get garbel out of sync screen.
I'm trying to set two resolution on for my monitor and one for my 40" 
rca NTCS  Tv.  Please let me know what I'm doing wrong.

Thanks
Hugues Belanger

I've been banging my head against the wall with this one -- I am pretty
sure this should work based on all the docs I've been reading.

What I have:
  Fedora Core 1 (rolled my own 2.6.8.1 kernel)
          ATI [mach*|Rage*|Radeon*] Support: NO
          ATI Chipset Support: YES
          /dev/agpgart: YES
          DRM: YES
  XFree86 v4.3.0 (rolled my own)
  Latest CVS tv_output branch of ati.2
  ATI 3D Rage II+ 215GTB [Mach64 GTB] (pci)
  ATI Rage XL  (on the mobo, not being used)
  Pertinant part of X config file:
    Section "Device"
    Driver "ati"
    VendorName "Videocard vendor"
    BoardName "ATI Mach 64 3D RAGE II+DVD"
    Option "TVOutput" "NTSC"

The Problem:
   VGA display works fine (in text and in X)
   S-Video output works fine in text mode
   S-Video displays all white after running "X"
        *completely white TV screen.
   Shutting down X makes the TV screen function fine again.

What I've Tried:
   Fiddled with composite_sync - no difference
   Changed to "Driver "vesa"" - TV-Out works perfect
   Changed back to "Driver "ati" - see problem above*

   Deleted all the hw/drivers/ati files and replaced them
     with the ati.2 files (the tv_output branch).  No difference.

Sidenote:
    My nerdy roommate is a deadbeat and giving me no support on this one
and I'm all out of ideas.

But we still need a branch in Xorg to start with ;-)

> -----Original Message-----
> From: Lourens Veen [mailto:lo...@ra...] 
> Sent: Thursday, August 26, 2004 18:32
> To: Shawn Starr; vo...@mi...; 
> gat...@li...
> Cc: xo...@fr...
> Subject: Re: [GATOS]Getting GATOS branch created on Xorg
> 
> 
> On Fri 20 August 2004 03:54, Shawn Starr wrote:
> > It would be best to discuss this so that it gets more visibility.
> >
> > What does everyone think?
> >
> > Shawn.
> >
> > On Tue, 17 Aug 2004, Shawn Starr wrote:
> > > Where would the latest code base be available? Would you 
> want write 
> > > access
> >
> > to
> >
> > > CVS? Its possible you'd get a branch for GATOS and then when its 
> > > stablized within Xorg be merged into -HEAD.
> >
> > Good question. The thing is I had very little time for development 
> > lately so perhaps this is best asked of other GATOS developers.
> >
> > So, I think it would make sense to put this question to the mailing 
> > list - it might be better for everyone if GATOS development 
> switches 
> > to X.Org CVS, at least as far as driver work is concerned.
> >
> > What is your opinion ?
> 
> I don't think my opinion should carry much weight, given my newness 
> to Gatos, but you asked for an opinion, so you get one :-).
> 
> I think this is a good first step on the road to merging Gatos back 
> into Xorg. The whole idea for Gatos was to develop TV-in support 
> separately from XFree86, and then fold it back into XFree86 when it 
> was ready. Unfortunately this last thing never happened, because of 
> the closed development model of XFree86. Now that we have Xorg, we 
> have an actual chance of eventually merging Gatos back in.
> 
> What this project needs is more users to test and give feedback, and 
> more developers to write code and fix bugs (and more docs from ATI< 
> but well...). Merging it back into Xorg eventually can give us that 
> extra exposure and move the project forward faster.
> 
> So, as a first step towards that goal, switching to Xorg CVS may be 
> a good idea. It might also be a bit more reliable :-). Personally, 
> I'd be happy to send my patches to a list for someone else to 
> commit. I don't feel at home enough to be checking things in 
> without outside review anyway.
> 
> My 2 eurocents (soon to be Swiss centimes, for three months at 
> least).
> 
> Lourens
> -- 
> GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key
> 

On Fri 20 August 2004 03:54, Shawn Starr wrote:
> It would be best to discuss this so that it gets more visibility.
>
> What does everyone think?
>
> Shawn.
>
> On Tue, 17 Aug 2004, Shawn Starr wrote:
> > Where would the latest code base be available? Would you want
> > write access
>
> to
>
> > CVS? Its possible you'd get a branch for GATOS and then when
> > its stablized within Xorg be merged into -HEAD.
>
> Good question. The thing is I had very little time for
> development lately so perhaps this is best asked of other GATOS
> developers.
>
> So, I think it would make sense to put this question to the
> mailing list - it might be better for everyone if GATOS
> development switches to X.Org CVS, at least as far as driver work
> is concerned.
>
> What is your opinion ?

I don't think my opinion should carry much weight, given my newness=20
to Gatos, but you asked for an opinion, so you get one :-).

I think this is a good first step on the road to merging Gatos back=20
into Xorg. The whole idea for Gatos was to develop TV-in support=20
separately from XFree86, and then fold it back into XFree86 when it=20
was ready. Unfortunately this last thing never happened, because of=20
the closed development model of XFree86. Now that we have Xorg, we=20
have an actual chance of eventually merging Gatos back in.

What this project needs is more users to test and give feedback, and=20
more developers to write code and fix bugs (and more docs from ATI<=20
but well...). Merging it back into Xorg eventually can give us that=20
extra exposure and move the project forward faster.

So, as a first step towards that goal, switching to Xorg CVS may be=20
a good idea. It might also be a bit more reliable :-). Personally,=20
I'd be happy to send my patches to a list for someone else to=20
commit. I don't feel at home enough to be checking things in=20
without outside review anyway.

My 2 eurocents (soon to be Swiss centimes, for three months at=20
least).

Lourens
--=20
GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key

On Wed, 25 Aug 2004 em...@di... wrote:

> Vladimir Dergachev wrote:
>> You have likely pinned this down - the BIOS is not being found on your
>> ATI card.
>>
>> Does the stock Xorg ATI driver work for you ? If yes, could you compare
>> the portions of radeon_driver.c that detect BIOS in both drivers ?
>
> yes, Xorg works fine... I compared the RADEONGetBIOSParameters()
> function.. there is no difference between both files...
>
> I don't know why this is happening.
>
> The only difference in the file related to BIOS (as far as I founded) is
> in the AGP/PCI detection.. Xorg use the "PCI config registers", and
> GATOS (apparently) use BIOS. There is a comment in GATOS ATI 4.4.0
> drivers which say:
>>     /* There are signatures in BIOS and PCI-SSID for a PCI card, but
>>      * they are not very reliable.  Following detection method works for
>>      * all cards tested so far.  Note, checking AGP_ENABLE bit after
>>      * drmAgpEnable call can also give the correct result.  However,
>>      * calling drmAgpEnable on a PCI card can cause some strange lockup
>>      * when the server restarts next time.
>>      */
>
>
> Ah!, my AIW is a PCI card..

I suggest you use X.org variation then. When GATOS drivers will be ported 
to the upcoming release of X.org this portion will not be retained as it 
is not GATOS-specific.

                           best

                             Vladimir Dergachev

>
> Thanks.
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Vladimir Dergachev wrote:
> You have likely pinned this down - the BIOS is not being found on your
> ATI card.
>
> Does the stock Xorg ATI driver work for you ? If yes, could you compare
> the portions of radeon_driver.c that detect BIOS in both drivers ?

yes, Xorg works fine... I compared the RADEONGetBIOSParameters()
function.. there is no difference between both files...

I don't know why this is happening.

The only difference in the file related to BIOS (as far as I founded) is
in the AGP/PCI detection.. Xorg use the "PCI config registers", and
GATOS (apparently) use BIOS. There is a comment in GATOS ATI 4.4.0
drivers which say:
>     /* There are signatures in BIOS and PCI-SSID for a PCI card, but
>      * they are not very reliable.  Following detection method works for
>      * all cards tested so far.  Note, checking AGP_ENABLE bit after
>      * drmAgpEnable call can also give the correct result.  However,
>      * calling drmAgpEnable on a PCI card can cause some strange lockup
>      * when the server restarts next time.
>      */


Ah!, my AIW is a PCI card..

Thanks.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Merged !

        Thank you very much !

                       Vladimir Dergachev

On Wed, 16 Jun 2004, Antti Ajanki wrote:

> Hi!
>
> Now that I built an IR-receiver, I just had to get LIRC support for
> avview and here it is ;-)
>
> After patching the sources run
>
>  aclocal && autoconf && autoheader && automake
>
> to update configure and Makefile.
>
>
> A couple of notes about the implementation:
>
> * Support is implemented using liblirc_client meaning that actions for
> remote control buttons are defined in ~/.lircrc file (see LIRC
> documentation for details). The prog name variable needed for the file
> is - supprise, supprise - 'avview'. The config strings avview
> currently understands are
>
>    fullscreen         - toggles fullscreen mode
>    next_channel val   - switches between favourite channels. val is
>                         the number of channels to skip, can be negative
>    mute               - toggle mute
>    exit               - exits
>    volume val         - changes volume by amount val
>    next_control val   - switches on-screen control. val is the number
>                         of controls to skip, can be negative
>    change_control val - changes the value of on-screen control by
>                         amount val.
>    next_encoding      - switches xv port encoding (PAL, NTSC, ...)
>    remote_power_off   - exits or toggles screensaver
>    channel val        - select channel val. val is channel name
>                         (e.g. E5)
>
> * Additional config file(s) can be loaded with command line parameter
> --lircconf. The LIRC documentation seems to imply that multiple config
> files can be loaded at the same time, but at least for me only the
> last one loaded is actually used. Nevertheless, you can test whether
> or not your version of LIRC supports multiple config files by giving
> them as comma-separated list (--lircconf=file1,file2,file3).
>
> * Currently only single-digit channel numbers are understand by the
> program, meaning that you can't select channel 11 with remote by
> pressing button 1 twice.
>
> I guess that was it. Enjoy!
>
> -- 
> Antti Ajanki
>
>
>
> diff -u avview.cvs/Makefile.am avview/Makefile.am
> --- avview.cvs/Makefile.am	2003-12-20 20:34:59.000000000 +0200
> +++ avview/Makefile.am	2004-06-14 21:37:45.000000000 +0300
> @@ -10,7 +10,7 @@
> avview_shell_SOURCES = xv.c frequencies.c xmisc.c string_cache.c v4l.c
> formats.c ffmpeg.c \
> 	alsa.c packet_stream.c linux.c main.c alsa.h config.h ffmpeg.h
> formats.h \
> 	frequencies.h global.h linux.h packet_stream.h string_cache.h
> v4l.h  \
> -	xmisc.h xv.h vbi.c vbi.h
> +	xmisc.h xv.h vbi.c vbi.h lirc.c lirc.h
> avview_shell_LDFLAGS = @TCL_LIB_SPEC@ @TK_LIB_SPEC@ @TK_XLIBSW@
>
> scpdir = @datadir@/AVview
> @@ -20,10 +20,10 @@
> nodist_scp_DATA = start_avview.desktop
>
> dist_scp_DATA = alsa.scp bindings.scp ffmpeg.scp themes.scp
> video_device.scp \
> -	alsa_mixer.scp channel_scan.scp  km.scp tree.scp xv.scp	vbi.scp \
> -	avview.scp diag.scp setup.scp v4l.scp xmisc.scp avview.modmap \
> -	avview-16x16.ppm avview-control-16x16.ppm avview-48x48.png
> start_avview.desktop.in \
> -	README INSTALL
> +	alsa_mixer.scp channel_scan.scp  km.scp tree.scp xv.scp	vbi.scp	\
> +	avview.scp diag.scp setup.scp v4l.scp xmisc.scp lirc.scp \
> +	avview.modmap avview-16x16.ppm avview-control-16x16.ppm \
> +	avview-48x48.png start_avview.desktop.in README INSTALL
>
> #
> # Whoever said that the suffix is .c ?
> diff -u avview.cvs/avview.scp avview/avview.scp
> --- avview.cvs/avview.scp	2004-01-14 02:05:59.000000000 +0200
> +++ avview/avview.scp	2004-06-14 18:48:13.000000000 +0300
> @@ -23,6 +23,7 @@
> 	--screen-size=WxH		start TV window with size WxH
> 	--geometry=geometry		specify TV window geometry, using
> 					usual X11 notation
> +	--lircconf=files		LIRC config file name
>
> }
> }
> @@ -87,6 +88,11 @@
> 			regexp -- {--geometry=(.+)} $option {} geometry
> 			append startup_script "wm geometry .
> \"$geometry\"\n"
> 			}
> +		"--lircconf=*" {
> +			global lirc_config_files
> +			regexp -- {--lircconf=(.+)} $option {} files
> + 			set lirc_config_files [split $files ,]
> +			}
> 		}
> 	}
>
> @@ -106,7 +112,8 @@
>
> foreach file {xmisc.scp tree.scp setup.scp themes.scp alsa.scp
> 	v4l.scp xv.scp channel_scan.scp ffmpeg.scp
> -	video_device.scp diag.scp bindings.scp vbi.scp km.scp} {
> +	video_device.scp diag.scp bindings.scp vbi.scp km.scp
> +	lirc.scp} {
> 	source $avview_directory/$file
> 	}
>
> diff -u avview.cvs/configure.in avview/configure.in
> --- avview.cvs/configure.in	2004-01-05 23:03:47.000000000 +0200
> +++ avview/configure.in	2004-06-15 18:21:06.000000000 +0300
> @@ -38,6 +38,7 @@
>
> AC_ARG_WITH(ffmpeg, [  --with-ffmpeg=path      Path to compiled ffmpeg
> source tree])
> AC_ARG_ENABLE(alsa, [  --disable-alsa          Do not use ALSA sound
> library])
> +AC_ARG_ENABLE(lirc, [  --disable-lirc          Disable LIRC support])
>
> AC_CHECK_LIB([dl], [dlopen])
> AC_CHECK_LIB([z], [uncompress])
> @@ -45,6 +46,7 @@
> AC_CHECK_LIB([pthread], [pthread_create])
> AC_CHECK_LIB([zvbi], [vbi_capture_v4l_new])
> AC_CHECK_LIB([asound], [snd_card_get_name])
> +AC_CHECK_LIB([lirc_client], [lirc_init])
>
> echo "The libraries mp3lame, ogg, vorbis and vorbisenc might be required
> by ffmpeg"
> AC_CHECK_LIB([mp3lame], [lame_encode_buffer])
> @@ -87,6 +89,21 @@
>
> fi
>
> +LIRC_PRESENT=no
> +
> +if ! test "$enable_lirc" = "no" ; then
> +
> +  if test "$ac_cv_lib_lirc_client_lirc_init" = "yes" ; then
> +    AC_DEFINE(USE_LIRC, 1, [use lirc libraries])
> +    LIRC_PRESENT=yes
> +  fi
> +
> +else
> +
> +  LIRC_PRESENT=disabled
> +
> +fi
> +
> AC_CHECK_HEADER(linux/videodev.h, ,echo "Avview requires video4linux
> support. You may want to upgrade to Linux 2.4.x."; exit)
>
> AC_CHECK_HEADER(libzvbi.h, , echo "Avview requires libzvbi 0.2.3 or
> later" ; exit )
> @@ -217,6 +234,7 @@
> echo "  TK location                         $TK_PREFIX"
> echo "  TCL version                         $TK_VERSION$TK_PATCH_LEVEL"
> echo "  ALSA support                        $ALSA_PRESENT"
> +echo "  LIRC support                        $LIRC_PRESENT"
> if test "$with_ffmpeg" = "" ; then
> echo "  Movie recording                     disabled"
> echo "         to enable specify
> --with-ffmpeg=/path/to/compiled/ffmpeg/source"
> diff -u avview.cvs/main.c avview/main.c
> --- avview.cvs/main.c	2004-01-03 20:21:19.000000000 +0200
> +++ avview/main.c	2004-06-11 20:08:39.000000000 +0300
> @@ -27,6 +27,7 @@
> #include "linux.h"
> #include "alsa.h"
> #include "vbi.h"
> +#include "lirc.h"
> #include <pthread.h>
>
> pthread_mutex_t  memory_mutex;
> @@ -79,6 +80,7 @@
> int Tcl_AppInit(Tcl_Interp * interp)
> {
> int status=TCL_OK;
> +ClientData data;
>
> status=Tcl_Init(interp);
> if(status!=TCL_OK)return TCL_ERROR;
> @@ -93,6 +95,8 @@
> init_alsa(interp);
> init_linux(interp);
> init_vbi(interp);
> +data=init_lirc(interp);
> +Tcl_CreateExitHandler(deinit_lirc, data);
> return TCL_OK;
> }
>
> diff -u avview.cvs/lirc.c avview/lirc.c
> --- avview.cvs/lirc.c	1970-01-01 02:00:00.000000000 +0200
> +++ avview/lirc.c	2004-06-15 20:09:03.000000000 +0300
> @@ -0,0 +1,185 @@
> +/*     lirc support for avview
> +
> +       (C) Antti Ajanki 2004
> +
> +       GNU Public License
> +
> +*/
> +
> +#ifdef HAVE_CONFIG_H
> +#include <config.h>
> +#endif
> +
> +#include <stdio.h>
> +#include <stdlib.h>
> +#include <tcl.h>
> +#include <tk.h>
> +#include <unistd.h>
> +#include <stdio.h>
> +#include <stdlib.h>
> +#include <string.h>
> +
> +#ifdef USE_LIRC
> +
> +#include <lirc/lirc_client.h>
> +#include <fcntl.h>
> +
> +struct lircdata {
> +  struct lirc_config *config;
> +  Tcl_Interp *interp;
> +};
> +
> +void lirc_event_handler(ClientData clientData, int mask) {
> +  int ret;
> +  char *code;
> +  char *c;
> +  char *buffer;
> +  int len;
> +  struct lircdata *data=(struct lircdata *)clientData;
> +
> +  // If we have no config file loaded, just read the strings from
> +  // socket but don't act upon them.
> +  if (data->config == NULL) {
> +    while(lirc_nextcode(&code)==0 && code!=NULL) {
> +      free(code);
> +    }
> +    return;
> +  }
> +
> +  // There can be multiple string in the socket waiting to be read.
> +  while((ret=lirc_nextcode(&code))==0 && code!=NULL) {
> +    // Translate code to action string and pass the string to TCL
> +    // procedure.
> +    ret=lirc_code2char(data->config,code,&c);
> +    if(ret==0 && c!=NULL) {
> +      len=strlen(c)+23;
> +      buffer=malloc(len);
> +      strcpy(buffer, "handle_lirc_command \"");
> +      strcpy(buffer+21, c);
> +      strcpy(buffer+len-2, "\"");
> +
> +      Tcl_EvalEx(data->interp, buffer, len-1, TCL_EVAL_GLOBAL);
> +      free(buffer);
> +    }
> +    free(code);
> +    if(ret == -1) break;
> +  }
> +}
> +
> +char *lirc_conffiles_changed(ClientData clientData, Tcl_Interp *interp,
> +			     char *name1, char *name2, int flags) {
> +  Tcl_Obj *configfilelist;
> +  Tcl_Obj **filenames;
> +  int num, i;
> +  char *filename;
> +  struct lircdata *data = (struct lircdata *)clientData;
> +  Tcl_DString *dstring;
> +
> +  if (clientData == NULL ) return NULL;
> +
> +  // The value of the variable is list of file names.
> +  configfilelist=Tcl_GetVar2Ex(interp, "lirc_config_files",
> +			       NULL, TCL_GLOBAL_ONLY);
> +
> +  if (configfilelist != NULL) {
> +    // First free old config data.
> +    lirc_freeconfig(data->config);
> +    data->config=NULL;
> +
> +    // Try to load every file and print error message it loading
> +    // fails.
> +    if (Tcl_ListObjGetElements(interp, configfilelist,
> +			       &num, &filenames) !=TCL_OK) {
> +      return NULL;
> +    }
> +
> +    for(i=0; i<num; i++) {
> +      filename = Tcl_GetString(filenames[i]);
> +      printf("Loading LIRC config file %s.\n", filename);
> +
> +      // Perform tilde substitution with Tcl_TranslateFileName. It
> +      // needs a Tcl_DString to return the name.
> +      dstring=(Tcl_DString *)Tcl_Alloc(sizeof(Tcl_DString));
> +      if(Tcl_TranslateFileName(interp, filename, dstring) != NULL) {
> +	filename = Tcl_DStringValue(dstring);
> +	if(lirc_readconfig(filename,&(data->config),NULL)==-1)
> +	  fprintf(stderr, "Error reading LIRC config file %s\n", filename);
> +
> +	Tcl_DStringFree(dstring);
> +      }
> +
> +      Tcl_Free((char *)dstring);
> +    }
> +  }
> +
> +  return NULL;
> +}
> +
> +ClientData init_lirc(Tcl_Interp *interp) {
> +  int flags;
> +  int lirc_socket;
> +  struct lirc_config *config;
> +  struct lircdata *data;
> +
> +  printf("Initializing LIRC.\n");
> +
> +  lirc_socket=lirc_init("avview",1);
> +  if(lirc_socket == -1) {
> +    fprintf(stderr, "Can't initialize LIRC: error opening socket.\n");
> +    return NULL;
> +  }
> +
> +  if(lirc_readconfig(NULL,&config,NULL)==-1) {
> +    fprintf(stderr, "Can't read default LIRC config file ~/.lircrc.\n");
> +    config=NULL;
> +  }
> +
> +  // Make socket non-blocking.
> +  fcntl(lirc_socket,F_SETOWN,getpid());
> +  flags=fcntl(lirc_socket,F_GETFL,0);
> +  if(flags == -1) {
> +    fprintf(stderr, "Can't initialize LIRC:"
> +	    "error occured while setting-up the socket.\n");
> +    lirc_deinit();
> +    return NULL;
> +  }
> +  fcntl(lirc_socket,F_SETFL,flags|O_NONBLOCK);
> +
> +  data=malloc(sizeof(struct lircdata));
> +  data->interp=interp;
> +  data->config=config;
> +
> +  // Trace this variable, so that we can load new config file when its
> +  // name is written to lirc_config_files
> +  Tcl_TraceVar(interp, "lirc_config_files", TCL_TRACE_WRITES,
> +	       (Tcl_VarTraceProc *)lirc_conffiles_changed, data);
> +
> +  // Register the event handler, which reads the socket and executes
> +  // the LIRC commands.
> +  Tcl_CreateFileHandler(lirc_socket, TCL_READABLE,
> +			lirc_event_handler, data);
> +  return data;
> +}
> +
> +void deinit_lirc(ClientData clientData) {
> +  struct lircdata *data=clientData;
> +
> +  // If data == NULL, the initialization failed and there is nothing
> +  // to deinitialize.
> +  if(data == NULL) return;
> +
> +  lirc_freeconfig(data->config);
> +  lirc_deinit();
> +  free(data);
> +}
> +
> +#else /* USE_LIRC */
> +
> +ClientData init_lirc(Tcl_Interp *interp) {
> +  return NULL;
> +}
> +
> +void deinit_lirc(ClientData clientData) {
> +}
> +
> +#endif /* USE_LIRC */
> diff -u avview.cvs/lirc.h avview/lirc.h
> --- avview.cvs/lirc.h	1970-01-01 02:00:00.000000000 +0200
> +++ avview/lirc.h	2004-06-15 18:53:33.000000000 +0300
> @@ -0,0 +1,17 @@
> +/*     lirc support for avview
> +
> +       (C) Antti Ajanki 2004
> +
> +       GNU Public License
> +
> +*/
> +
> +#ifndef __LIRC_H__
> +#define __LIRC_H__
> +
> +#include <tcl.h>
> +
> +ClientData init_lirc(Tcl_Interp * interp);
> +void deinit_lirc(ClientData data);
> +
> +#endif
> diff -u avview.cvs/lirc.scp avview/lirc.scp
> --- avview.cvs/lirc.scp	1970-01-01 02:00:00.000000000 +0200
> +++ avview/lirc.scp	2004-06-15 18:17:49.000000000 +0300
> @@ -0,0 +1,38 @@
> +#!avview_shell
> +
> +global lirc_bindings
> +set lirc_bindings {
> +    "toggle_fullscreen" "fullscreen"
> +    "next_fav_channel" "next_channel"
> +    "toggle_mute" "mute"
> +    "exit_avview" "exit"
> +    "switch_to_control XV_VOLUME; change_control" "volume"
> +    "next_control" "next_control"
> +    "change_control" "change_control"
> +    "next_encoding 1" "next_encoding"
> +    "remote_power_off" "remote_power_off"
> +    "switch_to_channel" "channel"
> +}
> +
> +proc handle_lirc_command { lircstring } {
> +    global lirc_bindings
> +
> +    # There can be multiple lines in one lircstring. Split the string
> +    # and handle every line separately.
> +    foreach line [split $lircstring \n] {
> +	# Extract space-separated tokens from line. The first token is
> + 	# commandname and will be compared against commandnames in
> + 	# lirc_bindings list. Remaining tokens will be passed as
> + 	# parameters to corresponding tcl-procedure.
> + 	set tokens [split $line]
> + 	foreach {action commandstring} $lirc_bindings {
> + 	    if {[lindex $tokens 0] == $commandstring} {
> + 		set err [catch {eval $action [lrange $tokens 1 end]} errmsg]
> + 		if {$err!=0} {
> + 		    puts stderr "Error in LIRC command: $errmsg"
> + 		}
> + 		break
> + 	    }
> + 	}
> +    }
> +}
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Hi Bryan,

   Thank you for the patch :)

   As you note the better solution is to merge with latest X.org code.
Could you try making a diff as follows:

     cd ati.4.4.0
     cvs diff -u -r orig -r HEAD

This will produce a diff of GATOS-specific changes, perhaps they will 
apply cleanly to 6.7.99 code ?

                     thank you !

                           Vladimir Dergachev

On Sun, 22 Aug 2004, Bryan D. Stine wrote:

> Hello everyone.
>
> I've attached a patch that allows GATOS to build against the in-development
> Xorg. This is tested against 6.7.99.2 (specifically, the SDK) and seems to
> require drm.h (from the extras/drm shared stuff) in one of the include dirs.
> As you can see, this does not merge the ati changes from 6.7.99 in, but only
> allows it to build. In my basic testing, it appears to work. The better
> solution is to merge the GATOS stuff into the upcoming release, though, so I
> consider this a temporary solution.
>
> (patch -p1 in the gatos src dir)
>
> -- 
> Bryan D. Stine
> <bat...@ge...>
>
> "Wade Boggs...goes down smooth."
> --Hank Aaron XXIV, 998 years from now
>

Hi Stanislav,

   I have checked in gatosmax.diff + gatosvideoextra.diff.

   Thank you very much !

                  Vladimir Dergachev

On Thu, 12 Aug 2004, Stanislav Brabec wrote:

> Hallo.
>
> There is a patch set, which fixes missing parts of ati.2 driver in
> ati.4.4.0. With these patches, TV tuner works OK with my R128 AIW,
> Xorg-X11 6.7.0 and ati.4.4.0.
>
> You can select one of possible patch sets:
>
> Minimal set of patches (fixes only absolutely needed things):
> gatoswait.diff+gatosbios.diff+gatosvideo.diff+gatosvideoextra.diff
> My tuner works.
>
> Maximal set of patches (adds all things not present in ati.4.4.0 and
> present in ati.2):
> gatosmax.diff+gatosvideoextra.diff
> My tuner works.
>
> Patches was created by manual editing of complete diff.
>
> You can browse these patches manually and check, what is useful and
> should be kept in ati.4.4.0.
>
> For future porting, it would be nice to distribute gatos also as diff
> file (or store in CVS exact information about X sources version - for
> example store original X files or keep original CVS headers using cvs
> admin -ko).
>
> Another good news is, that driver compiles against xorg serverkit and
> complete X sources are not needed any more:
>
> xmkmf /usr/X11R6/lib/Server
> make
> make install
>
> The remaining error (meaningless) with xorg-x11 is:
> checking rman over in /usr/X11R6/lib/Server/config/util first...
> make[1]: Entering directory `/usr/X11R6/lib/Server/config/util'
> make[1]: *** No rule to make target `rmanonly'.  Stop.
>
>
> ________________________________________________________________________
> Stanislav Brabec
> http://www.penguin.cz/~utx
>

On Wed, 25 Aug 2004, Eduardo Moreno wrote:

> I have a Nvidia card (primary), and also an ATI AIW pro. Using current
> release of Xorg, ati.2 drivers don't compile. ATI 4.4.0 compiles but
> doesn't work, because the X doesn't start (it freeze after the NVIDIA
> screen before start X), and the Xorg.log doesn't say anything. This is
> the tail of the log:
>
> (II) LoadModule: "tda8425"
> (II) Loading /usr/X11R6/lib/modules/multimedia/tda8425_drv.o
> (II) Module tda8425: vendor="X.Org Foundation"
>        compiled for 4.3.99.902, module version = 1.0.0
>        ABI class: X.Org Video Driver, version 0.7
> Fatal server error:
> Caught signal 11.  Server aborting
>
> The only GATOS drivers working for me are binary 4.3 drivers. I see the
> diff between both Xorg.log, I found only one thing anormal, BIOS is not
> founded in the 4.4.0 drivers:
>
> < (II) ATI(1): 0x55 0xaa
> < (II) ATI(1): VIDEO BIOS TABLE OFFSETS: bios_header=0x010e mm_table=0x015e
> < (II) ATI(1): MM_TABLE: 00-08-06-3a-4b-22-00-00-00-00-24-41-54-49
> ---
>> (II) ATI(1): Cannot access BIOS: info->VBIOS==NULL.
>> (II) ATI(1): No MM_TABLE found 0, 0
>
> Any help? is the NVIDIA card the problem? ATI must be the primary card?
> Thanks.

You have likely pinned this down - the BIOS is not being found on your ATI 
card.

Does the stock Xorg ATI driver work for you ? If yes, could you compare 
the portions of radeon_driver.c that detect BIOS in both drivers ?

                       thank you !

                            Vladimir Dergachev

>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

I have a Nvidia card (primary), and also an ATI AIW pro. Using current
release of Xorg, ati.2 drivers don't compile. ATI 4.4.0 compiles but
doesn't work, because the X doesn't start (it freeze after the NVIDIA
screen before start X), and the Xorg.log doesn't say anything. This is
the tail of the log:

(II) LoadModule: "tda8425"
(II) Loading /usr/X11R6/lib/modules/multimedia/tda8425_drv.o
(II) Module tda8425: vendor="X.Org Foundation"
         compiled for 4.3.99.902, module version = 1.0.0
         ABI class: X.Org Video Driver, version 0.7
Fatal server error:
Caught signal 11.  Server aborting

The only GATOS drivers working for me are binary 4.3 drivers. I see the
diff between both Xorg.log, I found only one thing anormal, BIOS is not
founded in the 4.4.0 drivers:

< (II) ATI(1): 0x55 0xaa
< (II) ATI(1): VIDEO BIOS TABLE OFFSETS: bios_header=0x010e mm_table=0x015e
< (II) ATI(1): MM_TABLE: 00-08-06-3a-4b-22-00-00-00-00-24-41-54-49
---
> (II) ATI(1): Cannot access BIOS: info->VBIOS==NULL.
> (II) ATI(1): No MM_TABLE found 0, 0

Any help? is the NVIDIA card the problem? ATI must be the primary card?
Thanks.

On Fri, 20 Aug 2004, Mark Tabash wrote:

> if (init_km_v4l(kms)){
> 	free_irq(kms->irq, kms);
> 	iounmap(kms->reg_aperture);
> 	release_mem_region(pci_resource_start(dev,2),
> 	pci_resource_len(dev,2));
> 	pci_set_drvdata(dev, NULL);
> 	return -EIO;
> }
>
> Yeilds a compilation error since init_km_v4l() has a void return type. 
>Please
> advise on how to fix this. Thanks.

Short answer: current CVS version is broken, download an older version (I 
think -D option with cvs helps)

Longer answer: That particular problem is easily fixed by simply removing 
the if statement but alas it is not the only obstacle preventing km from 
compiling.

It seems to me that the sysfs patch has broken the compilation. km_v4l.c 
isn't using pointers to video device structs as it now should, see 
attached compilation error messages.

I tried to change every reference to videodev structs to pointers and
driver compiles and even works, but I still get the "Please fix your
driver for proper sysfs support" messages in the logs, so apparently
it is not enough to fix the sysfs issue.

-- 
Antti Ajanki

Hello everyone.

I've attached a patch that allows GATOS to build against the in-development 
Xorg. This is tested against 6.7.99.2 (specifically, the SDK) and seems to 
require drm.h (from the extras/drm shared stuff) in one of the include dirs. 
As you can see, this does not merge the ati changes from 6.7.99 in, but only 
allows it to build. In my basic testing, it appears to work. The better 
solution is to merge the GATOS stuff into the upcoming release, though, so I 
consider this a temporary solution.

(patch -p1 in the gatos src dir)

-- 
Bryan D. Stine
<bat...@ge...>

"Wade Boggs...goes down smooth."
 --Hank Aaron XXIV, 998 years from now

On Sat, 21 Aug 2004, Michael Lindner wrote:

> Hi,
>
> I'm a developer (currently, although I haven't done UNIX driver development
> since the 1980s), who has a new PC with a 2.6 kernel and an ATI Radeon 9200
> All-in-wonder. I see this is currently unsupported, but it looks like you
> have a group actively developing, and I thought I would offer to see if I
> could be of any assistance.
>
> I don't have gobs of free time (I have a day job), and am naive about the
> Linux 2.6 kernel and video card drivers in general, but I am technically
> astute, and a seasoned C developer, so if you have any tasks that don't
> require knowledge I don't have, or if you'd be kind enough to point me to
> documentation so I could learn, I'd be happy to help.

The first thing to find out is what chips you have onboard. Do you have 
Rage Theatre or Rage Theatre 200 ? Which tuner module ? (large metal box).

Also find out what other chips are onboard and which version of Radeon it 
is.

                         best

                           Vladimir Dergachev

>
> Please let me know.
> -- 
> Michael Lindner
> http://www.starastronomy.org *** http://home.att.net/~mikel
> http://www.atmsite.org *** http://www.atmlist.net
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>

Hi,

I'm a developer (currently, although I haven't done UNIX driver development 
since the 1980s), who has a new PC with a 2.6 kernel and an ATI Radeon 9200 
All-in-wonder. I see this is currently unsupported, but it looks like you 
have a group actively developing, and I thought I would offer to see if I 
could be of any assistance.

I don't have gobs of free time (I have a day job), and am naive about the 
Linux 2.6 kernel and video card drivers in general, but I am technically 
astute, and a seasoned C developer, so if you have any tasks that don't 
require knowledge I don't have, or if you'd be kind enough to point me to 
documentation so I could learn, I'd be happy to help.

Please let me know.
-- 
Michael Lindner
http://www.starastronomy.org *** http://home.att.net/~mikel
http://www.atmsite.org *** http://www.atmlist.net

Hello,

The change from version 1.95 on line 679:
init_km_v4l(kms); 

To version 1.96 on line 688:
if (init_km_v4l(kms)){	
 	free_irq(kms->irq, kms);	
 	iounmap(kms->reg_aperture);	
 	release_mem_region(pci_resource_start(dev,2),	
 	pci_resource_len(dev,2));	
 	pci_set_drvdata(dev, NULL);	
	return -EIO;	
}

Yeilds a compilation error since init_km_v4l() has a void return type. Please 
advise on how to fix this. Thanks.

Cheers,

Mark T.

--- Vladimir Dergachev <vo...@mi...> wrote:
> On Fri, 20 Aug 2004, Jon Smirl wrote:
> 
> > There is already code in X for coordinating video memory usage with
> > DRM. The DRM memory manager keeps 2D X from stomping on 3D buffers.
> > Same mechansim can be used to protect the video streaming memory.
> 
> Last time I checked this was not straightforward. Furthermore, aren't
> 3d buffers fixed in size after Xserver startup ?

There is a DRM API for allocating VRAM memory from the pool assigned to
3D use. Just allocate yourself a chunk and don't start any 3D
operations on it. You get a pointer to it so you can do anything you
want with it.

> > Several other cards use kernel based v4l drivers, why is the radeon
> > special?
> 
> I am only aware of bt848 cards - these are standalone video capture
> device and do not have to share anything.

Check out the Matrox implementation.

> Also, AIW cards do have a v4l interface - however it is an auxiliary 
> driver only, it needs Xv program to setup the video stream for any
> data to be available (this way it can use video memory already
> allocated by Xserver for video stream)

I always thought the best solution would be combining the radeon V4L
device driver into the radeon DRM driver. That way we only have a
single device driver trying to attach to the hardware. The combined
driver would expose two interfaces, DRM and V4L. Since the drivers are
combined you can easily sort out the memory allocation.

Have you tried doing the experiment of combining the radeon DRM and V4L
device drivers? I would start out by just mixing up all of the code.
But the final version should make the V4L support an add-on module to
the DRM one.


=====
Jon Smirl
jon...@ya...


		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail