[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 08 Jun 2012 14:28:29 +0200
From: aep <aep@...s.org>
To: <musl@...ts.openwall.com>
Subject: Re: Hello
> Unless reading video memory has gotten substantially faster
Not in hardware, but the new DRI interface in the kernel made graphics
in linux much much less shitty.
> The way the X server is written, almost all common operations require
> reading back from video memory if implemented in software
This is because X is a network protocol, not a graphics stack.
The fix is to emulate X11 on top of a real graphics architecture,
namely DRI.
The only implementation i know is wayland.
Either way, the 1960 way of accessing GPU commandbuffers in userspace
is a dead end.
> By changing the implementation to do everything on a
> mirrored buffer in main memory
Correct. Afaik this is what XComposite in vesa already does, and
llvmpipe can operate very effiently on DRM shares in main memory.
You can even play quake3 on an arm cortex A9 with llvmpipe, it's right
on my desk.
But those things are 2012 technology, and they come at a price of a
pile of dirt below them, with horribly broken build systems and
misinterpreted "portability" issues.
Getting a real GFX stack on top of any musl-only distro is going to be
a long walk.
On Thu, 7 Jun 2012 23:31:41 -0400, Rich Felker wrote:
> On Fri, Jun 08, 2012 at 01:15:16AM +0800, orc wrote:
>> On Thu, 7 Jun 2012 12:19:28 -0400
>> Rich Felker <dalias@...ifal.cx> wrote:
>>
>> > As far as the server goes, even the oldest X server versions
>> should
>> > work fine with modern software (aside from possibly being really
>> slow
>> > when the software wants to do 3D, etc.). That's how X was
>> designed.
>> >
>> Of course we need modern X11libs for that. But yes, server expects
>> only
>> Xau, Xdmcp, crypto for ssl (modern X links to stuff like udev,
>> pixman
>> and others, but this can be avoided).
>> When building and running X I got only one thing: for 3D, games and
>> so
>> on I need a dedicated machine with videoboard vendor's drivers (no
>> matter opensource it or proprietary). For anything else, I would use
>> vesa.
> Unless reading video memory has gotten substantially faster (i.e. the
> same speed as main memory) I don't think vesa suffices for ANY use.
> The way the X server is written, almost all common operations require
> reading back from video memory if implemented in software. This could
> be avoided by changing the implementation to do everything on a
> mirrored buffer in main memory and only copy the final version to
> video memory, but as far as I know that was never done.
>
> If I'm wrong and video memory access issues have changed all this
> much
> in the past 4 or 5 years, please ignore this message...
>
>> So there is a question: will musl support this configs? Or I will
>> need patchelf and 'libc6-legacy' for them?
>
> It's intended to work, but I don't know whether it does yet.
>
> Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
