The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Valdis.Kletnieks@vt.edu,
	"Fredrik Markström" <fredrik.markstrom@avalonenterprise.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Developing non-commercial drivers ?
Date: Tue, 18 Nov 2008 15:20:57 -0500	[thread overview]
Message-ID: <20081118202057.GF29975@mit.edu> (raw)
In-Reply-To: <20081118192942.3c676f0d@lxorguk.ukuu.org.uk>

On Tue, Nov 18, 2008 at 07:29:42PM +0000, Alan Cox wrote:
> 
> Not entirely. There are several reasons this may occur
> - They could have something genuinely new - unlikely to be honest
> - They could think they have something genuinely new but don't
> - They may not yet have filed some relevant patent applications in which
> case they have to worry about secrecy
> 
> and other reasons.
> 

If I had to guess, they're probably doing some kind variant of TCP,
Crypto, or some other kind of networking offland trick.  There really
isn't much else you can do that might be considered new in an ethernet
controller.  And it's probably not new.

> Probably they should talk to the Linux Foundation. I'm not sure that
> assuming they are clueless is the first step. Understanding the problem
> as they see it is more important and probably something the Linux
> Foundation can help with and under a business to business framework.

Well, I'm from the Linux Foundation, and I'm here to help.  :-)

Seriously, if they are willing to talk to someone, we're certainly
willing to give them some free advice.  My guess is that's not very
likely, however.

						- Ted


  reply	other threads:[~2008-11-18 20:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 16:16 Developing non-commercial drivers ? Fredrik Markström
2008-11-18 16:29 ` Robert Hancock
2008-11-18 16:52   ` Fredrik Markström
2008-11-18 17:04     ` Robert Hancock
2008-11-18 17:17     ` Xavier Bestel
2008-11-18 17:17     ` Chris Friesen
2008-11-18 18:00       ` Radhakrishnan
2008-11-18 18:13         ` Chris Friesen
2008-11-18 18:33           ` linux-os (Dick Johnson)
2008-11-18 17:40     ` Alan Cox
2008-11-22 18:16     ` Dr. David Alan Gilbert
2008-11-18 17:32 ` Alan Cox
2008-11-18 19:25 ` Valdis.Kletnieks
2008-11-18 19:29   ` Alan Cox
2008-11-18 20:20     ` Theodore Tso [this message]
2008-11-18 21:13       ` Fredrik Markström
2008-11-18 23:28         ` Theodore Tso
2008-11-19 18:38 ` Lennart Sorensen
2008-11-19 22:32   ` Fredrik Markström
2008-11-19 22:47     ` Lennart Sorensen
2008-12-01  0:19 ` Enrico Weigelt

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=20081118202057.GF29975@mit.edu \
    --to=tytso@mit.edu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fredrik.markstrom@avalonenterprise.com \
    --cc=linux-kernel@vger.kernel.org \
    /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