On Fri, Mar 29, 2002 at 12:39:14AM -0800, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for
Around 4 o'clock on Apr 1, Vedran Rodic wrote:
I did something similiar weeks ago and sent a diff to Marc La France. I
should have sent it to this list too :)
My patch is larger than yours, since I took more code from Gatos and added
offscreen images support.
Yes, that would be useful as
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
On Fri, 29 Mar 2002, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth
On Fri, Mar 29, 2002 at 12:39:14AM -0800, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for
On Fri, 29 Mar 2002, Kevin E Martin wrote:
Keith, I'm still working on merging in some of my Radeon changes, so I
handle checking it in. Also, I'd like to hear from others if this works
for their cards (i.e., Keith's second question above). I just saw Andrew
Aitchison's post (ATI Radeon VE
On Fri, 29 Mar 2002, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth
Around 14 o'clock on Mar 29, Vladimir Dergachev wrote:
The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
to fix.
Keith, could you tell me what was broken in GATOS code ?
RADEONSetColorKey needs to convert a pixel value
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 14 o'clock on Mar 29, Vladimir Dergachev wrote:
The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
to fix.
Keith, could you tell me what was broken in GATOS code ?
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with 8bpp
modes so I thought the code to be correct.
Around 10 o'clock on Mar 29, Kevin E Martin wrote:
Keith, I'm still working on merging in some of my Radeon changes, so I
handle checking it in.
Ok. I've also added code to set the default color key value and I need to
fix how it computes color key values so that non-TrueColor visuals work
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with 8bpp
modes so I thought the code to be correct.
On Fri, 29 Mar 2002, Mark Vojkovich wrote:
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with
Around 12 o'clock on Mar 29, Mark Vojkovich wrote:
The Rage 128 didn't work that way. It keyed off index values, not
the color they correspond to. If it keys off the post colormap lookup
value, this isn't very useful for video since there can be many identical
colors in the colormap
Around 12 o'clock on Mar 29, Mark Vojkovich wrote:
The Rage 128 didn't work that way. It keyed off index values, not
the color they correspond to. If it keys off the post colormap lookup
value, this isn't very useful for video since there can be many identical
colors in the colormap
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
The reason is that we use colorkeying for clipping. 8bbp display has a
very large chance that this will break down and part of video will show
thru. Additionally, 8bpp is just plain bad for color intensive apps - you
will be ok if your
Around 15 o'clock on Mar 29, Dr Andrew C Aitchison wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Dr Andrew C Aitchison wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
On Fri, 29 Mar 2002, Vladimir Dergachev wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and stuck
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
The video key is now configurable (option videokey 42) and
has a non-zero default value (30).
I just want to point out that GATOS code already supports this.
As for 8bbp - I will
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
As for Radeon colorkeying the reason we use RGB values is because Radeon
no longer supports keying on the value of graphics pixel,
Well, I just experimentally determined that (at least on my M6 LY), this
is not true. For the component
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
As for Radeon colorkeying the reason we use RGB values is because Radeon
no longer supports keying on the value of graphics pixel,
Well, I just experimentally determined that (at least on
24 matches
Mail list logo
