gatos-devel Mailing List for GATOS

Hi,
I have a 9200SE and I set the ntsc-pal pin switcher to pal. Plugging this card 
on a different computer it boots in pal but using a P4R800-VM (radeon 9100 
IGP...) it only boots in ntsc and can't change color mode 
(Option "TVStandard") within x, only the modeline. The Option works, thus if 
I swith it to another format it changes.
I know that there are some problems with 9100IGP but even plugging an external 
AGP card?? Opengl and dri works ok ...

Thanks !

Am Dienstag 12 Juni 2007 schrieb federico ulivi:
> I've just re-released the tv output driver with MIT license.

Now, that's great news. For completenes, I think all people that have over =
the=20
time adapted the driver to latest drivers should also agree to the=20
MIT-license.

They are, from what I know
a) Rune Petersen
b) Wei-Tsun Sun
c) Anton Bolshakov
d) Mounir Lamouri
e) Oliver Schinagl
f) Steven Leung
Anyone I forgot?

Now, if they all could agree with the new license (probably best on some=20
public place, e.g. the gatos-list), this would be fine. The latest version =
I=20
know is the one in the gentoo bugzilla.

While I'm not really familiar with the code, I'd like to provide some=20
coordination. I've updated the wiki-page at
http://wiki.x.org/wiki/radeonTV
with some new information. I think this could be the place where all=20
development gets together.

=2D-=20
Hanno B=C3=B6ck		Blog:   http://www.hboeck.de/
GPG: 3DBD3B20		Jabber: ja...@hb...

dPailler a écrit :
> Hi everybody,
>
> I am really sorry , but I can't still make capture work with avview and km:
>
>  avview work perfectly.
>
> But i always have 
>
> "Looking for km device that corresponds to PCI:01:00.0
> km_devs=
> Looking for km device that corresponds to PCI:01:00.0
> km_devs=
>
> vbi_sec_cc_page_on_screen_err=failed to open VBI device:
> V4L2 access method failed: Cannot open '/dev/vbi0': 2, No such file or
> directory.
> V4L access method failed: Cannot open '/dev/vbi0': 2, No such file or
> directory.BKTR access method failed: BKTR driver interface not compiled.)
> "
> when I type " start_avview " on command line
>
> I don't understand why there is nothing after km_devs=
>
> For km : I have made make; make test and make install after a /etc/init.d/gdm stop and before /etc/init.d/gdm start
>
> Once with 2.6.18 kernel , it gave me something, but 99% of the times that freezed my computer. And I didn't know why after  a lot of tests , it began to work.
> But now, I am on 2.6.20.11 on Etch for network reason.
>
> I have a All in wonder radeon agp 32M wich seems to work perfectly ( I didn' see wrong things on Xorg.0.log)
>  
> Is there a problem with radeonfb ?
>
> tThanks for your help.
>
> David Pailler
>   
Is the fact that I put the option UseFBdev at "false" can have any place
in the pb. I have to put it at false because in the other case , it
freeze my PC. and it is impossible to launch xserver.

Hi everybody,

I am really sorry , but I can't still make capture work with avview and km:

 avview work perfectly.

But i always have 

"Looking for km device that corresponds to PCI:01:00.0
km_devs=
Looking for km device that corresponds to PCI:01:00.0
km_devs=

vbi_sec_cc_page_on_screen_err=failed to open VBI device:
V4L2 access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.
V4L access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.BKTR access method failed: BKTR driver interface not compiled.)
"
when I type " start_avview " on command line

I don't understand why there is nothing after km_devs=

For km : I have made make; make test and make install after a /etc/init.d/gdm stop and before /etc/init.d/gdm start

Once with 2.6.18 kernel , it gave me something, but 99% of the times that freezed my computer. And I didn't know why after  a lot of tests , it began to work.
But now, I am on 2.6.20.11 on Etch for network reason.

I have a All in wonder radeon agp 32M wich seems to work perfectly ( I didn' see wrong things on Xorg.0.log)
 
Is there a problem with radeonfb ?

tThanks for your help.

David Pailler

Stanislav Brabec a écrit :
> dPailler wrote:
>
>   
>> I always have , after patching avview :
>> "checking ffmpeg version...
>>
>> *** AVview requires ffmpeg 0.4.8
>> If you are sure you are using correct version of ffmpeg check config.log
>> for det ails
>> "
>> I did :
>>  "./configure --with-alsa
>> --with-ffmpeg=/home/david/compile/ffmpeg-0.4.9-pre1/"
>>
>> What do I have not understand ?
>>     
>
> Call autoreconf (or autoreconf -f -i, or autoconf). configure needs to
> be re-generated from patched configure.in.
>
>   
Thanks, in fact acalocal autoconf autoheader automake and latest ffmpeg
is accepted.

But now , I still have my km problem:
start_avview and avview work perfectly.
But

"Looking for km device that corresponds to PCI:01:00.0
km_devs=
Looking for km device that corresponds to PCI:01:00.0
km_devs=

vbi_sec_cc_page_on_screen_err=failed to open VBI device:
V4L2 access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.
V4L access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.BKTR access method failed: BKTR driver interface not compiled.)
"
I don't understand why there is nothing after km_devs=


I have made make; make test and make install after a /etc/init.d/gdm stop and before /etc/init.d/gdm start
Is there a problem with radeonfb ?

dPailler wrote:

> I always have , after patching avview :
> "checking ffmpeg version...
> 
> *** AVview requires ffmpeg 0.4.8
> If you are sure you are using correct version of ffmpeg check config.log
> for det ails
> "
> I did :
>  "./configure --with-alsa
> --with-ffmpeg=/home/david/compile/ffmpeg-0.4.9-pre1/"
> 
> What do I have not understand ?

Call autoreconf (or autoreconf -f -i, or autoconf). configure needs to
be re-generated from patched configure.in.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx, ICQ 116020046

Stanislav Brabec a écrit :
> dPailler wrote:
>   
>> Stanislav Brabec a écrit :
>>     
>>> dPailler wrtoe:
>>>       
>
>   
>> Thank you,
>> but what do you mean by cleaning avview/ffmpeg.c ?
>>
>> And I don't understand : "prevent
>>
>> double conversion by using of new AVRational type "
>>     
>
> ffmpeg-0.4.9 introduced new data type AVRational (fraction) for frame
> rate, and other similar information.
>
> ffmpeg-0.4.8 was using integers related to FFMPEG_FRAME_RATE_BASE.
>
> It means, that all computations inside avview code should be done
> directly in AVRational instead of using old units and converting the
> result to AVRational.
>
> New ffmpeg code also has a new argument parser, which also accepts
> AVRation strings.
>
>   
>> bytheway, Ihave to patch avview and try with ffmpeg 0.4.9 not with newer. that's it ?
>>     
>
> It was done against CVS version few months ago. It had O.4.9 in the
> configure string, so I named this patch 0.4.9.
>
>   
I will try but I don't get what you talking about !

And I am frnch my english is not really good and my knowledges about
compilation really really basic.

Stanislav Brabec a écrit :
> dPailler wrtoe:
>   
>> Hi every one,
>> Is there some onoewho have succeeded in the install off avview with a
>> newer ffmpeg than 0.4.8 ?
>>     
>
> http://ftp.penguin.cz/pub/users/utx/gatos/avview-ffmpeg-preliminary-crashing-0.4.9.patch
>
> Compiles and installs but crashes. Feel free to try to fix it.
>
> When it will work, avview/ffmpeg.c will need cleanup (e. g. prevent
> double conversion by using of new AVRational types).
>
>   
I always have , after patching avview :
"checking ffmpeg version...

*** AVview requires ffmpeg 0.4.8
If you are sure you are using correct version of ffmpeg check config.log
for det ails
"
I did :
 "./configure --with-alsa
--with-ffmpeg=/home/david/compile/ffmpeg-0.4.9-pre1/"

What do I have not understand ?

dPailler wrote:
> Stanislav Brabec a écrit :
> > dPailler wrtoe:

> Thank you,
> but what do you mean by cleaning avview/ffmpeg.c ?
> 
> And I don't understand : "prevent
> 
> double conversion by using of new AVRational type "

ffmpeg-0.4.9 introduced new data type AVRational (fraction) for frame
rate, and other similar information.

ffmpeg-0.4.8 was using integers related to FFMPEG_FRAME_RATE_BASE.

It means, that all computations inside avview code should be done
directly in AVRational instead of using old units and converting the
result to AVRational.

New ffmpeg code also has a new argument parser, which also accepts
AVRation strings.

> bytheway, Ihave to patch avview and try with ffmpeg 0.4.9 not with newer. that's it ?

It was done against CVS version few months ago. It had O.4.9 in the
configure string, so I named this patch 0.4.9.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sb...@su...
Lihovarská 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

Stanislav Brabec a écrit :
> dPailler wrtoe:
>   
>> Hi every one,
>> Is there some onoewho have succeeded in the install off avview with a
>> newer ffmpeg than 0.4.8 ?
>>     
>
> http://ftp.penguin.cz/pub/users/utx/gatos/avview-ffmpeg-preliminary-crashing-0.4.9.patch
>
> Compiles and installs but crashes. Feel free to try to fix it.
>
> When it will work, avview/ffmpeg.c will need cleanup (e. g. prevent
> double conversion by using of new AVRational types).
>
>   
Thank you,
but what do you mean by cleaning avview/ffmpeg.c ?

And I don't understand : "prevent

double conversion by using of new AVRational type "

bytheway, Ihave to patch avview and try with ffmpeg 0.4.9 not with newer. that's it ?

dPailler wrtoe:
> Hi every one,
> Is there some onoewho have succeeded in the install off avview with a
> newer ffmpeg than 0.4.8 ?

http://ftp.penguin.cz/pub/users/utx/gatos/avview-ffmpeg-preliminary-crashing-0.4.9.patch

Compiles and installs but crashes. Feel free to try to fix it.

When it will work, avview/ffmpeg.c will need cleanup (e. g. prevent
double conversion by using of new AVRational types).

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sb...@su...
Lihovarská 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

Thank you!
Now all it is left is to make it work for Radeon 9600 M10 family :)

On 6/12/07, federico ulivi <fu...@ly...> wrote:
> Hi everyone!
>
> I've just re-released the tv output driver with MIT license.
> I hope this will make it easier to integrate into X.Org without patches.
> Do not expect any new feature, code is exactly the same.
> I basically abandoned the development in 2004 due to severe lack of time.
> I apologize for taking so long to all the guys who asked for this
> re-licensing.
>
> Enjoy!
>
>
>
> Federico Ulivi - Milan (Italy)
> http://utenti.lycos.it/fulivi
>
>
>  ________________________________
>
>  Want to change your life? Find the perfect job with Lycos Jobs.
>  Career Advice. Job Resources & Recommendations.
>  Post your resume & find a job match!
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
> https://lists.sourceforge.net/lists/listinfo/gatos-devel
>
>

Hi every one,
Is there some onoewho have succeeded in the install off avview with a
newer ffmpeg than 0.4.8 ?

And for the install of km is someone have the same pb as mine ?:

I have change my kernel to 2.6.20.11 on etch and I can't have the v4l
driver . In the message of avview there is :
"Looking for km device that corresponds to PCI:01:00.0
km_devs=
Looking for km device that corresponds to PCI:01:00.0
km_devs=
"
But nothing after  the "="
(And
"vbi_sec_cc_page_on_screen_err=failed to open VBI device:
V4L2 access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.
V4L access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.BKTR access method failed: BKTR driver interface not compiled.)
"


Is it km problem or avview problem ?

Thanks for your help.

Hi everyone!
<br>
<br>I've just re-released the tv output driver with MIT license.
<br>I hope this will make it easier to integrate into X.Org without patches.
<br>Do not expect any new feature, code is exactly the same. 
<br>I basically abandoned the development in 2004 due to severe lack of time.
<br>I apologize for taking so long to all the guys who asked for this re-licensing.
<br>
<br>Enjoy!
<br><br><br><br><font color=# style='font-size: 9pt;'>Federico Ulivi - Milan (Italy)
<br>http://utenti.lycos.it/fulivi
<br></font><br/>
<div>
<hr style="width:85%;margin-left:0px;text-align:left"/><br/>
<b>Want to change your life? Find the perfect job with Lycos Jobs.</b><br/>
Career Advice. Job Resources & Recommendations.<br/>
<a href="http://www.careerbuilder.com/?lr=cblycos&siteid=lycoshp7"
target="_blank"><u>Post your resume & find a job match!</u></a>
</div>

I have change my kernel to 2.6.20.11 on etch and I can't have the v4l
driver . In the message of avview ther is :
"Looking for km device that corresponds to PCI:01:00.0
km_devs=
Looking for km device that corresponds to PCI:01:00.0
km_devs=
"
But nothing after  the "="
And
"vbi_sec_cc_page_on_screen_err=failed to open VBI device:
V4L2 access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.
V4L access method failed: Cannot open '/dev/vbi0': 2, No such file or
directory.BKTR access method failed: BKTR driver interface not compiled.
"
I think that when km=devs will give me something.
I shall have progressed./
Nethertheless I have tv worked.
Please is someone can help me ?
Km et avview from cvs and ffmpeg-0.4.8 with gcc-3.4