From: Gary Thomas <gary@mlbassoc.com>
To: Jack Sun <pjsun55@gmail.com>
Cc: eCos development <ecos-devel@ecos.sourceware.org>
Subject: Re: Porting linux driver to ecos
Date: Thu, 21 Apr 2005 12:16:00 -0000 [thread overview]
Message-ID: <1114085751.1030.233.camel@hermes> (raw)
In-Reply-To: <e94897a305042105106854171d@mail.gmail.com>
On Thu, 2005-04-21 at 20:10 +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?
Note: this should really be asked on ecos-devel@ecos.sourceware.org
You'd be much better off starting with drivers that have been ported
to FreeBSD since our network stack is derived from that.
As for Linux drivers, *CAUTION* since they will [mostly] be pure
GPL code which is not license compatible with the rest of Linux.
In general, you can use it for ideas, but you can't copy (cut & paste).
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
parent reply other threads:[~2005-04-21 12:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e94897a305042105106854171d@mail.gmail.com>]
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=1114085751.1030.233.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=pjsun55@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).