From: "H. Peter Anvin" <hpa@zytor.com>
To: Baybal Ni <nikulinpi@gmail.com>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>, linux-kernel@vger.kernel.org
Subject: Re: My new fancy font for framebuffer
Date: Tue, 24 Mar 2009 16:15:04 -0700 [thread overview]
Message-ID: <49C96978.6050904@zytor.com> (raw)
In-Reply-To: <ff479ab60903232343k2448a11dtebe21df6acb24a5f@mail.gmail.com>
Baybal Ni wrote:
>
> 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.
>
No, it wouldn't. The fundamental requirement of the GPL is distribution
of the preferred editable format, which in this case is the BDF (and the
unicode files.)
> 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.
It has nothing to do with "4 basics", it has to do with the literal
specification in the license. ssencessence There is nothing wrong with
incorporating code from another GPL'd project (quite on the contrary,
it's encouraged), but it has to be in source code form -- a C file which
contains a processed binary is not source.
Of course, you could contact the author and get a special exception, too
(in which case this should be declared in the file.)
-hpa
(I am not a lawyer. My understanding is that in the United States, none
of this really applies because bitmap fonts are not copyrightable.
However, my understanding is that this is not true in some other
jurisdictions, so we can't just go ahead and ignore the license.)
next prev parent reply other threads:[~2009-03-24 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 16:45 My new fancy font for framebuffer 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
2009-03-24 23:15 ` H. Peter Anvin [this message]
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=49C96978.6050904@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikulinpi@gmail.com \
--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