From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Corbin Simpson <mostawesomedude@gmail.com>
Cc: timofonic timofonic <timofonic@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org
Subject: Re: Future desktop on dumb frame buffers?
Date: Mon, 21 Mar 2011 19:59:05 +0000 [thread overview]
Message-ID: <20110321125905.0159a6f4@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTi=kRdC1LoHxqwKxYKZJf99vBEU=OmQoY+zS1dK-@mail.gmail.com>
On Mon, 21 Mar 2011 12:34:38 -0700
Corbin Simpson <mostawesomedude@gmail.com> wrote:
> Related: We are still missing basic userspace tools (kmsset, e.g.),
> some kind of direct KMS console (kmscon would work, if it existed),
> and an xf86-video-modesetting which compiles and works (this is
> actually possible now, with some patches that landed in 2.6.38 for
> generic KMS access.)
Yeah, we used to call that drmcon, and it's still a big open. I think
there are some projects that sit on top of fbdev and provide a good
text console with fancy character and input support, but I don't know
if any of them have been ported to KMS to handle multiple outputs or
with an aim toward integrating into a distro as a VT replacement.
kmsset or something would be pretty easy to do; the modetest program in
the drm repo would be a good starting point for that. One limitation
there is handling fbcon, which makes reallocation of the framebuffer
somewhat difficult.
IIRC plymouth or whatever Fedora is using these days uses the KMS APIs
though...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-21 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 11:20 Future desktop on dumb frame buffers? Geert Uytterhoeven
2011-03-19 15:45 ` Rob Clark
2011-03-21 18:00 ` Jesse Barnes
2011-03-21 19:19 ` timofonic timofonic
[not found] ` <AANLkTimjOs8ZuKRUt1aOizhbRw2-Ni4bTPty-dKpZ-rz-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-21 19:25 ` Jesse Barnes
2011-03-21 19:34 ` Corbin Simpson
2011-03-21 19:59 ` Jesse Barnes [this message]
2011-03-21 21:13 ` Ondrej Zary
2011-03-21 21:46 ` Alex Deucher
2011-03-21 19:50 ` Geert Uytterhoeven
2011-03-21 19:56 ` Jesse Barnes
2011-03-21 20:08 ` Alex Deucher
2011-03-23 14:09 ` Robert Fekete
2011-03-24 11:05 ` Laurent Pinchart
2011-03-21 21:20 ` Alan Cox
[not found] ` <20110321212008.384711f0-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2011-03-21 21:22 ` Jesse Barnes
2011-03-21 21:37 ` Matt Turner
2011-04-04 9:40 ` Alan Cox
2011-03-22 15:26 ` Michal Suchanek
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=20110321125905.0159a6f4@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=mostawesomedude@gmail.com \
--cc=timofonic@gmail.com \
--cc=wayland-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).