[Dri-devel] new 2048 limit code...
I've had several mergedfb users complain about the 2048 DRI limit
put in yesterday:
else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) {
info->directRenderingEnabled = FALSE;
xf86DrvMsg(scrnIndex, X_WARNING,
"Direct Rendering Disabled -- "
"Virtual resolution exceeds 2048 "
"(hardware limitation)\n");
}
I'm not sure what the best way around this is...
While that is the limit, you can have a desktop larger than 2048 in
either dimension and 3D will work as long as the 3D windows are within
those limits. Often times users have a desktop larger than 2048 and
then when they use 3D (game, etc. using xvidmode), they switch to a
clone mode of less then 2048 and everything works fine. people rarely
run any apps larger than 2048 (other than screen savers maybe...).
I don't really care which way we go on this issue, I'm just pointing
out that's it's there...
perhaps we can not disable the DRI if mergedfb is active and the viral
is larger than 2048?
Anyone have any thoughts?
Alex
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] new 2048 limit code...
On Fri, 2003-10-17 at 17:27, Alex Deucher wrote:
>I've had several mergedfb users complain about the 2048 DRI limit
> put in yesterday:
>
> else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) {
> info->directRenderingEnabled = FALSE;
> xf86DrvMsg(scrnIndex, X_WARNING,
> "Direct Rendering Disabled -- "
> "Virtual resolution exceeds 2048 "
> "(hardware limitation)\n");
> }
>
> I'm not sure what the best way around this is...
> While that is the limit, you can have a desktop larger than 2048 in
> either dimension and 3D will work as long as the 3D windows are within
> those limits. Often times users have a desktop larger than 2048 and
> then when they use 3D (game, etc. using xvidmode), they switch to a
> clone mode of less then 2048 and everything works fine. people rarely
> run any apps larger than 2048 (other than screen savers maybe...).
>
> I don't really care which way we go on this issue, I'm just pointing
> out that's it's there...
>
> perhaps we can not disable the DRI if mergedfb is active and the viral
> is larger than 2048?
>
> Anyone have any thoughts?
Maybe in the 3d driver you could fall back to software on grabbing the
lock if the width is too large?
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
---
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] new 2048 limit code...
On Fri, Oct 17, 2003 at 05:27:36PM -0700, Alex Deucher wrote:
>
>I've had several mergedfb users complain about the 2048 DRI limit
> put in yesterday:
>
> else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) {
> info->directRenderingEnabled = FALSE;
> xf86DrvMsg(scrnIndex, X_WARNING,
> "Direct Rendering Disabled -- "
> "Virtual resolution exceeds 2048 "
> "(hardware limitation)\n");
> }
>
> I'm not sure what the best way around this is...
> While that is the limit, you can have a desktop larger than 2048 in
> either dimension and 3D will work as long as the 3D windows are within
> those limits. Often times users have a desktop larger than 2048 and
> then when they use 3D (game, etc. using xvidmode), they switch to a
> clone mode of less then 2048 and everything works fine. people rarely
> run any apps larger than 2048 (other than screen savers maybe...).
>
> I don't really care which way we go on this issue, I'm just pointing
> out that's it's there...
>
> perhaps we can not disable the DRI if mergedfb is active and the viral
> is larger than 2048?
>
> Anyone have any thoughts?
How does this work on Windows ?
Alan.
---
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] new 2048 limit code...
On Sat, 2003-10-18 at 12:27, Keith Whitwell wrote: > Eric Anholt wrote: > > On Fri, 2003-10-17 at 17:27, Alex Deucher wrote: > > > >>perhaps we can not disable the DRI if mergedfb is active and the viral > >>is larger than 2048? It was only MergedFB which made this necessary... > > Maybe in the 3d driver you could fall back to software on grabbing the > > lock if the width is too large? > > Better still would be to have the 3d driver subdivide cliprects larger than > width 2048, and adjust the origin cooridnates to make it work. Interesting idea. I think we should keep the status quo until the 3D drivers can deal with this though, to avoid confusion with users who don't know the details. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] new 2048 limit code...
Unless anyone says otherwise, I'm going to remove this code. All it has done is generate complaints from MergedFB users. Apparently it doesn't hurt anything (ie. cause a crash) to leave direct rendering enabled if the virtual desktop is larger than 2048. Since MergedFB users seem to be the only ones running into it, I don't see this affecting regular DRI users. I will put a warning in the code if the virtual res is larger than 2048 to let them know that they may run into issues. Alex --- Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Sat, 2003-10-18 at 12:27, Keith Whitwell wrote: > > Eric Anholt wrote: > > > On Fri, 2003-10-17 at 17:27, Alex Deucher wrote: > > > > > >>perhaps we can not disable the DRI if mergedfb is active and the > viral > > >>is larger than 2048? > > It was only MergedFB which made this necessary... > > > > Maybe in the 3d driver you could fall back to software on > grabbing the > > > lock if the width is too large? > > > > Better still would be to have the 3d driver subdivide cliprects > larger than > > width 2048, and adjust the origin cooridnates to make it work. > > Interesting idea. > > I think we should keep the status quo until the 3D drivers can deal > with > this though, to avoid confusion with users who don't know the > details. > > __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
