On Tue, 2003-03-04 at 11:36, Michel Dänzer wrote:
I have not provided a diff because it is quite a hack and very
system
specific, at the moment. Effectively, I forced the virtual size to
be
2048x768, hacked the RADEONDoAdjustFrame() function to fix views as
I
wanted them, used the
On Wed, Mar 05, 2003 at 11:06:45AM -0500, Jonathan Thambidurai wrote:
On Tue, 2003-03-04 at 11:36, Michel Dänzer wrote:
I have not provided a diff because it is quite a hack and very
system
specific, at the moment. Effectively, I forced the virtual size to
be
2048x768, hacked the
On Die, 2003-03-04 at 01:52, Jonathan Thambidurai wrote:
I am pleased to report that thanks to the guidance Jens Owens gave in a
previous message, I have made 3D work on two heads simultaneously (IIRC,
the ATI Windows XP drivers didn't do this).
Coolness.
I have not provided a diff
Hello, ...
As you may have noticed, i have started a (sub) thread with David Dawes
on this subject on the xfree86 list.
Friendly,
Sven Luther
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
On Thu, Feb 27, 2003 at 02:14:37AM +0100, Michel Dänzer wrote:
On Mit, 2003-02-26 at 18:16, Alex Deucher wrote:
--- Sven Luther [EMAIL PROTECTED] wrote:
[ video memory management ]
How is it done right now ? Is a part of the onchip memory reserved
for framebuffer and XAA, and another
On Thu, Feb 27, 2003 at 02:12:24AM +0100, Michel Dänzer wrote:
On Mit, 2003-02-26 at 21:11, Sven Luther wrote:
[...] because the DRI is just rendering to the framebuffer, it doesn't
know if you are displaying it or not, and doesn't even care. The only
issue is with size limits of the 3D
On Don, 2003-02-27 at 09:33, Sven Luther wrote:
On Thu, Feb 27, 2003 at 02:14:37AM +0100, Michel Dänzer wrote:
On Mit, 2003-02-26 at 18:16, Alex Deucher wrote:
-- Sven Luther [EMAIL PROTECTED] wrote:
[ video memory management ]
How is it done right now ? Is a part of the onchip
On Thu, Feb 27, 2003 at 06:58:42PM +0100, Michel Dänzer wrote:
On Don, 2003-02-27 at 09:33, Sven Luther wrote:
On Thu, Feb 27, 2003 at 02:14:37AM +0100, Michel Dänzer wrote:
On Mit, 2003-02-26 at 18:16, Alex Deucher wrote:
-- Sven Luther [EMAIL PROTECTED] wrote:
[ video memory
On Mon, Feb 24, 2003 at 01:28:15PM -0800, Alex Deucher wrote:
right now for these chips you set up the entity as shareable and then
divide your framebuffer into two or more frambuffers, one for each
CRTC. Each instance of the driver then works using its framebuffer.
each head is
--- Sven Luther [EMAIL PROTECTED] wrote:
On Mon, Feb 24, 2003 at 01:28:15PM -0800, Alex Deucher wrote:
right now for these chips you set up the entity as shareable and
then
divide your framebuffer into two or more frambuffers, one for each
CRTC. Each instance of the driver then works
On Wed, 26 Feb 2003, Sven Luther wrote:
Yes, and you have to divide the fb memory in two, one for each head, or
something such, and each head will have its separate offscreen memory
manager, possibly using different screen strides.
Side note: I know that what people are mostly talking about
On Wed, Feb 26, 2003 at 09:16:53AM -0800, Alex Deucher wrote:
--- Sven Luther [EMAIL PROTECTED] wrote:
How is it done right now ? Is a part of the onchip memory reserved
for
framebuffer and XAA, and another part free for 3D use ?
Not sure. I'm not familiar with the memory manager
--- Linus Torvalds [EMAIL PROTECTED] wrote:
On Wed, 26 Feb 2003, Sven Luther wrote:
Yes, and you have to divide the fb memory in two, one for each
head, or
something such, and each head will have its separate offscreen
memory
manager, possibly using different screen strides.
Side
On Wed, Feb 26, 2003 at 09:40:18AM -0800, Linus Torvalds wrote:
On Wed, 26 Feb 2003, Sven Luther wrote:
Yes, and you have to divide the fb memory in two, one for each head, or
something such, and each head will have its separate offscreen memory
manager, possibly using different screen
On Mit, 2003-02-26 at 21:11, Sven Luther wrote:
[...] because the DRI is just rendering to the framebuffer, it doesn't
know if you are displaying it or not, and doesn't even care. The only
issue is with size limits of the 3D engine, like Michel said, with the
Radeon 3D engine being limited
On Mit, 2003-02-26 at 18:16, Alex Deucher wrote:
--- Sven Luther [EMAIL PROTECTED] wrote:
[ video memory management ]
How is it done right now ? Is a part of the onchip memory reserved
for framebuffer and XAA, and another part free for 3D use ?
Not sure. I'm not familiar with the memory
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides Xinerama
Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides Xinerama functionality without actually using the
Xinerama wrapper.
Could you please point me to the code which needs to be worked on for
the above solution so that I know where to start? Would I have to
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides Xinerama functionality without actually using the
Xinerama wrapper.
Wouldn't
On Mon, Feb 24, 2003 at 08:35:13AM -0700, Jens Owen wrote:
Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
On Mon, 2003-02-24 at 17:36, Steven Newbury wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides Xinerama
On Mon, 2003-02-24 at 16:09, Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D comes for free:
On Mon, 2003-02-24 at 16:27, Jonathan Thambidurai wrote:
http://www.tungstengraphics.com/dri/Simple_Xinerama_DH.txt
This solution provides Xinerama functionality without actually using the
Xinerama wrapper.
Could you please point me to the code which needs to be worked on for
the
On Mon, Feb 24, 2003 at 06:05:21PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 16:09, Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
head supported on a single X11 screen. Then 3D
On Mon, 2003-02-24 at 18:11, Sven Luther wrote:
On Mon, Feb 24, 2003 at 06:05:21PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 16:09, Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A short cut to this whole thing would be to work on getting a second
On Mon, Feb 24, 2003 at 06:35:47PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 18:11, Sven Luther wrote:
On Mon, Feb 24, 2003 at 06:05:21PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 16:09, Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A
On Mon, Feb 24, 2003 at 06:35:47PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 18:11, Sven Luther wrote:
On Mon, Feb 24, 2003 at 06:05:21PM +0100, Michel Dänzer wrote:
On Mon, 2003-02-24 at 16:09, Sven Luther wrote:
On Mon, Feb 24, 2003 at 07:58:55AM -0700, Jens Owen wrote:
A
On Mon, 2003-02-24 at 11:12, Jens Owen wrote:
I believe you can implement this at the 2D DDX driver level. Getting
the configuration file semantics worked out would probably be the first
step. Then get the driver to read those semantics and initial the
secondary display pipeline.
Have
I too am curious about that. I've been working on adding duoview
support to the s3 savage driver. I talked to Tim Roberts a while back
and I figured out the basics of how it works. I've got a semi-working
driver, but alas, I think I need some help getting the second crtc to
output to the vga
Let me begin with the following: I downloaded the texmem branch from
DRI CVS. It fails to compile, giving the error
./config/imake/imake -I./config/cf -s
./config/makedepend/Makefile.proto -f ./config/makedepend/Imakefile
-DTOPDIR=../.. -DCURDIR=./config/makedepend
./config/imake/imake: No
On Die, 2003-02-25 at 01:24, Jonathan Thambidurai wrote:
I had a look at radeon_driver.c. The first thing that drew my attention
was the the conditional that was prefixed by
/* Xinerama has sync problem with DRI, disable it for now */
Does this imply that everything is set up already
I too am curious about that. I've been working on adding duoview
support to the s3 savage driver. I talked to Tim Roberts a while back
and I figured out the basics of how it works. I've got a semi-working
driver, but alas, I think I need some help getting the second crtc to
output to the vga
On Mon, 2003-02-24 at 03:16, Jonathan Thambidurai wrote:
On my Mobility Radeon 7500, I would like to have accelerated 3D working
on one screen (primary I assume) of a Xinerama dual-head setup. As it
stands, direct rendering is completely disabled upon XFree86 startup
whenever two heads are
34 matches
Mail list logo
