From: Steven N. <s_j...@ya...> - 2005-06-06 15:28:54
|
--- s_j...@ya... <s_j...@ya...> wrote: > =?iso-8859-1?B?SSByZWFsaXNlIHRoaXMgaXMgc2xpZ2h0bHkgb2ZmIHRvcGljLCBidXQgSSBmaWd1cmVkIG91dHNpZGUgb2YgQVRJIEknZCBtb3N0DQ==?= > =?iso-8859-1?B?bGlrZWx5IGZpbmQgc29tZW9uZSBoZXJlIHdobyBrbm93cy4gSSd2ZSByZWFkIHRoYXQgdGhlIFdpbmRvd3MgZHJpdmVyIGFsbG93cw0=?= > =?iso-8859-1?B?Y29tcG9uZW50IHZpZGVvIG91dHB1dCBmb3IgY29ubmVjdGlvbiB0byBUVnMsIHByb2plY3RvcnMgZXRjLiBEb2VzIGFueW9uZSBrbm93DQ==?= > =?iso-8859-1?B?d2hhdCByZWdpc3RlcnMgbmVlZCB0byBiZSBzZXQgdG8gd2hhdCB0byBlbmFibGUgdGhpcyBtb2RlPyBJIG5lZWQgdGhlIHN5bmMgb24gWQ0=?= > =?iso-8859-1?B?dG9vLiBJJ3ZlIGJlZW4gc2V0dGluZyByYW5kb20gcmVnaXN0ZXJzIGJ1dCBoYXZlbid0IGV2ZW4gbWFuYWdlZCBzeW5jIG9uIGdyZWVuLg0=?= > =?iso-8859-1?B?DSAg?= > =?iso-8859-1?B?DSAg?= > =?iso-8859-1?B?U3RldmUN?= > =?iso-8859-1?B?DSAg?= > =?iso-8859-1?B?DSAg?= > =?iso-8859-1?B?CQkN?= > =?iso-8859-1?B?X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18gDQ==?= > =?iso-8859-1?B?SG93IG11Y2ggZnJlZSBwaG90byBzdG9yYWdlIGRvIHlvdSBnZXQ/IFN0b3JlIHlvdXIgaG9saWRheSAN?= > =?iso-8859-1?B?c25hcHMgZm9yIEZSRUUgd2l0aCBZYWhvbyEgUGhvdG9zIGh0dHA6Ly91ay5waG90b3MueWFob28uY29tDQ==?= Steve ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com |
From: Vladimir D. <vo...@mi...> - 2005-06-10 01:42:01
|
There is an option "composite_sync" - take a look there. As for Y Cb Cr, I would expect this is implemented as some sort of transform before output. I.e. the chip still thinks it is outputting R, G, B, just weird R G B values. In particular take a look at how gamma support is implemented in the Radeon driver for newer chipsets, it might shed some clues. best Vladimir Dergachev On Mon, 6 Jun 2005, Steven Newbury wrote: > --- s_j...@ya... <s_j...@ya...> wrote: >> > =?iso-8859-1?B?SSByZWFsaXNlIHRoaXMgaXMgc2xpZ2h0bHkgb2ZmIHRvcGljLCBidXQgSSBmaWd1cmVkIG91dHNpZGUgb2YgQVRJIEknZCBtb3N0DQ==?= >> > =?iso-8859-1?B?bGlrZWx5IGZpbmQgc29tZW9uZSBoZXJlIHdobyBrbm93cy4gSSd2ZSByZWFkIHRoYXQgdGhlIFdpbmRvd3MgZHJpdmVyIGFsbG93cw0=?= >> > =?iso-8859-1?B?Y29tcG9uZW50IHZpZGVvIG91dHB1dCBmb3IgY29ubmVjdGlvbiB0byBUVnMsIHByb2plY3RvcnMgZXRjLiBEb2VzIGFueW9uZSBrbm93DQ==?= >> > =?iso-8859-1?B?d2hhdCByZWdpc3RlcnMgbmVlZCB0byBiZSBzZXQgdG8gd2hhdCB0byBlbmFibGUgdGhpcyBtb2RlPyBJIG5lZWQgdGhlIHN5bmMgb24gWQ0=?= >> > =?iso-8859-1?B?dG9vLiBJJ3ZlIGJlZW4gc2V0dGluZyByYW5kb20gcmVnaXN0ZXJzIGJ1dCBoYXZlbid0IGV2ZW4gbWFuYWdlZCBzeW5jIG9uIGdyZWVuLg0=?= >> =?iso-8859-1?B?DSAg?= >> =?iso-8859-1?B?DSAg?= >> =?iso-8859-1?B?U3RldmUN?= >> =?iso-8859-1?B?DSAg?= >> =?iso-8859-1?B?DSAg?= >> =?iso-8859-1?B?CQkN?= >> > =?iso-8859-1?B?X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18gDQ==?= >> > =?iso-8859-1?B?SG93IG11Y2ggZnJlZSBwaG90byBzdG9yYWdlIGRvIHlvdSBnZXQ/IFN0b3JlIHlvdXIgaG9saWRheSAN?= >> > =?iso-8859-1?B?c25hcHMgZm9yIEZSRUUgd2l0aCBZYWhvbyEgUGhvdG9zIGh0dHA6Ly91ay5waG90b3MueWFob28uY29tDQ==?= > > > Steve > > > > > > ___________________________________________________________ > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com |
From: Alex D. <ale...@gm...> - 2005-06-10 13:05:40
|
You may also want to take a look at my unfinished radeon tv-out patch: http://www.botchco.com/alex/xorg/radeon_tvout.c http://www.botchco.com/alex/xorg/radeon_tvout.h http://www.botchco.com/alex/xorg/radeon_tvout.diff one of the regs (DAC2 I think) has an option to be sourced to either a crtc or directly to the linear transform unit. Alex On 6/9/05, Vladimir Dergachev <vo...@mi...> wrote: >=20 > There is an option "composite_sync" - take a look there. >=20 > As for Y Cb Cr, I would expect this is implemented as some sort of > transform before output. I.e. the chip still thinks it is outputting R, G= , > B, just weird R G B values. >=20 > In particular take a look at how gamma support is implemented in the > Radeon driver for newer chipsets, it might shed some clues. >=20 > best >=20 > Vladimir Dergachev >=20 >=20 > On Mon, 6 Jun 2005, Steven Newbury wrote: >=20 > > --- s_j...@ya... <s_j...@ya...> wrote: > >> > > =3D?iso-8859-1?B?SSByZWFsaXNlIHRoaXMgaXMgc2xpZ2h0bHkgb2ZmIHRvcGljLCBidX= QgSSBmaWd1cmVkIG91dHNpZGUgb2YgQVRJIEknZCBtb3N0DQ=3D=3D?=3D > >> > > =3D?iso-8859-1?B?bGlrZWx5IGZpbmQgc29tZW9uZSBoZXJlIHdobyBrbm93cy4gSSd2ZS= ByZWFkIHRoYXQgdGhlIFdpbmRvd3MgZHJpdmVyIGFsbG93cw0=3D?=3D > >> > > =3D?iso-8859-1?B?Y29tcG9uZW50IHZpZGVvIG91dHB1dCBmb3IgY29ubmVjdGlvbiB0by= BUVnMsIHByb2plY3RvcnMgZXRjLiBEb2VzIGFueW9uZSBrbm93DQ=3D=3D?=3D > >> > > =3D?iso-8859-1?B?d2hhdCByZWdpc3RlcnMgbmVlZCB0byBiZSBzZXQgdG8gd2hhdCB0by= BlbmFibGUgdGhpcyBtb2RlPyBJIG5lZWQgdGhlIHN5bmMgb24gWQ0=3D?=3D > >> > > =3D?iso-8859-1?B?dG9vLiBJJ3ZlIGJlZW4gc2V0dGluZyByYW5kb20gcmVnaXN0ZXJzIG= J1dCBoYXZlbid0IGV2ZW4gbWFuYWdlZCBzeW5jIG9uIGdyZWVuLg0=3D?=3D > >> =3D?iso-8859-1?B?DSAg?=3D > >> =3D?iso-8859-1?B?DSAg?=3D > >> =3D?iso-8859-1?B?U3RldmUN?=3D > >> =3D?iso-8859-1?B?DSAg?=3D > >> =3D?iso-8859-1?B?DSAg?=3D > >> =3D?iso-8859-1?B?CQkN?=3D > >> > > =3D?iso-8859-1?B?X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX1= 9fX19fX19fX19fX19fX19fX18gDQ=3D=3D?=3D > >> > > =3D?iso-8859-1?B?SG93IG11Y2ggZnJlZSBwaG90byBzdG9yYWdlIGRvIHlvdSBnZXQ/IF= N0b3JlIHlvdXIgaG9saWRheSAN?=3D > >> > > =3D?iso-8859-1?B?c25hcHMgZm9yIEZSRUUgd2l0aCBZYWhvbyEgUGhvdG9zIGh0dHA6Ly= 91ay5waG90b3MueWFob28uY29tDQ=3D=3D?=3D > > > > > > Steve > > > > > > > > > > > > ___________________________________________________________ > > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with vo= icemail http://uk.messenger.yahoo.com >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you sho= tput > a projector? How fast can you ride your desk chair down the office luge t= rack? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20 > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel > |
From: Steven N. <s_j...@ya...> - 2005-08-05 11:16:42
|
--- Alex Deucher <ale...@gm...> wrote: > You may also want to take a look at my unfinished radeon tv-out patch: > > http://www.botchco.com/alex/xorg/radeon_tvout.c > http://www.botchco.com/alex/xorg/radeon_tvout.h > http://www.botchco.com/alex/xorg/radeon_tvout.diff > > one of the regs (DAC2 I think) has an option to be sourced to either a > crtc or directly to the linear transform unit. > > Alex > > On 6/9/05, Vladimir Dergachev <vo...@mi...> wrote: > > > > There is an option "composite_sync" - take a look there. > > > > As for Y Cb Cr, I would expect this is implemented as some sort of > > transform before output. I.e. the chip still thinks it is outputting R, G, > > B, just weird R G B values. > > > > In particular take a look at how gamma support is implemented in the > > Radeon driver for newer chipsets, it might shed some clues. OK. I've finally got the time (and Internet connection!) to look at this again, but I need some more help. The "composite_sync" option only seems to relate to old hw like mach64. The register it toggles is listed as 0x100 in atiregs.h but is missing from radeon_reg.h. I've tried poking around but haven't managed to find anything that works as yet. I know the TV will sync to a VGA composite signal just the colours will be very wrong, the Sony PS2 _only_ outputs in composite sync and I've played around with that quite a bit. Alex, I'm sure your approach is the likely to be correct but I don't really know where to go from here. Should I just keep trying to set random registers or do you have some idea what I should do? I did notice in your tvout patch: #define RADEON_TV_DAC_CNTL 0x088c -# define RADEON_TV_DAC_STD_MASK 0x0300 +# define RADEON_TV_DAC_BLANK (1 << 0) +# define RADEON_TV_DAC_HOLD (1 << 1) +# define RADEON_TV_DAC_PEDESTAL (1 << 2) +# define RADEON_TV_MONITOR_DETECT_EN (1 << 4) +# define RADEON_TV_DAC_CMPOUT (1 << 5) <-- related? # define RADEON_TV_DAC_BGSLEEP (1 << 6) +# define RADEON_TV_DAC_STD_MASK 0x0300 +# define RADEON_TV_DAC_STD_NTSC (1 << 8) # define RADEON_TV_DAC_RDACPD (1 << 24) # define RADEON_TV_DAC_GDACPD (1 << 25) # define RADEON_TV_DAC_BDACPD (1 << 26) Could RADEON_TV_DAC_CMPOUT be related to composite output or is it only for the TV-out encoder hardware? Any help would be greatly appreciated, at the moment I'm forced to use the vesa driver in order to at least use s-video out to get any picture at all, it doesn't work well, no video scaling/colour conversion, no 3D or even 2D acceleration etc etc. TV-out would be better than what I have right now but I'd really like to get it working with components, it should be easier anyway, no? Steve ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com |
From: Alex D. <ale...@gm...> - 2005-08-05 13:17:02
|
On 8/5/05, Steven Newbury <s_j...@ya...> wrote: >=20 > --- Alex Deucher <ale...@gm...> wrote: >=20 > > You may also want to take a look at my unfinished radeon tv-out patch: > > > > http://www.botchco.com/alex/xorg/radeon_tvout.c > > http://www.botchco.com/alex/xorg/radeon_tvout.h > > http://www.botchco.com/alex/xorg/radeon_tvout.diff > > > > one of the regs (DAC2 I think) has an option to be sourced to either a > > crtc or directly to the linear transform unit. > > > > Alex > > > > On 6/9/05, Vladimir Dergachev <vo...@mi...> wrote: > > > > > > There is an option "composite_sync" - take a look there. > > > > > > As for Y Cb Cr, I would expect this is implemented as some sort of > > > transform before output. I.e. the chip still thinks it is outputting = R, G, > > > B, just weird R G B values. > > > > > > In particular take a look at how gamma support is implemented in the > > > Radeon driver for newer chipsets, it might shed some clues. >=20 > OK. I've finally got the time (and Internet connection!) to look at this > again, but I need some more help. >=20 > The "composite_sync" option only seems to relate to old hw like mach64. = The > register it toggles is listed as 0x100 in atiregs.h but is missing from > radeon_reg.h. I've tried poking around but haven't managed to find anyth= ing > that works as yet. I know the TV will sync to a VGA composite signal jus= t the > colours will be very wrong, the Sony PS2 _only_ outputs in composite sync= and > I've played around with that quite a bit. >=20 > Alex, I'm sure your approach is the likely to be correct but I don't real= ly > know where to go from here. Should I just keep trying to set random regi= sters > or do you have some idea what I should do? Unforunately, most of the tv-out and compoent out is undocumented, or we have limited documentation, but no real guid as to how everything needs to be programmed. One of the Gatos guys got regular tv-out working and Rune Peterson keeps a relatively up to date tv-out patch here: http://megahurts.dk/rune/tv_output.html that might be of some help. >=20 > I did notice in your tvout patch: > #define RADEON_TV_DAC_CNTL 0x088c > -# define RADEON_TV_DAC_STD_MASK 0x0300 > +# define RADEON_TV_DAC_BLANK (1 << 0) > +# define RADEON_TV_DAC_HOLD (1 << 1) > +# define RADEON_TV_DAC_PEDESTAL (1 << 2) > +# define RADEON_TV_MONITOR_DETECT_EN (1 << 4) > +# define RADEON_TV_DAC_CMPOUT (1 << 5) <-- related? > # define RADEON_TV_DAC_BGSLEEP (1 << 6) > +# define RADEON_TV_DAC_STD_MASK 0x0300 > +# define RADEON_TV_DAC_STD_NTSC (1 << 8) > # define RADEON_TV_DAC_RDACPD (1 << 24) > # define RADEON_TV_DAC_GDACPD (1 << 25) > # define RADEON_TV_DAC_BDACPD (1 << 26) >=20 > Could RADEON_TV_DAC_CMPOUT be related to composite output or is it only f= or the > TV-out encoder hardware? I'm not sure. On the newer r4xx hardware component output is handled by the tv-encoder. I'm not sure how it worked on older hardware. >=20 > Any help would be greatly appreciated, at the moment I'm forced to use th= e vesa > driver in order to at least use s-video out to get any picture at all, it > doesn't work well, no video scaling/colour conversion, no 3D or even 2D > acceleration etc etc. TV-out would be better than what I have right now = but > I'd really like to get it working with components, it should be easier an= yway, no? Not really. Ati hasn't released any information about setting up the chip for component output. Perhaps you can dump the radeon registers in windows and compare how that driver sets things up, or perhaps the fglrx driver supports component out too and you could use the register dump tools from the r300 project. Alex >=20 > Steve > |
From: Steven N. <s_j...@ya...> - 2005-08-05 13:40:24
|
Thanks for the quick reply. --- Alex Deucher <ale...@gm...> wrote: > On 8/5/05, Steven Newbury <s_j...@ya...> wrote: > > > > --- Alex Deucher <ale...@gm...> wrote: > > > > > You may also want to take a look at my unfinished radeon tv-out patch: > > > > > > http://www.botchco.com/alex/xorg/radeon_tvout.c > > > http://www.botchco.com/alex/xorg/radeon_tvout.h > > > http://www.botchco.com/alex/xorg/radeon_tvout.diff > > > > > > one of the regs (DAC2 I think) has an option to be sourced to either a > > > crtc or directly to the linear transform unit. > > > > > > Alex > > > > > > On 6/9/05, Vladimir Dergachev <vo...@mi...> wrote: > > > > > > > > There is an option "composite_sync" - take a look there. > > > > > > > > As for Y Cb Cr, I would expect this is implemented as some sort of > > > > transform before output. I.e. the chip still thinks it is outputting R, > G, > > > > B, just weird R G B values. > > > > > > > > In particular take a look at how gamma support is implemented in the > > > > Radeon driver for newer chipsets, it might shed some clues. > > > > OK. I've finally got the time (and Internet connection!) to look at this > > again, but I need some more help. > > > > The "composite_sync" option only seems to relate to old hw like mach64. > The > > register it toggles is listed as 0x100 in atiregs.h but is missing from > > radeon_reg.h. I've tried poking around but haven't managed to find > anything > > that works as yet. I know the TV will sync to a VGA composite signal just > the > > colours will be very wrong, the Sony PS2 _only_ outputs in composite sync > and > > I've played around with that quite a bit. > > > > Alex, I'm sure your approach is the likely to be correct but I don't really > > know where to go from here. Should I just keep trying to set random > registers > > or do you have some idea what I should do? > > Unforunately, most of the tv-out and compoent out is undocumented, or > we have limited documentation, but no real guid as to how everything > needs to be programmed. One of the Gatos guys got regular tv-out > working and Rune Peterson keeps a relatively up to date tv-out patch > here: > http://megahurts.dk/rune/tv_output.html > that might be of some help. I'll give that a go, at least I might be able to get an accelerated X server going. > > > > I did notice in your tvout patch: > > #define RADEON_TV_DAC_CNTL 0x088c > > -# define RADEON_TV_DAC_STD_MASK 0x0300 > > +# define RADEON_TV_DAC_BLANK (1 << 0) > > +# define RADEON_TV_DAC_HOLD (1 << 1) > > +# define RADEON_TV_DAC_PEDESTAL (1 << 2) > > +# define RADEON_TV_MONITOR_DETECT_EN (1 << 4) > > +# define RADEON_TV_DAC_CMPOUT (1 << 5) <-- related? > > # define RADEON_TV_DAC_BGSLEEP (1 << 6) > > +# define RADEON_TV_DAC_STD_MASK 0x0300 > > +# define RADEON_TV_DAC_STD_NTSC (1 << 8) > > # define RADEON_TV_DAC_RDACPD (1 << 24) > > # define RADEON_TV_DAC_GDACPD (1 << 25) > > # define RADEON_TV_DAC_BDACPD (1 << 26) > > > > Could RADEON_TV_DAC_CMPOUT be related to composite output or is it only for > the > > TV-out encoder hardware? > > I'm not sure. On the newer r4xx hardware component output is handled > by the tv-encoder. I'm not sure how it worked on older hardware. I've got an R200 and an RV280 which I've been experimenting with. Ideally I'd like to get the R200 working since it is by far the better card. > > > > > Any help would be greatly appreciated, at the moment I'm forced to use the > vesa > > driver in order to at least use s-video out to get any picture at all, it > > doesn't work well, no video scaling/colour conversion, no 3D or even 2D > > acceleration etc etc. TV-out would be better than what I have right now > but > > I'd really like to get it working with components, it should be easier > anyway, no? > > Not really. Ati hasn't released any information about setting up the > chip for component output. Perhaps you can dump the radeon registers > in windows and compare how that driver sets things up, or perhaps the > fglrx driver supports component out too and you could use the register > dump tools from the r300 project. > I'll check the docs for the fglrx driver see if it mentions anything. I know from reading various forums that under Windows the driver normally responds to a DDC id from the ATI component adaptor (VGA->component cable with a DDC chip built in), however people have found that by setting a registry key it's possible to get component out working with a standard RGB->component cable which is what I'm trying to use. So if all else fails I'll see if I can install a copy of Windows and get it working with component out. It seemed strange to me that I couldn't get regular VGA sync-on-green working though, it would/should have been enough for me to get some kind of output. I guess I just didn't toggle the right bit in the right register, judging by the fact that the driver doesn't support sync-on-green should I assume that it too is undocumented? Or is sync-on-green and composite sync the same thing in this case? My understanding was that composite sync meant that the H and V syncs were combined, while sync-on-green meant composite sync also combined with Green. Where as composite video was everything mixed all together with some kind of colour encoding such as PAL or NTSC and S-Video is like composite except that the colour encoding (chrominance) was carried on a separate wire. Steve ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
From: Steven N. <s_j...@ya...> - 2005-08-06 12:46:00
|
--- Alex Deucher <ale...@gm...> wrote: > Not really. Ati hasn't released any information about setting up the > chip for component output. Perhaps you can dump the radeon registers > in windows and compare how that driver sets things up, or perhaps the > fglrx driver supports component out too and you could use the register > dump tools from the r300 project. > Hi again! I'm going to have a go at getting Windows working with component out and get a register dump from it. Do you know where I could find a register dumper for Windows? Or should I try compiling http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/hy0/radeon_dump.tgz under Cygwin? Would that work? Steve ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com |
From: Alex D. <ale...@gm...> - 2005-08-06 17:32:10
|
On 8/6/05, Steven Newbury <s_j...@ya...> wrote: > --- Alex Deucher <ale...@gm...> wrote: >=20 > > Not really. Ati hasn't released any information about setting up the > > chip for component output. Perhaps you can dump the radeon registers > > in windows and compare how that driver sets things up, or perhaps the > > fglrx driver supports component out too and you could use the register > > dump tools from the r300 project. > > > Hi again! I'm going to have a go at getting Windows working with compone= nt out > and get a register dump from it. Do you know where I could find a regist= er > dumper for Windows? =20 I don't know off hand. >Or should I try compiling > http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/hy0/radeon_dump.tgz u= nder > Cygwin? Would that work? I've never tried. You can give it a shot and see what happens. Alex >=20 > Steve >=20 > |
From: Steven N. <s_j...@ya...> - 2005-08-07 18:31:17
|
I've managed to get my Radeon 8500 to work with YPbPr output under Windows. I did have a bit of trouble finding how to do it again, eventually found this thread on avsforum: http://www.avsforum.com/avs-vb/showthread.php?t=212199&page=1&pp=20 The picture quality is incomparable to s-video and the Windows driver only supports US HDTV standard output modes, while my TV also supports PAL type HDTV modes ie. 576p; hopefully this limitation will be gone if I can get this working with Xorg. It's worth noting that it does NOT work on all Radeon cards, specifically my 9200SE will not work in YPbPr mode. --- Alex Deucher <ale...@gm...> wrote: > On 8/6/05, Steven Newbury <s_j...@ya...> wrote: > > --- Alex Deucher <ale...@gm...> wrote: > > > > > Not really. Ati hasn't released any information about setting up the > > > chip for component output. Perhaps you can dump the radeon registers > > > in windows and compare how that driver sets things up, or perhaps the > > > fglrx driver supports component out too and you could use the register > > > dump tools from the r300 project. > > > > > Hi again! I'm going to have a go at getting Windows working with component > out > > and get a register dump from it. Do you know where I could find a register > > dumper for Windows? > > I don't know off hand. > > >Or should I try compiling > > http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/hy0/radeon_dump.tgz > under > > Cygwin? Would that work? > > I've never tried. You can give it a shot and see what happens. I've got it to compile, however to to open /dev/mem I had to change it to open it RDONLY, I don't why that would be, this is a default install of WinXP so my user account is running as "Administrator". I've now come to another problem, cygwin/nt5.1 doesn't have a /proc/bus/pci so radeon_dump is segfaulting: $ ./radeon_dump Unknown card radeon_dump: ATI (null) BIOS Image start: ------------------- Segmentation fault (core dumped) I'm still looking for a native Win32 Radeon register dumper though I've not yet had any luck in that regard. Steve ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com |
From: Aapo T. <ae...@ra...> - 2005-08-08 10:39:58
Attachments:
regdump.tar.bz2
|
On Sun, 7 Aug 2005 19:30:48 +0100 (BST) Steven Newbury <s_j...@ya...> wrote: > I've managed to get my Radeon 8500 to work with YPbPr output under Windows. I > did have a bit of trouble finding how to do it again, eventually found this > thread on avsforum: > http://www.avsforum.com/avs-vb/showthread.php?t=212199&page=1&pp=20 > > The picture quality is incomparable to s-video and the Windows driver only > supports US HDTV standard output modes, while my TV also supports PAL type HDTV > modes ie. 576p; hopefully this limitation will be gone if I can get this > working with Xorg. > > It's worth noting that it does NOT work on all Radeon cards, specifically my > 9200SE will not work in YPbPr mode. > > --- Alex Deucher <ale...@gm...> wrote: > > > On 8/6/05, Steven Newbury <s_j...@ya...> wrote: > > > --- Alex Deucher <ale...@gm...> wrote: > > > > > > > Not really. Ati hasn't released any information about setting up the > > > > chip for component output. Perhaps you can dump the radeon registers > > > > in windows and compare how that driver sets things up, or perhaps the > > > > fglrx driver supports component out too and you could use the register > > > > dump tools from the r300 project. > > > > > > > Hi again! I'm going to have a go at getting Windows working with component > > out > > > and get a register dump from it. Do you know where I could find a register > > > dumper for Windows? > > > > I don't know off hand. > > > > >Or should I try compiling > > > http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/hy0/radeon_dump.tgz > > under > > > Cygwin? Would that work? > > > > I've never tried. You can give it a shot and see what happens. > I've got it to compile, however to to open /dev/mem I had to change it to open > it RDONLY, I don't why that would be, this is a default install of WinXP so my > user account is running as "Administrator". I've now come to another problem, > cygwin/nt5.1 doesn't have a /proc/bus/pci so radeon_dump is segfaulting: > $ ./radeon_dump > Unknown card > radeon_dump: ATI (null) > BIOS Image start: ------------------- > Segmentation fault (core dumped) > > I'm still looking for a native Win32 Radeon register dumper though I've not yet > had any luck in that regard. Only device drivers can access hardware under windows. Fortunately at least one _working_ HW-library still exists - http://zealsoftstudio.com/memaccess/ . -- Aapo Tahkola |
From: Philip A. <phi...@ka...> - 2005-08-08 12:35:38
|
On Sun, Aug 07, 2005 at 07:30:48PM +0100, Steven Newbury wrote: > The picture quality is incomparable to s-video and the Windows > driver only supports US HDTV standard output modes, while my TV also > supports PAL type HDTV modes ie. 576p; hopefully this limitation > will be gone if I can get this working with Xorg. Would that be 'incomparable' as in 'better' or 'worse'? :) Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt |
From: Philip A. <ph...@ka...> - 2005-08-08 08:52:10
|
On Sun, Aug 07, 2005 at 07:30:48PM +0100, Steven Newbury wrote: > The picture quality is incomparable to s-video and the Windows > driver only supports US HDTV standard output modes, while my TV also > supports PAL type HDTV modes ie. 576p; hopefully this limitation > will be gone if I can get this working with Xorg. Would that be 'incomparable' as in 'better' or 'worse'? :) Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt |