linux-kernel - Re: My new fancy font for framebuffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Mar 2009 15:43:50 +0900
From:	Baybal Ni <nikulinpi@...il.com>
To:	Ken Moffat <zarniwhoop@...world.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: My new fancy font for framebuffer

On Mon, Mar 23, 2009 at 08:35, Ken Moffat <zarniwhoop@...world.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/