From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Karel Kulhav? <clock@twibright.com>, linux-kernel@vger.kernel.org
Subject: Re: Compatibility of Nvidia NVNET driver license with GPL
Date: Sat, 3 Jan 2004 13:53:21 -0500 [thread overview]
Message-ID: <20040103185321.GA8379@gtf.org> (raw)
In-Reply-To: <20040103184434.GD1080@elf.ucw.cz>
On Sat, Jan 03, 2004 at 07:44:34PM +0100, Pavel Machek wrote:
> Hi!
>
> > If you are serious about this, we have tons of good ideas, and tons of
> > suggestions on how to avoid bad ideas :)
> >
> > OpenCores (http://www.opencores.org/) might be a good place to start, as
> > they already have a 10/100 ethernet MAC which is working, and has been
> > silicon'd: http://www.opencores.org/projects/ethmac/ Full "source" for
> > the MAC is available, in VHDL I think. OpenCores also has PCI VHDL and
> > other glue you may need.
> >
> > You'll definitely want to implement autonegotiation. It's a showstopper
> > without that. And if it's not gigabit ethernet, it's already outdated.
> > So it's a tough challenge.
>
> AFAIK, Clock is developing
> ethernet-over-infrared-over-300meters-of-air. It knows what is at the
> other end, and probably does not need autonegotiation. It is probably
> not going to be gigabit, either. [Current version that works is 10mbit
> over ~300meters].
FWIW autonegotiation is strictly related to "the wire", so wireless
would be a totally different space.
Jeff
next prev parent reply other threads:[~2004-01-03 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 6:31 Karel Kulhavý
2003-12-31 6:36 ` Jeff Garzik
2003-12-31 10:43 ` Karel Kulhavý
2003-12-31 13:00 ` Jeff Garzik
2004-01-03 18:44 ` Pavel Machek
2004-01-03 18:53 ` Jeff Garzik [this message]
2004-01-01 5:11 ` Paul Jackson
2004-01-01 17:48 ` Jeff Garzik
2004-01-02 17:04 ` Chuck Campbell
2004-01-02 20:09 ` Jan-Benedict Glaw
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=20040103185321.GA8379@gtf.org \
--to=jgarzik@pobox.com \
--cc=clock@twibright.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
Powered by JetHome