From: Marcel Holtmann <marcel@holtmann.org>
To: Dax Kelson <dax@gurulabs.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
gene.heskett@verizon.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Han Boetes <han@mijncomputer.nl>
Subject: Re: Intel also needs convincing on firmware licensing.
Date: Thu, 28 Oct 2004 21:10:39 +0200 [thread overview]
Message-ID: <1098990639.6636.37.camel@pegasus> (raw)
In-Reply-To: <1098990028.3856.277.camel@mentorng.gurulabs.com>
Hi Dax,
> 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.
as a side note, the finally choosen directory is /lib/firmware/.
Regards
Marcel
next prev parent reply other threads:[~2004-10-28 19:11 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
2004-10-28 19:10 ` Marcel Holtmann [this message]
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=1098990639.6636.37.camel@pegasus \
--to=marcel@holtmann.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox