From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Microcai <microcai@fedoraproject.org>,
Vojtech Pavlik <vojtech@suse.cz>,
linuxconsole@vger.kernel.org,
linuxconsole-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Kernel fbcon UNICODE font support
Date: Thu, 2 Dec 2010 14:59:23 +0100 [thread overview]
Message-ID: <20101202135923.GA11944@const.bordeaux.inria.fr> (raw)
In-Reply-To: <alpine.LFD.2.00.1012020137320.28091@casper.infradead.org>
James Simmons, le Thu 02 Dec 2010 13:50:28 +0000, a écrit :
> This is nice and neat for vgacon but it doesn't flow so nicely with
> graphical consoles or text LCDs. What I like to see is the attribute
> buffer be split from the vc_screenbuf. The bonus is in embbeded systems we
> could arrange the code so we could have a light weight printk VT without
> the extra junk of the VC. Do we really need a attribute buffer for printk?
> I believe that would be the first step in the right direction.
That's exactly what I suggested privately to Microcai. Increasing the
number of supported glyphs should then becomes way simpler, and
double-width not so far.
Samuel
next prev parent reply other threads:[~2010-12-02 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 5:53 Microcai
2010-11-27 12:57 ` Samuel Thibault
2010-11-27 16:18 ` microcai
2010-11-27 16:39 ` Samuel Thibault
2010-11-28 6:50 ` microcai
2010-11-28 8:15 ` Vojtech Pavlik
2010-11-28 8:29 ` Microcai
2010-12-02 13:50 ` James Simmons
2010-12-02 13:59 ` Samuel Thibault [this message]
2010-12-02 18:25 ` James Simmons
2010-11-28 8:47 ` Samuel Thibault
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=20101202135923.GA11944@const.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=linuxconsole@vger.kernel.org \
--cc=microcai@fedoraproject.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®