From: Microcai <microcai@fedoraproject.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-console@vger.kernel.org
Subject: Re: [PATCH 1/2] Kernel fbcon UNICODE font support
Date: Sat, 27 Nov 2010 16:19:43 +0800 [thread overview]
Message-ID: <1290845983.677.6.camel@cai.gentoo> (raw)
In-Reply-To: <20101126232503.30cfe78b@pyx>
在 2010-11-26五的 23:25 +0000，Alan Cox写道：
> > > Use a different virtual frame buffer, or write software to multiplex
> > > the
> > > use of it, you know like say X does...
> >
> > Well, then different virtual frame buffer will not have fbterm running ,
> > how do you see UNICODE output?
>
> It'll have video on it so you won't anyway, and if you want it windowed
> then use a windowing system or write one.
Any way, I see /*FIXME: need support more than 255 chars font*/ in
fbcon.c. So, you *plan* to support UNICODE font , then why not take it ?
If the patch is not good enough , I'm still working on it. I can adjust
and make things more perfect.
--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-11-27 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 10:02 [PATCH 1/2] Kernel fbcon UNICODE font support Microcai
2010-11-26 10:09 ` Alan Cox
2010-11-26 10:19 ` microcai
[not found] ` <1F1E2EC1077B4BA58A16D9D3B458A7FD@avitech.sk>
2010-11-26 10:32 ` microcai
2010-11-26 10:41 ` Alan Cox
[not found] ` <AANLkTi=T7pfTP0xHmGqLCSj_8vq_kRijCp5NF+VeBz_f@mail.gmail.com>
[not found] ` <20101126104818.1e8f6511@lxorguk.ukuu.org.uk>
2010-11-26 10:53 ` microcai
2010-11-26 11:03 ` microcai
2010-11-26 11:42 ` Alan Cox
2010-11-26 11:53 ` Microcai
2010-11-26 23:25 ` Alan Cox
2010-11-27 5:52 ` Microcai
2010-11-27 13:53 ` Alan Cox
2010-11-29 1:42 ` microcai
2010-11-29 8:52 ` Samuel Thibault
2010-11-27 8:19 ` Microcai [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=1290845983.677.6.camel@cai.gentoo \
--to=microcai@fedoraproject.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-console@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