From: Jonathan Larmour <jifl@jifvik.org>
To: Jack Sun <pjsun55@gmail.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Porting linux driver to ecos
Date: Thu, 21 Apr 2005 21:38:00 -0000 [thread overview]
Message-ID: <42681D54.4020704@jifvik.org> (raw)
In-Reply-To: <e94897a305042105106854171d@mail.gmail.com>
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
Probably very difficult indeed.
> and what I need to take care in your experience?
If you were to start anywhere, I'd suggest updating the FreeBSD stack port
to the latest version, which would allow you to incorporate the FreeBSD
stack's wireless support. Unfortunately the stack update is required as (if
I recall correctly) the code is not standalone but depends on other changes
that have taken place in the network stack.
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2005-04-21 21:38 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
2005-04-21 21:38 ` Jonathan Larmour [this message]
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=42681D54.4020704@jifvik.org \
--to=jifl@jifvik.org \
--cc=ecos-maintainers@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).