linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose@wanadoo.es>
To: gpc01532@hotmail.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re:How to Avoid GPL Issue
Date: Sat, 28 Jun 2003 02:55:17 +0200	[thread overview]
Message-ID: <3EFCE775.7060004@wanadoo.es> (raw)

Dear Sir or Madam,

>We are trying to port a third party hardware driver into Linux kernel and
>this third party vendor does not allow us to publish the source code. Is
>there any approach that we can avoid publicizing the third party code while
>porting to Linux? Do we need to write some shim layer code in Linux kernel
>to interface the third party code? How can we do that? Is there any document
>or samples?

You should begin reading 'Proprietary kernel modules' at
http://people.redhat.com/rkeech/pkm.html

regards,
--
I don't even see the code. All I see is blonde, brunette, redhead.


                 reply	other threads:[~2003-06-28  0:41 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=3EFCE775.7060004@wanadoo.es \
    --to=xose@wanadoo.es \
    --cc=gpc01532@hotmail.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;
as well as URLs for NNTP newsgroup(s).