In this function there is a section in an if (IS_R300_VARIANT) which returns,
and later in the function there is another section setting display
priorities for IS_R300_VARIANT
something is wrong there...
Dave.
---
SF.Net email is Sponsored
On Sun, 7 Aug 2005, Dave Airlie wrote:
In this function there is a section in an if (IS_R300_VARIANT) which returns,
and later in the function there is another section setting display
priorities for IS_R300_VARIANT
something is wrong there...
You are quite right, we should get rid of the
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and red/blue are missing gray scale is set.
Are there chips that can scanout
On Fri, 5 Aug 2005, Jon Smirl wrote:
I've included the scanout types for the R200, what other ones are
supported by the various chips? For example I think the R300 can
scanout in floating point.
1 bpp monochrome (black = 0 and white = 1 or vice versa)
1 bpp indexed
2 bpp indexed
3 bpp indexed
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=212199page=1pp=20
The picture quality is incomparable to s-video and the
On Sun, 7 Aug 2005, Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and red/blue are missing gray scale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sergio wrote:
Compiling my r200 of a recent checkout, i get still all objects but also
following errors at r200_vtxtmp_x86.o :
# make
rm -f r200_vtxtmp_x86.i
/usr/ccs/lib/cpp -Dsun -Di386 -DSVR4 -D__EXTENSIONS__ -D__i386
-D_LARGEFILE_SOURCE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and
Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and red/blue are missing gray scale is set.
No, if
On Sun, 7 Aug 2005, Vladimir Dergachev wrote:
On Sun, 7 Aug 2005, Dave Airlie wrote:
In this function there is a section in an if (IS_R300_VARIANT) which
returns,
and later in the function there is another section setting display
priorities for IS_R300_VARIANT
something is wrong
Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Smirl wrote:
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So something
like:
A:2/0/R:10/2/G:10/12/B:10/22//I
This is getting more cryptic by the minute.
Can't we have a simple field: value lines ? Something like:
Ian Romanick a écrit :
The x86 assembly sources pretty much require GNU AS.
OK : thank you very very much for you answer !
About this, two questions :
1) I am compiling the whole project with Sun compiler and linker,
because its better and most sure on Solaris, e.g. GNU ld can fail in
Vladimir Dergachev wrote:
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So
something like:
A:2/0/R:10/2/G:10/12/B:10/22//I
This is getting more cryptic by the minute.
Can't we have a simple field:
On Mon, 8 Aug 2005, Antonino A. Daplas wrote:
Vladimir Dergachev wrote:
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So
something like:
A:2/0/R:10/2/G:10/12/B:10/22//I
This is getting more cryptic
On 8/7/05, Antonino A. Daplas [EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
I agree that something like the above is acceptable, exept that we need
an extra field for offset and another if indexed color or not. So
something like:
A:2/0/R:10/2/G:10/12/B:10/22//I
The offsets are not
16 matches
Mail list logo
