mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baybal Ni <nikulinpi@gmail.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: My new fancy font for framebuffer
Date: Tue, 24 Mar 2009 15:43:50 +0900	[thread overview]
Message-ID: <ff479ab60903232343k2448a11dtebe21df6acb24a5f@mail.gmail.com> (raw)
In-Reply-To: <20090322233502.GC1114@deepthought>

On Mon, Mar 23, 2009 at 08:35, Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> On Sun, Mar 22, 2009 at 06:22:11PM +0900, Baybal Ni wrote:
>>
>> Yes, but we want it to be bundled in kernel, for me it is the only
>> option for systems with qvga screens or so on. Old fonts were nice
>> only on CRT displays, but on TFTs they are giving too much load on
>> eyes and brain. More clean contoured fonts are effectively cutting it.
>
>  Who are the "we" who want it to be in the kernel ?
>
>  There are _many_ available screen fonts, and I can understand
> people being unhappy with the common existing fonts, particularly
> once messages move beyond English into whatever locale you are using
> (I use my own variant console font [1] to cover most European
> languages with letter forms that I find easy to read), but what
> specific problem does putting terminus in the kernel solve ?
>
>  e.g. are the kernel's boot messages *before* you run 'setfont'
> illegible ?  If so, what is your specific hardware ?
>
>  I've been using only TFTs for a few years, and I don't see any
> significant problems, only questions of preferred letter shapes and
> glyph coverage.  But then, I'm a native English speaker, so I have
> to be willing to accept that a font I find easy to read might not be
> easy for people who do not normally use a latin alphabet.  If that
> applies to you, you need to provide reasons why this belongs in the
> kernel instead of userspace.
>
> ken
>
> [1] sigma-consolefonts - you probably won't like it ;-)
> --
> das eine Mal als Tragödie, das andere Mal als Farce
>

Yes, I don't have a capability to have kbd in my devices, as every bit
is counted on devices with less than 4mb of flash.
My devices are various daps and dffs alike with =< 480x320 screens,
some of them are mochrome. All of them uses linux native fb console.
Thought, it is not a maintream, but still, linux is the only already
solution for things like that.

>That being said, there is no fundamental reason why the BDF and the
>resulting processing can't be included in the kernel.

So, why not just to squeeze the whole kbd into the kernel? =D, or you
want the way how to inject bdf blob compiletime? These way it would
violate the GPL almost the same way as you have already said.

Why you are so unhappy about GPL in GPL? I Think that it is perfectly
ok as long as it goes along with 4 basics of GPL. And it does along
with it.

As I see, current bundled fonts could be already copyright ridden these way.

  reply	other threads:[~2009-03-24  6:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21 16:45 Baybal Ni
2009-03-21 18:15 ` Arjan van de Ven
2009-03-22  4:12   ` H. Peter Anvin
2009-03-22  4:17   ` H. Peter Anvin
2009-03-22  9:22     ` Baybal Ni
2009-03-22 19:01       ` H. Peter Anvin
2009-03-22 23:35       ` Ken Moffat
2009-03-24  6:43         ` Baybal Ni [this message]
2009-03-24 23:15           ` H. Peter Anvin
2009-03-24 23:39             ` Felipe Contreras
2009-03-24 23:43               ` H. Peter Anvin
     [not found] <cicyE-3qo-15@gated-at.bofh.it>
     [not found] ` <cidXL-5OQ-35@gated-at.bofh.it>
     [not found]   ` <cinu8-41e-3@gated-at.bofh.it>
     [not found]     ` <cisas-37w-5@gated-at.bofh.it>
     [not found]       ` <ciFKp-7QW-17@gated-at.bofh.it>
     [not found]         ` <cj8CE-3uO-11@gated-at.bofh.it>
     [not found]           ` <cjo4C-3hh-13@gated-at.bofh.it>
     [not found]             ` <cjoo1-3FO-13@gated-at.bofh.it>
     [not found]               ` <cjoxL-3SW-35@gated-at.bofh.it>
2009-03-26 13:55                 ` Bodo Eggert
2009-03-30  7:51                   ` Baybal Ni

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=ff479ab60903232343k2448a11dtebe21df6acb24a5f@mail.gmail.com \
    --to=nikulinpi@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zarniwhoop@ntlworld.com \
    /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®