From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: Hello
Date: Thu, 7 Jun 2012 22:49:54 -0700 [thread overview]
Message-ID: <20120607224954.0e4649ed@newbook> (raw)
In-Reply-To: <20120608033141.GH163@brightrain.aerifal.cx>
On Thu, 7 Jun 2012 23:31:41 -0400
Rich Felker <dalias@aerifal.cx> 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@aerifal.cx> wrote:
> > 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.
Works/usable on a 2000 Dell Dimension/PIII@800MHz/128 to 256 MB RAM/i810
graphics running NetBSD 5.1.
(with an i810, there are no usable drivers at present...though kdrive
i810 might work if I can dig it up...)
However, I can't compile vesa drivers with musl.
(vesa needs sys/vm86.h to use the BIOS drivers, and sys/io.h for
hardware)
Also, uvesafb (the universal framebuffer driver) may not work with
musl: it relies on a userspace daemon, which uses vm86 or libx86 (which
in turn wants vm86, though it can emulate it...)
Isaac Dunham
next prev parent reply other threads:[~2012-06-08 5:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 12:01 Hello orc
2012-06-07 13:13 ` Hello John Spencer
2012-06-07 15:18 ` Hello orc
2012-06-07 16:29 ` Hello John Spencer
2012-06-07 16:19 ` Hello Rich Felker
2012-06-07 17:15 ` Hello orc
2012-06-08 3:31 ` Hello Rich Felker
2012-06-08 5:49 ` Isaac Dunham [this message]
2012-06-08 12:28 ` Hello aep
2012-06-08 14:14 ` Hello Rich Felker
2012-06-08 16:17 ` Hello aep
2012-06-08 16:11 ` Hello Rich Felker
2012-06-09 2:05 ` Hello Isaac Dunham
2012-07-05 17:24 ` Hello orc
2012-07-05 23:34 ` Hello Rich Felker
2012-07-06 6:06 ` Hello orc
2012-07-06 6:26 ` Hello Rich Felker
2012-07-06 8:22 ` Hello orc
2012-07-06 23:14 ` Hello idunham
2012-07-07 0:57 ` Hello Rich Felker
2012-07-07 8:07 ` Hello orc
2012-07-07 15:54 ` Hello idunham
2012-07-08 9:09 ` Hello orc
2012-06-07 17:45 ` Hello Christian Neukirchen
2012-06-07 18:03 ` Hello Jens Staal
2012-06-07 19:10 ` Hello John Spencer
2012-06-07 17:33 ` Hello Jens Staal
2012-06-07 17:59 ` Hello orc
2012-06-20 7:29 ` Hello orc
2012-06-23 1:43 ` Hello idunham
2012-06-23 1:51 ` Hello Rich Felker
2012-06-25 12:09 ` Hello orc
2012-06-25 11:59 ` Hello orc
2012-06-25 13:53 ` Hello idunham
2012-07-22 23:09 Hello idunham
2012-07-23 2:01 ` Hello Rich Felker
2012-07-23 3:49 ` Hello idunham
2012-07-23 21:01 ` Hello Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120607224954.0e4649ed@newbook \
--to=idunham@lavabit.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).