From: Antoine Martin <antoine@nagafix.co.uk>
To: User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Cc: Gerd Knorr <kraxel@bytesex.org>
Subject: [uml-devel] uml FB
Date: Sun, 02 Dec 2007 14:50:14 +0000 [thread overview]
Message-ID: <4752C626.4050000@nagafix.co.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Been looking at the uml-x11-fb patch again.
It still does apply more or less cleanly, but won't build (can't get
Kbuild to play nice) and I was thinking: wouldn't it be easier to just
drop all the X11 stuff and have just a plain in-memory VESA type of
framebuffer in the guest (straightforward contiguous memory region).
This would allow the guest to have a framebuffer and if we need to
actually see its contents, it could easily be exposed using shared
memory. This would completely de-couple the framebuffer from the host,
allowing us to attach/detach as needed: start session, detach, log out
of X, log in, attach to guest framebuffer (although this doesn't address
the mouse/keyboard issue).
Is this (easily) feasable at all?
Thanks
Antoine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHUsYmGK2zHPGK1rsRCpt9AJ40otwE6ziQDIpR6u0/ImQYFsFcegCfe5Jw
Q6XhYv6RkGb11AVZ/aZBB5c=
=xdpn
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2007-12-02 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 14:50 Antoine Martin [this message]
2007-12-03 9:38 ` [uml-devel] uml FB Gerd Hoffmann
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=4752C626.4050000@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=kraxel@bytesex.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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