From: Dax Kelson <dax@gurulabs.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: gene.heskett@verizon.net, linux-kernel@vger.kernel.org,
Han Boetes <han@mijncomputer.nl>
Subject: Re: Intel also needs convincing on firmware licensing.
Date: Thu, 28 Oct 2004 13:00:28 -0600 [thread overview]
Message-ID: <1098990028.3856.277.camel@mentorng.gurulabs.com> (raw)
In-Reply-To: <200410280850.51033.vda@port.imtp.ilyichevsk.odessa.ua>
On Wed, 2004-10-27 at 23:50, Denis Vlasenko wrote:
> However, disassemblers do exist. Hiding secrets in binary .o
> files is silly.
Who cares what the secrets in the firmware are.
Again, it does not execute on your computer's CPU. It does not taint the
kernel. The Linux kernel driver is 100% GPLd, no binary blobs.
Nearly all the devices in your computer have firmware. Your keyboard,
your CDROM drive, your graphics card. It is hypocritical to clamor for
the source code to the IPW2100/2200/etc while not clamoring for the
source code to all the other firmwares in your computer.
It is unfortunate that the firmware isn't stored onboard the Intel card,
and instead needs to be loaded, however, this is a pretty minor
inconvenience.
The only remaining issue, if the redistribution terms of the firmware
are liberal enough so that RHEL/FC and other free minded distros can
include the files out of the box in /lib/hotplug/firmware directory.
Apparently the terms are OK with SUSE as they include the firmware in
SUSE LINUX v9.2. This isn't a huge surprise as SUSE has always been more
willing to bundle less than free works.
Dax Kelson
Guru Labs
next prev parent reply other threads:[~2004-10-28 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 2:25 Intel also needs convincing on firmware licensing Han Boetes
2004-10-28 3:28 ` Lee Revell
2004-10-28 3:46 ` Gene Heskett
2004-10-28 5:50 ` Denis Vlasenko
2004-10-28 19:00 ` Dax Kelson [this message]
2004-10-28 19:10 ` Marcel Holtmann
2004-10-28 15:41 ` Kalin KOZHUHAROV
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=1098990028.3856.277.camel@mentorng.gurulabs.com \
--to=dax@gurulabs.com \
--cc=gene.heskett@verizon.net \
--cc=han@mijncomputer.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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 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.