all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@alaskasi.com>
To: "Workgroup for fully free GNU/Linux distributions"
	<gnu-linux-libre@nongnu.org>,
	"Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Free firmware - A redefinition of the term and a new metric for it's measurement.
Date: Fri, 3 Feb 2017 09:44:16 -0900	[thread overview]
Message-ID: <2c7ae911-863f-4831-f024-060e5f899d3a@alaskasi.com> (raw)
In-Reply-To: <CAL1_imnr2tk9rNK2NyTX4sn8P07cR8x2Ge84M4c=hLYV4Bmy2Q@mail.gmail.com>

Hi David, I don't agree that just being given a redistributable blob is
any wonderful thing. What you end up with down the road (and this is
where we are now) is systems that need several (or many) blobs that only
the providing company understands and controls. Usually these blobs are
in control of critical or highly desirable functionality. You don't know
for sure what the blobs do or whether or not they have security
vulnerabilities. And sometimes the blobs come with restrict licensing
allowing distribution but not allowing you to reverse engineer.

For firmware development to be practical, you want more than
documentation. You want source code. Also (for embedded development) you
want a tool chain. You might have the source code but find it near
impossible to build because you don't have a good tool chain.

Yeah, with documentation, you might be able to engineer the source code
and tool chain... but it might take you 3+ years, and then only if
enough people are interested. And by that time no one will want the
hardware anymore. This isn't a moderately annoying problem for x86, but
it is a major problem for tablets, cell phones, and other embedded
development.

The companies that should be the rewarded are the ones that release
firmware, source code, and tool chain. E.g., Thinkpenguin and the TPE-R1100.

On 02/03/2017 09:18 AM, David Craven wrote:
> Hi Taylan,
> 
>> Being freely redistributeable doesn't make a blob free software
>> obviously, so endorsing such blobs would be out of the question as per
>> the core principles of the FSF.  Correct me if I misunderstand.
> 
> The requirements I proposed for the definition of free firmware is
> already more than most companies are willing to do. Any company
> willing to do these things should IMO get a medal pinned on their
> chest and not be disadvantaged.
> 

-- 
Christopher Howard, Computer Assistant
Alaska Satellite Internet
3239 La Ree Way, Fairbanks, AK 99709
907-451-0088 or 888-396-5623 (toll free)
fax: 888-260-3584
mailto:christopher@alaskasi.com
http://www.alaskasatelliteinternet.com

  reply	other threads:[~2017-02-03 18:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 14:37 Free firmware - A redefinition of the term and a new metric for it's measurement David Craven
2017-02-03 17:40 ` Taylan Ulrich Bayırlı/Kammer
2017-02-03 18:18   ` David Craven
2017-02-03 18:44     ` Christopher Howard [this message]
2017-02-03 20:12       ` David Craven
2017-02-05 22:53       ` [GNU-linux-libre] " Maxim Cournoyer
2017-02-10 17:31         ` David Craven
2017-02-10 18:21           ` Christopher Howard
2017-02-13  7:02             ` Maxim Cournoyer
2017-02-13  8:42               ` [GNU-linux-libre] " John Darrington
2017-02-13 19:24                 ` David Craven
2017-02-13 21:21                   ` [GNU-linux-libre] " Hartmut Goebel
2017-02-13 22:48                     ` David Craven
2017-02-14  6:55                   ` Maxim Cournoyer
2017-02-14 10:41                     ` [GNU-linux-libre] " David Craven
2017-02-14 17:47                       ` Maxim Cournoyer
2017-02-14 12:15 ` Denis 'GNUtoo' Carikli
2017-02-14 18:43   ` [GNU-linux-libre] " David Craven
2017-02-14 20:11     ` Adonay Felipe Nogueira
2017-02-14 20:47       ` David Craven
2017-02-14 20:57         ` Christopher Howard
2017-02-14 21:01           ` David Craven
2017-02-14 21:13             ` [GNU-linux-libre] " David Craven
2017-02-20  7:50     ` Denis 'GNUtoo' Carikli
2017-02-21 12:15       ` David Craven

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=2c7ae911-863f-4831-f024-060e5f899d3a@alaskasi.com \
    --to=christopher@alaskasi.com \
    --cc=gnu-linux-libre@nongnu.org \
    --cc=guix-devel@gnu.org \
    --cc=taylanbayirli@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.