From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Nathan Williams" <ngwilliams@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: MODULE_LICENSE usage
Date: Mon, 06 Aug 2007 14:25:37 +0200 [thread overview]
Message-ID: <m3bqdkx326.fsf@maximus.localdomain> (raw)
In-Reply-To: <b4e196fa0708060053x65f0b1d3m50c62206cb65e016@mail.gmail.com> (Nathan Williams's message of "Mon, 6 Aug 2007 17:53:44 +1000")
Hi,
"Nathan Williams" <ngwilliams@gmail.com> writes:
> I'm working on a driver for an ADSL modem which requires the use of a
> binary library from the chipset manufacturer.
Legal things aside, the practical solutions are:
a) if the binary "library" is just firmware running on modem's CPU
(outside the host CPU and address space), then you should just
make it a file and use firmware_loader to load it to ADSL.
Having "open" firmware is nice but not a hard requirement.
b) if the binary blob is really a library to be run in kernel (host)
space then there is no point in writing such driver - there are
completely open-source drivers for ADSL devices and most (if not
all) people will prefer them over any binary library.
Perhaps you can convince the chipset manufacturer to open the source
or publish the complete docs, but I wouldn't count on it.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-08-06 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:53 MODULE_LICENSE usage Nathan Williams
2007-08-06 8:21 ` Jan Engelhardt
2007-08-06 8:24 ` Alan Cox
2007-08-06 10:41 ` Remy Bohmer
2007-08-06 12:25 ` Krzysztof Halasa [this message]
2007-08-06 15:22 ` David Schwartz
2007-08-07 3:29 ` Nathan Williams
2007-08-07 7:17 ` Arnd Bergmann
2007-08-07 15:17 ` Alan Cox
2007-08-07 18:22 ` David Schwartz
2007-08-07 18:22 ` David Schwartz
2007-08-07 19:20 ` Krzysztof Halasa
2007-08-07 20:02 ` Alan Cox
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=m3bqdkx326.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ngwilliams@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox