From: "Yann E. MORIN" <yann.morin@atosorigin.com>
To: "lkml" <linux-kernel@vger.kernel.org>
Subject: Manifesto for GPL source code
Date: Mon, 19 Nov 2001 11:59:44 +0100 [thread overview]
Message-ID: <012101c170e9$4c5b5770$8a140237@rennes.si.fr.atosorigin.com> (raw)
Hi all!
I'm in the process (well, no realy, but soon) of writing a driver
for a telephony board (manufacturer has decided not to support the
Linux plateform, sad...).
I've got the LDD2, the LKMPG, the Linux code. I know about
KernelNewbies and have spent quite a few weeks reading through LKML.
Everything is getting well in place both in my head and in my
employer's.
Anyhow, some pointers to this kind of work, to other source of
information, anything you might be worth reading/downloading/compiling
will be welcome.
But then, we'll have to 'deal' with the board manufacturer to obtain
the specifications. What we'd like to do is sign no NDA, as to provide
the community with yet another driver (I need assistance to write such
a piece of code and I feel it GOOD to release that driver _free_).
So here's the question:
Where could I find some kind of a manifesto to show the manufacturer
to have him understand the pros (and cons) of GPL Software, so they
release the HW specs.
When the manufacturer doesn't agree with GPL, what kind of NDA would
be most valuable to sign, as to provide the most possible info to
the comunity? I know some have signed NDAs and release only binaries.
Would that be a satisfactory agreement?
Thanx all!
Yann, hoppefully futur linux device driver writer! ;-)
--
.---------------------------.----------------------.------------------.
| Yann E. MORIN | Real-Time Embedded | ASCII RIBBON /"\ |
| phone (+33/0) 299 055 231 | Software Designer | CAMPAIGN \ / |
| fax (+33/0) 299 055 221 °----------------------: AGAINST X |
| yann.morin@atosorigin.com www.atosorigin.com | HTML MAIL / \ |
°--------------------------------------------------°------------------°
reply other threads:[~2001-11-19 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='012101c170e9$4c5b5770$8a140237@rennes.si.fr.atosorigin.com' \
--to=yann.morin@atosorigin.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®