From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Capture All <capture_all@yahoo.com>
Cc: netdev@oss.sgi.com
Subject: Re: forthdeth
Date: Fri, 23 Jan 2004 12:35:02 +0100 [thread overview]
Message-ID: <401106E6.2070605@gmx.net> (raw)
In-Reply-To: <20040123055612.78211.qmail@web80809.mail.yahoo.com>
Capture All wrote:
> Hello Sir, I am going to port the nvnet driver to windows ce version.
If Windows CE is running on anything that needs nvnet, NVidia will port
the driver themselves, I'm sure.
> Could I got a copy of the src from you? Also, you mentioned there is a
> specification about the reverse engineering. Could you send it to me
> also?
Sorry, but neither I nor any of the other forcedeth developers have any
source of nvnet and we never want to have it because it would taint us.
The specification is private and will never be shared with anybody because
we do not want to get into legal trouble.
> I looked into this page, found there are some patches. Does any of the
> patch includes all the source I need? For example
> forcedeth_2_6_patch_v20.txt ?
>
> http://www.hailfinger.org/carldani/linux/patches/forcedeth/
None of this patches will help you at all if you want to port nvnet
because forcedeth is written based on a spec that includes only nic
initialization and packet rx/tx and none of the inner workings and
structures of nvnet.
> Thanks! Blues
Sorry to disappoint you, but maybe you should ask NVidia if they release a
Windows CE version of their driver.
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2004-01-23 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 5:56 forthdeth Capture All
2004-01-23 11:35 ` Carl-Daniel Hailfinger [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=401106E6.2070605@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=capture_all@yahoo.com \
--cc=netdev@oss.sgi.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 NNTP newsgroup(s).