All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr>
To: "Måns Rullgård" <mru@users.sourceforge.net>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Re: Fwd: RE: To ESS Tech Support
Date: Fri, 13 Jun 2003 20:53:53 +0300	[thread overview]
Message-ID: <200306132053.53350.p_christ@hol.gr> (raw)
In-Reply-To: <yw1x1xxye1gk.fsf@zaphod.guide>

> Warren Turkal <wturkal@cbu.edu> writes:
> > Another message from the ESS people. If some other people could take
> > the time to request this info from ESS also, maybe they would be
> > more forthcoming with the info.
>
> Tell them you want the complete specs for the chip, and are willing to
> sign an NDA.  That might help.

That may not be accurate. If you're writing a driver for linux, you most 
probably want to publish it under GPL, which definitely conflicts with the 
NDA. The NDA should be about the chip only, not the driver.

The real case you should stick at (the one for any such case) is that nobody 
could actually use the linux driver without owning the product, for which 
we've paid. Tell them that by supporting (it's so easy for them) linux, they 
get themselves out of the "non-desirable" hardware list. We (linux users) 
have several lists with hw and companies we should avoid. ESS is one of them.



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

  reply	other threads:[~2003-06-13 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  7:08 Fwd: RE: To ESS Tech Support Warren Turkal
2003-06-13 10:06 ` Måns Rullgård
2003-06-13 17:53   ` P. Christeas [this message]
2003-06-13 18:28     ` Måns Rullgård
2003-06-13 19:13       ` Daniel Berlin

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=200306132053.53350.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mru@users.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.