gatos-devel Mailing List for GATOS

Hi,

I'm totally new to linux. I've installed fedora core 5 but since I've ATI
Mobility Radeon 7500 I cannnot use the prop. ATI drivers. I was wondering i=
f
could get some help on how to get my tv-out working. Since I'm already
running X.org R7 I did not dear to try out the mini-how to on Rune's page.
I'm not really sure what I'm patching either.

Could you please give me a detailed description on how to get my tv-out
working. Here are some facts about my system.

- Kernel 2.6.16-1.2096_FC5 on i686
- X.org R7
- ATI Mob Rage 7500

Rahil

"Simeon Korzano" <ko...@us...> writes:
> When I start avview, Ican select any channel, I can see the picture 
> in color, but there is no sound. I can _watch_ TV even without km 
> modules.
> Every switch and button in mixer is checked. Volume and levels are 
> high and mute off. Alsa Sound System works fine. My sound card is 
> Sound Blaster Live Player 1024. What's wrong? What can I do?

You're stuck at the same point than me. After reading the
documentation, I saw that I need to load km *before* starting Xorg.

I have not yet found the time to actually try, so I cannot tell you more.

HTH

Quantum Scientific <In...@qu...> writes:

> The avview Readme says use ffmpeg-0.4.8, so I tried to compile that
> ancient thing.  But when I include the codec options, the build
> fails.  I would much rather use a more recent ffmpeg.

I did manage to build ffmpeg-0.4.8 with gcc-3.4. Compilation does not
work with gcc-4.0.

HTH

Hi

I have ATI 9800 PRO AIW installed in my computer. It works=20
flawlessly in Windows XP. I have Fedora Core 5 operating system,=20
kernel 2.6.16-1.2096_FC5. X version is 7.0. I copied ativmc20.cod by name=
=20
rt2_pmem.bin into /usr/lib/xorg/modules/multimedia.=20
According to Xorg.0.log it seem to be OK.

(II) RADEON(0): Microcode: Use default microcode path:=20
/usr/lib/xorg/modules/multimedia/rt2_pmem.bin
(II) RADEON(0): Microcode: Use default microcode type: BINARY
(II) RADEON(0): Microcode: device_id: 4d4a
(II) RADEON(0): Microcode: vendor_id: 1002
(II) RADEON(0): Microcode: rev_id: 21
(II) RADEON(0): Microcode: num_seg: 4
(II) RADEON(0): Microcode: dsp_init OK
(II) RADEON(0): Microcode: dsp_download OK
(II) RADEON(0): VIP_GPIO_CNTL: 200001
(II) RADEON(0): VIP_GPIO_INOUT: 6200000
(II) RADEON(0): VIP_GPIO_CNTL: 200011
(II) RADEON(0): VIP_GPIO_INOUT: 6310010
(II) RADEON(0): Rage Theatre setting standard 0x0000
(II) RADEON(0): Microcode: Use microcode path:=20
/usr/lib/xorg/modules/multimedia/rt2_pmem.bin
(II) RADEON(0): Microcode: Use microcode type: BINARY
(II) RADEON(0): Microcode: device_id: 4d4a
(II) RADEON(0): Microcode: vendor_id: 1002
(II) RADEON(0): Microcode: rev_id: 21
(II) RADEON(0): Microcode: num_seg: 4
(II) RADEON(0): Microcode: dsp_init OK
(II) RADEON(0): Microcode: dsp_download OK



I downloaded km-0.61,=20
avviewer-0.80.7 and latest patches. I compiled and installed them=20
without any problem.=20

Command lsmod | grep km prints:

km_drv                 39480  0
km_api_drv             16424  1 km_drv
videodev                9409  1 km_drv

Required modules seem to be loaded.
There is /proc/km, but it is empty. There are no /dev/video,=20
/dev/video0 or anything like that. Test1.tcl and test3.tcl report=20
errors.

When I start avview, Ican select any channel, I can see the picture=20
in color, but there is no sound. I can _watch_ TV even without km=20
modules.
Every switch and button in mixer is checked. Volume and levels are=20
high and mute off. Alsa Sound System works fine. My sound card is=20
Sound Blaster Live Player 1024. What's wrong? What can I do?

Best regards

Simeon=20
=20=20






--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/

Hello list,

Trying to build AVView, as that seems to be the most compatible with KM capture.

I'd built ffmpeg-0.cvs20060329 for it, and make completed for avview, but when I run it and it asks to be configured, I click OK and it promptly crashes.  Looking at the log, it got all kinds of missing files and symbol errors on ffmpeg.

The avview Readme says use ffmpeg-0.4.8, so I tried to compile that ancient thing.  But when I include the codec options, the build fails.  I would much rather use a more recent ffmpeg.

When I tried to get avview through CVS, it would not let me log in.

Is avview the best viewer for this?  Any idea what's wrong?  Can you capture video on an IBM A22P notebook with Rage MobilityM3 AGP 2x (rev 02)?  

If not, is there a better cardbus card, which might even capture HVTV through HDMI?

Thanks

Hendrik Sattler wrote:
> Am Mittwoch, 19. April 2006 15:50 schrieb Rune Petersen:
>> NTSC does not run at 60 Hz, but at 60*1000/1001 = 59.94 Hz.
>> So even NTSC needs to be down-sampled :)
> 
> And why does it not downsample itself? The chipset somewhat already _knows_ if 
> it needs 50 or 60 Hz and doing a 75Hz->50Hz conversion internally should not 
> be worth mentioning.
> Is the chipset really that cheap?
> 

My guess is it may be simpler/cheaper to have 2 predefined down-sample 
functions (60->50 & 60->59.94) then having a more general down-sampler, 
but I'm no expert I just call it as I see it.

In some ways TV-out can be seen as a crap-filter. you take a high 
quality image, ruin it, and then show it on a large screen TV.

By the way some time ago someone sent me a Xorg log showing a setup 
running at 75 Hz which He claimed worked. So it might work, or Xorg 
logged wrong (or he made a mistake).


Rune Petersen

Am Mittwoch, 19. April 2006 15:50 schrieb Rune Petersen:
> NTSC does not run at 60 Hz, but at 60*1000/1001 = 59.94 Hz.
> So even NTSC needs to be down-sampled :)

And why does it not downsample itself? The chipset somewhat already _knows_ if 
it needs 50 or 60 Hz and doing a 75Hz->50Hz conversion internally should not 
be worth mentioning.
Is the chipset really that cheap?

HS

Molle Bestefich wrote:
> Rune Petersen writes:
>> From what I know you should always use a refresh rate of 60 Hz.
> 
> I'm confused.
> You are aware that all PAL television sets expect 50 Hz, right?
Yes, but AFAIK the refresh rate does not drive that part of the TV-out 
circuit.
60 Hz is a natural choice if you want to have a monitor and the TV 
showing the same (clone).
The signal will get down-sampled to 50 Hz for PAL by the TV-out circuit.
I'm not saying that 50 Hz will not work, but that 60 Hz is a safer bet.

A funny fact:
NTSC does not run at 60 Hz, but at 60*1000/1001 = 59.94 Hz.
So even NTSC needs to be down-sampled :)
> 
>> Anyway none of this will happen before I get myself a place to live.
> 
> Yeah, I'm in that boat too.
> Copenhagen?  It's a bitch :-).  Damn expensive.

You don't say.


Rune Petersen

Kris Anderson writes:
> There's an exception in there.
> [... snip DMCA info ...]

Thanks for sharing!

Rune Petersen writes:
> From what I know you should always use a refresh rate of 60 Hz.

I'm confused.
You are aware that all PAL television sets expect 50 Hz, right?

> Anyway none of this will happen before I get myself a place to live.

Yeah, I'm in that boat too.
Copenhagen?  It's a bitch :-).  Damn expensive.

Greg Stark wrote:
> It's a binary-only driver.

Ah, thanks for clearing that up.

"Molle Bestefich" <mol...@gm...> writes:

> Another way around the defect-by-design copyright protection and the
> demented laws that protects it is to use Nvidia hardware.  I think TV
> output works fine with that.  Don't know if the developers have
> dinosaur balls, or if Nvidia has just ripped copy protection from the
> hardware entirely, or what's going on there, but I think it works. 

It's a binary-only driver.

-- 
greg

Molle Bestefich wrote:
> Rune Petersen wrote:
>> partly because of my illness
> 
> Condolences.
> Hope it's nothing serious...

At least not fatal (they had to operate).

> 
>> but mostly because I lack the knowledge to understand what
>> effects the different parameters has on the output. progress is usually
>> done by poking at the code and see if it helped.
> 
> I can say so much that the current patch doesn't work for me with a
> flatscreen and a TV.
> If I use IgnoreEDID to force the refresh to 50Hz, then X won't start:

 From what I know you should always use a refresh rate of 60 Hz.

> 
> (II) RADEON(0): Not using default mode "<X>x<Y>" (bad mode
> clock/interlace/doublescan)
> (WW) RADEON(0): Mode pool is empty
> (EE) RADEON(0): No valid mode found for this DFP/LCD
> (EE) Screen(s) found, but none have a usable configuration.

LCD's only work at 60 Hz and up.
> 
> If IgnoreEDID is disabled, then the output to the TV is out of sync.
> Probably driven at 60Hz.

> 
>> A very depressing way
>> to work when you don't have the necessary equipment.
> 
> Indeed.  (Equipment?)

An oscilloscope is the most obvious (I can borrow that). a test machine 
(I am currently using my "production" machine which is very restrictive) 
Another is test equipment that shows the different sync values (a bit 
expensive =)

If I am able to measure the sync values I might be able to deduce how 
the different parameters effect sync (H + V) and hopefully fix it.

Anyway none of this will happen before I get myself a place to live.


Rune Petersen

--- Molle Bestefich <mol...@gm...> wrote:

> Alberto Hernando wrote:
> > I've been trying the patch from
> http://megahurts.dk/rune/tv_output.html to
> > make work my radeon igp-9100 card. The tv output,
> I mean. Until now, I have
> > had no success. There is image, but it's out of
> sync.
> 
> I have the same problem with a different Radeon
> card.
> 
> > I've been searching in the web, but there is no
> info about work in progress.
> 
> Developers are scared of the DMCA, so no work is
> being done.
> 
> (Short story: Making TV output work is considered
> 'circumventing a
> copy-protection device'.)
> 
> (Long story: ATI is not making documentation
> available that would
> enable developers to get Macrovision working.  Since
> the hardware has
> Macrovision support, enabling TV output without it
> would constitute
> 'circumventing copy-protection'.)
> 
> > And if there is something in the cvs, there is no
> instructions to grab new versions.
> > I'm not a programmer. Using cvs might sound
> trivial, but it isn't for me.
> 
> Using CVS is not the hard part, you'll get the hang
> of that in no time.
> Making Xorg compile in your particular build
> environment is probably
> the hard part.
> You could use Gentoo, where the build environment is
> setup to compile
> X on your PC already.  And it probably should work
> on other distros
> too, but no guarantees - you'll have to try.
> 
> But didn't you just say that you were actively using
> the patch to
> drive (out of sync though) your TV output?
> 
> > Until now, I'm using the closed ati drivers. I get
> tv-out, but no dri
> 
> Plus it has various bugs that goes unfixed for
> months and months.
> 
> > So, if there something that a simple user can go
> to help, I'd like to know.
> 
> The current TV output patch *should* work for basic
> TV output,
> although it doesn't work for me either.
> 
> IMO what you'll get if you do make it work is
> horrible, compared to
> what your card can do and will do with Windows +
> Catalyst drivers +
> PowerStrip.
> 
> We could perhaps create a bounty for making proper
> TV output for
> Radeon cards, and someone in a country with less
> braindamaged laws
> could get the patch up to speed wrt. the features
> available on
> Windows.
> 
> I don't know if merging the patch with Xorg sources
> and getting it
> properly distributed would be a problem then. 
> Probably.
> 
> Another way around the defect-by-design copyright
> protection and the
> demented laws that protects it is to use Nvidia
> hardware.  I think TV
> output works fine with that.  Don't know if the
> developers have
> dinosaur balls, or if Nvidia has just ripped copy
> protection from the
> hardware entirely, or what's going on there, but I
> think it works. 
> Haven't tried it though.  But it's probably much
> easier just to switch
> hardware than to fix the Xorg drivers :-).
> 
> (And that is, by the way, exactly what I'm planning
> to do, once I
> figure out if I'm correct and TV output does work on
> Nvidia...)
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
> groundbreaking scripting language
> that extends applications into web and mobile media.
> Attend the live webcast
> and join the prime developer group breaking into
> this new coding territory!
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Gatos-devel mailing list
> Gat...@li...
>
https://lists.sourceforge.net/lists/listinfo/gatos-devel
> 
I'm confused, why are people afraid of the DMCA?

There's an exception in there.

{Item 2}
2. Reverse engineering (section 1201(f)). This
exception permits circumvention, and the development
of technological means for such circumvention, by a
person who has lawfully obtained a right to use a copy
of a computer program for the sole purpose of 
identifying and analyzing elements of the program
necessary to achieve interoperability with other
programs, to the extent that such acts are permitted
under copyright law.


As users of video devices we agreed to their license
agreement when we opened the package, installing on
our system and what ever else.

What the developers are trying to do is achieve
interoperability with other programs. The other
programs being everything under the sun as far as
Linux, BSD, or what ever OS under the sun go. Nice big
hole eh?

But wait there's more!

Protection of minors (section 1201(h))
Protection of minors (section 1201(h)). This exception
allows a court applying the prohibition to a component
or part to consider the necessity for its
incorporation in technology that prevents access of
minors to material on the Internet.

So as a minor if their ATI card isn't working they
should be permitted to reverse engineer so they can
get on the internet? Cool!


It gets better!
Personal privacy (section 1201(i)). This exception
permits circumvention when the technological measure,
or the work it protects, is capable of collecting or
disseminating personally identifying information about
the online activities of a natural person.

Hey, those guys across the street have a gizmo that
can read what's  on my monitor (Yes, monitors produce
useable radio waves and there's been hints of
technology that can read those and potentially expose
your private information). So come on you developers,
make it so my ATI card works in such a way that the
radio waves are scrambled, yet my picture remains
crystal clear. And I cause use TV in, TV out, and
everthing else my spiffy card uses.

And best of all!
Security testing (section 1201(j)). This exception
permits circumvention of access control measures, and
the development of technological means for such
circumvention, for the purpose of testing the security
of a computer, computer system or computer network,
with the authorization of its owner or operator.

Okay developers, make some drivers that work better
than ATI's because I'm concerned about my security.
And (deity of choice) knows that I need to be secure
on my computer because I do not need some nutter
breaking in to my video drivers and seeing what I'm
doing.

Yay for the exceptions.



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Rune Petersen wrote:
> partly because of my illness

Condolences.
Hope it's nothing serious...

> but mostly because I lack the knowledge to understand what
> effects the different parameters has on the output. progress is usually
> done by poking at the code and see if it helped.

I can say so much that the current patch doesn't work for me with a
flatscreen and a TV.
If I use IgnoreEDID to force the refresh to 50Hz, then X won't start:

(II) RADEON(0): Not using default mode "<X>x<Y>" (bad mode
clock/interlace/doublescan)
(WW) RADEON(0): Mode pool is empty
(EE) RADEON(0): No valid mode found for this DFP/LCD
(EE) Screen(s) found, but none have a usable configuration.

If IgnoreEDID is disabled, then the output to the TV is out of sync.
Probably driven at 60Hz.

> A very depressing way
> to work when you don't have the necessary equipment.

Indeed.  (Equipment?)

El S=E1bado, 15 de Abril de 2006 23:02, Rune Petersen escribi=F3:
> There is no real progress on tv_output from me, partly because of my
> illness but mostly because I lack the knowledge to understand what
> effects the different parameters has on the output. progress is usually
> done by poking at the code and see if it helped. A very depressing way
> to work when you don't have the necessary equipment.


Hi.

These are indeed sad news. I was hoping to make it work somehow, but I'll h=
ave=20
to do with what I have now. Perhaps if you give me some hints about things =
I=20
can (easily) try, I could make some attempt. Something like changing a=20
#define or similar. It takes about 1 hour to compile x.org 6.9, so I can ma=
ke=20
some try from time to time. Who knows, perhaps x.org 7.1 will provide more=
=20
features.

Anyway, thanks for your work.

	Alberto

Alberto Hernando wrote:
> I've been trying the patch from http://megahurts.dk/rune/tv_output.html t=
o
> make work my radeon igp-9100 card. The tv output, I mean. Until now, I ha=
ve
> had no success. There is image, but it's out of sync.

I have the same problem with a different Radeon card.

> I've been searching in the web, but there is no info about work in progre=
ss.

Developers are scared of the DMCA, so no work is being done.

(Short story: Making TV output work is considered 'circumventing a
copy-protection device'.)

(Long story: ATI is not making documentation available that would
enable developers to get Macrovision working.  Since the hardware has
Macrovision support, enabling TV output without it would constitute
'circumventing copy-protection'.)

> And if there is something in the cvs, there is no instructions to grab ne=
w versions.
> I'm not a programmer. Using cvs might sound trivial, but it isn't for me.

Using CVS is not the hard part, you'll get the hang of that in no time.
Making Xorg compile in your particular build environment is probably
the hard part.
You could use Gentoo, where the build environment is setup to compile
X on your PC already.  And it probably should work on other distros
too, but no guarantees - you'll have to try.

But didn't you just say that you were actively using the patch to
drive (out of sync though) your TV output?

> Until now, I'm using the closed ati drivers. I get tv-out, but no dri

Plus it has various bugs that goes unfixed for months and months.

> So, if there something that a simple user can go to help, I'd like to kno=
w.

The current TV output patch *should* work for basic TV output,
although it doesn't work for me either.

IMO what you'll get if you do make it work is horrible, compared to
what your card can do and will do with Windows + Catalyst drivers +
PowerStrip.

We could perhaps create a bounty for making proper TV output for
Radeon cards, and someone in a country with less braindamaged laws
could get the patch up to speed wrt. the features available on
Windows.

I don't know if merging the patch with Xorg sources and getting it
properly distributed would be a problem then.  Probably.

Another way around the defect-by-design copyright protection and the
demented laws that protects it is to use Nvidia hardware.  I think TV
output works fine with that.  Don't know if the developers have
dinosaur balls, or if Nvidia has just ripped copy protection from the
hardware entirely, or what's going on there, but I think it works.=20
Haven't tried it though.  But it's probably much easier just to switch
hardware than to fix the Xorg drivers :-).

(And that is, by the way, exactly what I'm planning to do, once I
figure out if I'm correct and TV output does work on Nvidia...)

Hi,

There is no real progress on tv_output from me, partly because of my 
illness but mostly because I lack the knowledge to understand what 
effects the different parameters has on the output. progress is usually 
done by poking at the code and see if it helped. A very depressing way 
to work when you don't have the necessary equipment.

I have requested reading recommendations and notes from different people 
but nothing have materialized.

If someone knows of some good reading material I would be grateful.


Rune Petersen

Alberto Hernando wrote:
> Hi.
> 
> I've been trying the patch from http://megahurts.dk/rune/tv_output.html to 
> make work my radeon igp-9100 card. The tv output, I mean. Until now, I have 
> had no success. There is image, but it's out of sync. I've been searching in 
> the web, but there is no info about work in progress. And if there is 
> something in the cvs, there is no instructions to grab new versions. I'm not 
> a programmer. Using cvs might sound trivial, but it isn't for me. Until now, 
> I'm using the closed ati drivers. I get tv-out, but no dri, and I'd like 
> both. So, if there something that a simple user can go to help, I'd like to 
> know.
> 
> 	Alberto
> 

Hi.


>
> Developers are scared of the DMCA, so no work is being done.
>
> (Short story: Making TV output work is considered 'circumventing a
> copy-protection device'.)
>
> (Long story: ATI is not making documentation available that would
> enable developers to get Macrovision working.  Since the hardware has
> Macrovision support, enabling TV output without it would constitute
> 'circumventing copy-protection'.)

Hmm... I don't live in the US, so I'm not very aware of these things. But I 
thought that as it was nearly working, there wouldn't be any trouble in 
improving it.


>
> Using CVS is not the hard part, you'll get the hang of that in no time.
> Making Xorg compile in your particular build environment is probably
> the hard part.

I'm trying in a LFS environment. Actually, I have 2 partitions in the box. One 
with debian sarge and ati drivers, and the other with the LFS and gatos, for 
testing.

>
> But didn't you just say that you were actively using the patch to
> drive (out of sync though) your TV output?

I'm trying. And I'd really love to make it work. But there is the sync issue. 
Rune Peterson game me some hints that I could try, but...

>
> > Until now, I'm using the closed ati drivers. I get tv-out, but no dri
>
> Plus it has various bugs that goes unfixed for months and months.

Yes, there first versions I tried caused image corruption after some time of 
using it. 


>
> IMO what you'll get if you do make it work is horrible, compared to
> what your card can do and will do with Windows + Catalyst drivers +
> PowerStrip.

Horrible or not, I'm sure it will be better than what I have now. But I can't 
compare to what I get in windows... because it's a linux-only machine. I use 
it for Freevo (freevo.sf.net).

>
> Another way around the defect-by-design copyright protection and the
> demented laws that protects it is to use Nvidia hardware.  I think TV
> output works fine with that.  Don't know if the developers have
> dinosaur balls, or if Nvidia has just ripped copy protection from the
> hardware entirely, or what's going on there, but I think it works.
> Haven't tried it though.  But it's probably much easier just to switch
> hardware than to fix the Xorg drivers :-).

Not in my case :( The machine is an asus pundit-r, a barebone, and the graphic 
chipset is in the motherboard.

Looks like I'll have to wait a bit more.

Thanks

	Alberto

Hi.

I've been trying the patch from http://megahurts.dk/rune/tv_output.html to 
make work my radeon igp-9100 card. The tv output, I mean. Until now, I have 
had no success. There is image, but it's out of sync. I've been searching in 
the web, but there is no info about work in progress. And if there is 
something in the cvs, there is no instructions to grab new versions. I'm not 
a programmer. Using cvs might sound trivial, but it isn't for me. Until now, 
I'm using the closed ati drivers. I get tv-out, but no dri, and I'd like 
both. So, if there something that a simple user can go to help, I'd like to 
know.

	Alberto

        I am interested in obtaining detailed programming information
on the "avivo" series of graphics chips sold by ATI in their x1000
series products, which I understand is different from the radeon
engine that the gatos project develops for.

        I hope to write X and v4l output drivers for the x1000 (long
ago I used to write X server drivers professionally).  If anybody on
this list could point me to the information or to the right people, I
would appreciate it.  Also, if anyone has already started work on
this or wants me to let them know what I find out, I would be happy
to cooperate.

        I am aware of the vesafb-tng kernel patch (although I have
not yet tried it), but I would like to at least be able to add
blit support and a hardware scalable video window.  Even if the
card is on a pci-express x16 interface, playing 60 frames per
second on a 2560x1600 display (haven't bought it yet) at 32 bits
per pixel would be almost 1 gigabyte per second of bus bandwidth.

        Thanks in advance for any information.

Adam Richter

T24gMy8yMi8wNiwgTWlrZSBLZWxseSA8cGlvdG8wMUBnbWFpbC5jb20+IHdyb3RlOgo+IElzIGl0
IHBvc3NpYmxlIHRoZSBpbi1rZXJuZWwgcmFkZW9uLXRuZyBmcmFtZWJ1ZmZlciBpcyBpbnRlcmZl
cmluZyBpbiBzb21lIHdheT8KClllcywgSSd2ZSBmb3VuZCB0aGF0IHRoaXMgaXMgdGhlIHByb2Js
ZW0uIE5vdyBJIGNhbiBnZXQgYSBwaWN0dXJlCihhbGJpZXQgb25seSBibGFjayBhbmQgd2hpdGUg
YW5kIHcvbyBzb3VuZCkuIFNvLCBpdCB3b3Jrcy4gSXMgdGhlcmUKYW55dGhpbmcgSSBjYW4gZG8g
dG8gaGVscCB3aXRoIGdldHRpbmcgc291bmQsIGNoYW5uZWwgY2hhbmdpbmcsCmNoYW5naW5nIHRv
IGNvbXBvc2l0ZSBpbnB1dCwgZXRjIHRvIHdvcmsgcmlnaHQgd2l0aCBteSBBaVcgOTAwMCBQcm8/
CgpJZiBpdCBpc24ndCB5ZXQgaW1wbGVtZW50ZWQsIGFyZSB0aGVyZSBzb21lIHByb2dyYW1zIEkg
Y2FuIHJ1biB0byBnZXQKdXNlZnVsIGluZm9ybWF0aW9uIGZvciB0aGUgZGV2ZWxvcGVycz8KCi0t
Ck1pa2UgS2VsbHkKIkhhcHBpbmVzcyBhZGRzIGFuZCBtdWx0aXBsaWVzIGFzIHdlIGRpdmlkZSBp
dCB3aXRoIG90aGVycy4iCg==

>
>
>
>Actually, the patch is for ``CVS'' of the Xorg 7, which is newer than the one (release version) you downloaded.
>I try to make a patch for version 6.5.7.3, you might want to give it a try:
>
>http://shell.world-net.co.nz/~knightw/tvout/7/xf86-video-ati-X11R7.0-6.5.7.3-tvout.patch.gz
>
>  
>
The Patch works an I can use the X server without the TVOutput Option. 
But when I try to use it with the TVOutput "PAL" Option, the display and 
the TV will stay black and the X server needs 98% of the CPU time.
Maybe I will try it with Xorg6.9 the next days.

Thank you for your fast answer,

Gabriel Huber

Hi,

> I tried to patch the xorg7.0 ati drivers to get the tv_ouput to work with my old Apple IBook 600MHZ with the ubuntu dapper 6.06 development version.
> I tried it with the package:
> http://xorg.freedesktop.org/releases/X11R7.0/src/driver/xf86-video-ati-X11R7.0-6.5.7.3.tar.bz2
> 
> I tried to use the
> http://shell.world-net.co.nz/~knightw/xorg7/xorg7_CVS-20060402-tv_output.patch.gz
> Patch, but it didn't work. The following output was printed out:

Actually, the patch is for ``CVS'' of the Xorg 7, which is newer than the one (release version) you downloaded.
I try to make a patch for version 6.5.7.3, you might want to give it a try:

http://shell.world-net.co.nz/~knightw/tvout/7/xf86-video-ati-X11R7.0-6.5.7.3-tvout.patch.gz


> 
> # patch -p1 -d xf86-video-ati-X11R7.0-6.5.7.3 < xorg7_CVS-20060402-tv_output.patch
> 
> 1 out of 21 hunks FAILED -- saving rejects to file src/radeon_driver.c.rej
> 

You see, there is a failed patch hunk, I consider it won't even compile in this situation.

> I also tried it with the patch:
> http://megahurts.dk/rune/stuff/xorg_CVS-20051214-tv_output.patch.gz
> Therefor, I copied the Imakefile form the xorg6.9 to the 
> xf86-video-ati-X11R7.0-6.5.7.3/src directory, to get the patch work.
> > 
> Since then I couldn't start the X server anymore.
> It fails with an segmentation fault, after loading the module theater_out.so.
> The problem therefor seems to be in line 2341:
> b->ioctl(b , GB_IOCTL_GET_TYPE , 20 , s);
> The variable b seems to be null.

One of the differences of the patch that I made over the patch for Xorg 6.9 series, is that, 
there is a null pointer passing somewhere in the driver.c or somewhere I can't recall right now. And hence
it is normal you have got the error message like this.

> 
> Maybe anyone can use these informations or tell me what is wrong.
> 

Try the patch for driver version 6.5.7.3 as I just mentioned, see how it goes.

Best Regards,

Wei-Tsun Sun

Hi,

I tried to patch the xorg7.0 ati drivers to get the tv_ouput to work with my old Apple IBook 600MHZ with the ubuntu dapper 6.06 development version.
I tried it with the package:
http://xorg.freedesktop.org/releases/X11R7.0/src/driver/xf86-video-ati-X11R7.0-6.5.7.3.tar.bz2

I tried to use the
http://shell.world-net.co.nz/~knightw/xorg7/xorg7_CVS-20060402-tv_output.patch.gz
Patch, but it didn't work. The following output was printed out:

# patch -p1 -d xf86-video-ati-X11R7.0-6.5.7.3 < xorg7_CVS-20060402-tv_output.patch

patching file src/Makefile.am
Hunk #1 succeeded at 91 (offset -4 lines).
Hunk #2 succeeded at 193 (offset -4 lines).
patching file src/radeon_driver.c
Hunk #1 succeeded at 72 (offset -4 lines).
Hunk #2 succeeded at 182 (offset -7 lines).
Hunk #3 succeeded at 246 (offset -9 lines).
Hunk #4 succeeded at 5472 (offset -253 lines).
Hunk #5 FAILED at 5938.
Hunk #6 succeeded at 5914 (offset -495 lines).
Hunk #7 succeeded at 5998 (offset -502 lines).
Hunk #8 succeeded at 6167 (offset -517 lines).
Hunk #9 succeeded at 6232 (offset -517 lines).
Hunk #10 succeeded at 6313 (offset -517 lines).
Hunk #11 succeeded at 6707 (offset -543 lines).
Hunk #12 succeeded at 6778 (offset -543 lines).
Hunk #13 succeeded at 6788 (offset -543 lines).
Hunk #14 succeeded at 6896 (offset -545 lines).
Hunk #15 succeeded at 6948 (offset -545 lines).
Hunk #16 succeeded at 7682 (offset -563 lines).
Hunk #17 succeeded at 8030 (offset -566 lines).
Hunk #18 succeeded at 8096 (offset -567 lines).
Hunk #19 succeeded at 8178 with fuzz 2 (offset -567 lines).
Hunk #20 succeeded at 8251 (offset -569 lines).
Hunk #21 succeeded at 9603 (offset -611 lines).
1 out of 21 hunks FAILED -- saving rejects to file src/radeon_driver.c.rej
patching file src/radeon.h
Hunk #1 succeeded at 64 (offset 1 line).
Hunk #2 succeeded at 224 (offset -3 lines).
Hunk #3 succeeded at 631 (offset -14 lines).
Hunk #4 succeeded at 726 (offset -19 lines).
Hunk #5 succeeded at 739 (offset -19 lines).
Hunk #6 succeeded at 778 (offset -19 lines).
patching file src/radeon_reg.h
Hunk #1 succeeded at 1207 (offset -16 lines).
patching file src/radeon_video.c
Hunk #1 succeeded at 77 (offset -5 lines).
Hunk #2 succeeded at 120 (offset -5 lines).
Hunk #3 succeeded at 156 (offset -5 lines).
Hunk #4 succeeded at 260 (offset -5 lines).
Hunk #5 succeeded at 278 (offset -5 lines).
Hunk #6 succeeded at 1091 (offset -5 lines).
Hunk #7 succeeded at 1106 (offset -5 lines).
Hunk #8 succeeded at 1320 (offset -5 lines).
Hunk #9 succeeded at 1448 (offset -5 lines).
Hunk #10 succeeded at 1533 (offset -5 lines).
Hunk #11 succeeded at 1571 (offset -5 lines).
Hunk #12 succeeded at 1894 (offset -5 lines).
Hunk #13 succeeded at 2018 (offset -5 lines).
patching file src/radeon_video.h
patching file src/radeon_vip.c
Hunk #1 succeeded at 340 (offset -2 lines).
Hunk #2 succeeded at 349 (offset -2 lines).
patching file src/README.tvout
patching file src/theater_out.c
patching file src/theater_out.h
patching file src/theater_out_module.c
patching file src/tvo_set/Imakefile
patching file src/tvo_set/tvo_set.c

#

I also tried it with the patch:
http://megahurts.dk/rune/stuff/xorg_CVS-20051214-tv_output.patch.gz
Therefor, I copied the Imakefile form the xorg6.9 to the 
xf86-video-ati-X11R7.0-6.5.7.3/src directory, to get the patch work.

After that, I added the following line 65 to configure.ac:
PKG_CHECK_MODULES(TVO_SET, xv x11)

Changed the line 184 of configure.ac:
AC_OUTPUT([
      Makefile
      src/Makefile
      man/Makefile
      src/tvo_set/Makefile
])

Added the following lines in line 102 at src/Makefile.am:
theater_out_la_LTLIBRARIES = theater_out.la
theater_out_la_LDFLAGS = -module -avoid-version
theater_out_ladir = @moduledir@/multimedia
theater_out_la_SOURCES = theater_out.c theater_out_module.c

Changed the following line 22 of Makefile.am
SUBDIRS = src man src/tvo_set

Wrote the file src/tvoset/Makefile.am:
bin_PROGRAMS = tvo_set
tvo_set_SOURCES = tvo_set.c
tvo_set_LDADD = $(TVO_SET_LIBS)

After that, I run the commands:
aclocal-1.9
autoheader2.50
automake-1.9
autoconf2.50
./configure
make
make install

Since then I couldn't start the X server anymore.
It fails with an segmentation fault, after loading the module theater_out.so.
The problem therefor seems to be in line 2341:
b->ioctl(b , GB_IOCTL_GET_TYPE , 20 , s);
The variable b seems to be null.

Maybe anyone can use these informations or tell me what is wrong.

I uploaded the changed xf86-video-ati-X11R7.0-6.5.7.3.tar.bz2 package, with the changed Makefile.am files to
http://www.ghuber.de/xf86-video-ati-X11R7.0-6.5.7.3-tvout.tar.gz

Gabriel Huber

[Resending this with Xorg.log as link because attachment was too big]

Hi,

I noticed a few people on the list trying to get GATOS TV out to work with the 
(PPC) Mac Mini without much success...unfortunately I've not got very far 
either.

From what I can see, the driver hangs in readFifo(), while saving the timing 
tables during the theaterOutSave() call. The exit condition for the loop 
doesn't seem to ever occur:

       do
 	{
 	  ert_read(t , TV_HOST_RD_WT_CNTL , &tmp);
 	}
           while ((tmp & VIP_HOST_RD_WT_CNTL_RD_ACK) == 0);

Liberal splatterings of printfs reveal that the value in TV_HOST_RD_WT_CNTL 
never changes (after being initialised to
  addr | VIP_HOST_RD_WT_CNTL_RD).

Since this code seems to be only used to save the ERT state for later restore 
after leaving TV Out mode, I decided it didn't matter too much and commented 
out the call to theaterOutSave in radeon_driver.c. This seem to fix the hanging 
problem, and X continued to start up successfully.

However, the TV only shows flickery black and white lines (there clearly is a 
signal coming out of the composite/s-video adaptor, but it is garbage). I've 
tried various modelines, but to no avail.

I just wondered if anyone else has any idea how to get this working? 
(xorg.conf is attached, and Xorg.log is here: 
http://www.holgate.org.uk/Xorg.0.log.txt - I've added some debugging to 
dump the register address space, not sure if it's any help).

Many thanks in advance, and thanks for writing the code in the first place 
:)

cheers,
Matt.

Does GATOS support NetBSD 3.0?

Please CC all replies