From: "mirabilos" <eccesys@topmail.de>
To: "James Simmons" <jsimmons@linux-fbdev.org>,
"Scott Prader" <gnea@rochester.rr.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: [RFC and 1/2 OT] Re: ANNOUNCE New Open Source X server
Date: Fri, 20 Apr 2001 10:16:35 -0000 [thread overview]
Message-ID: <00ca01c0c982$fbcb25a0$de00a8c0@homeip.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10104191007240.23576-100000@www.transvirtual.com>
----- Original Message -----
From: "James Simmons" <jsimmons@linux-fbdev.org>
To: "Scott Prader" <gnea@rochester.rr.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Thursday, April 19, 2001 5:16 PM
Subject: Re: ANNOUNCE New Open Source X server
>
> Thank you. It is true all I want to do is help the community. I feel
as
> alot of people do XFree86 can not meet the needs of the community. It
is
> very sad that people feel that no amount of people in the open source
> community can make code of the same or better quality as XFree86 in a
> shorter period of time. I don't feel this way. Now I'm off to work on
code
> and documentation for the project. Thank you.
My idea were: why not integrate kind of Nano-X (yes I know what that is)
into the kernel, just the X server, configured by make menuconfig (or
which you like more), and just use XF86 or something different (or even
X clients running under a different machine on the net) on it.
It should then implement enough of, if not the full, X11R6 API, and have
either direct access to the gfx board or at least to the fb (might this
be speeded up?).
It doesn't need to be fullstly (?) integrated to the kernel, it may also
be a "server" (as in microkernel systems), loaded as module but on CPL3.
So a crash doesn't hang the full system: if it crashes, we have a SysRq
which kicks out the module and does either a videomode-switch to a sane
80x25 (BIOS 03), VGA (BIOS 12) or - if framebuffer-based - nothing
because
the X server and the fb are separated.
We might as well support EGA, HGC or CGA(??) cards for it; switching to
a sane mode isn't that difficult (as discussed earlier, and for HGC I
have some NASM sources), and IIRC there is a HGC framebuffer somewhere.
-mirabilos
--
))) LICENSE FOR ABOVE MESSAGE BODY: (((
YOU _MUST NOT_ READ ABOVE MESSAGE BODY IF YOU DO NOT AGREE TO THESE
TERMS. BY READING ABOVE MESSAGE BODY YOU _AUTOMATICALLY_ _DO AGREE_
TO THE FOLLOWING TERMS:
This mail/work is protected by copyright law. It _MUST NOT_ be used
otherwise than specified by the terms and conditions at:
http://members.tripod.de/mirabilos/license.mip
The mail is, if not _explicitly_ specified differently, ONLY licensed
by these terms. THIS _CANNOT_ BE OVERRIDDEN BY ANY "TERMS OF SERVICE"
OF ANY S.PROVIDER THE MAIL GOES THROUGH, EVEN _NOT_ IF I SIGNED THEM!
--
(Sorry for the bandwidth, but some ToS force me to.)
EA F0 FF 00 F0 #$@%CARRIER LOST
prev parent reply other threads:[~2001-04-20 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 17:16 ANNOUNCE New Open Source X server James Simmons
2001-04-20 10:16 ` mirabilos [this message]
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='00ca01c0c982$fbcb25a0$de00a8c0@homeip.net' \
--to=eccesys@topmail.de \
--cc=gnea@rochester.rr.com \
--cc=jsimmons@linux-fbdev.org \
--cc=linux-kernel@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox