public inbox for
 help / color / mirror / Atom feed
From: Andrew Lunn <>
To: Jack Sun <>
Subject: Re: Porting linux driver to ecos
Date: Thu, 21 Apr 2005 12:16:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Apr 21, 2005 at 08:10:11PM +0800, Jack Sun wrote:
> Hi,
> I would like to port the wireless driver source code from linux to
> ecos on my platform.
> Is it easy to do and what I need to take care in your experience?

Before you start you need to consider the licensing issue. Linux is
GPL. eCos is modGPL. The modification means that the viral effects of
the GPL do not spread to the application code. However if you port the
GPL wireless driver into eCos, the GPL from the driver will spread
over all of eCos and to the application. ie you need to make your
application sources available. You need to decide if this is
acceptable to you. 

We won't be able to accept your code into the eCos repository
obviously because it is GPL.

Also, you might consider talking a look at the FreeBSD wlan
drivers. They will probably have both a more suitable licence and will
be easier to port since the TCP/IP stack in eCos is from FreeBSD.


  reply	other threads:[~2005-04-21 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 12:10 Jack Sun
2005-04-21 12:16 ` Andrew Lunn [this message]
2005-04-21 21:38 ` Jonathan Larmour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).