On 2019-02-13 03:36 PM, Kevin Brace wrote:
>> Date: Wed, 13 Feb 2019 14:03:02 -0500
>> From: Connor Behan
>> To: xorg-devel@lists.x.org
>> Subject: Re: [PATCH xf86-video-savage] Disable EXA acceleration for
>> now
>> Message-ID:
>> Content-Type: te
lback or ddx-specific
initialization called from inputthread, that happens to be an empty stub
everywhere but the xf86 ddx for Solaris.
Thoughts on that?
Thanks,
-alan-
___
xorg-devel@lists.x.org: X.Org development
Archives: http://
1). Closing log file.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
uch of a burden? If you're registering
a provider other than Xorg's you're already doing it from the DDX
driver
-Kyle
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
far, libGLX_mesa.so is the only
glvnd client-side GLX implementation that will be loaded for use with
Xorg's GLX. Thus, it doesn't seem to refute ajax's comment from earlier
in the thread:
>>> At the other extreme, the server could do nearly all the work of
>>> generating the possible __GLX_VENDOR_LIBRARY_NAME strings (with the
>>> practical downside of each server-side GLX vendor needing to enumerate
>>> the GPUs it can drive, in order to generate the hardware-specific
>>> identifiers).
>> I don't think this downside is much of a burden? If you're registering
>> a provider other than Xorg's you're already doing it from the DDX
>> driver
> -Kyle
>
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
+extern _X_EXPORT void
+xf86AssignNoOutputInitialSize(ScrnInfoPtr scrn, const OptionInfoRec *options,
+ int *no_output_width, int *no_output_height);
+
extern _X_EXPORT Bool
xf86InitialConfiguration(ScrnInfoPtr pScrn, Bool canGrow);
--
2.19.1
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
to the libglvnd's normal
vendor selection, I'd say it's orthogonal to GPU offloading. Off the top
of my head, the "GlxVendorLibrary" option ought to work regardless of
which __GLXprovider it finds. I think it would be possible to add a
function to let a driver override the GLX_VENDOR_NAMES_EXT string
,
> + "Using %s acceleration architecture\n",
> + psav->useEXA ? "EXA" : "XAA");
> + } else {
> + xf86DrvMsg(pScrn->scrnIndex, X_INFO,
> + "Hardware acceleration is disabled.\
__
mesa-dev mailing list
mesa-...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
any point in this process, and even this
part is optional and should be a pretty trivial extension to the GLXVND
interface in the server.
-Kyle
_______
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
rom the selected ':'?
> >
> > (2) Who should decide which vendor/gpu gets the semantic name
> > "performance" or "battery"? They are relative, so I don't know that
> > vendors can decide for themselves in isolation. It kind of feels
> &
Consider updating or deleting it:
http://www.freedesktop.org/wiki/Software/Glamor/
Thanks.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
Mailing list subscription confirmation notice for mailing list
xorg-devel
We have received a request from archive@mail-archive.com for
subscription of your email address, archive@mail-archive.com, to the
xorg-de...@lists.x.org mailing list. To confirm that you want to be
added to this mailing
Mailing list subscription confirmation notice for mailing list
xorg-devel
We have received a request from archive@mail-archive.com for
subscription of your email address, archive@mail-archive.com, to the
xorg-de...@lists.x.org mailing list. To confirm that you want to be
added to this mailing
14 matches
Mail list logo
