All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Hollis <goemon@sasami.anime.net>
To: linux-sound@vger.kernel.org
Subject: Re: 4D-NXs (was Re: Sync Issues)
Date: Wed, 27 Oct 1999 20:06:30 +0000	[thread overview]
Message-ID: <marc-linux-sound-94105520414258@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94102459902838@msgid-missing>

On Wed, 27 Oct 1999, Paul Barton-Davis wrote:
>       * "we don't have enough programmers to do that"

If the drivers are being written for them by volunteers, I dont see how
this is relevant.

>       * "we don't have any written documentation to give you guys -
>          we wrote the driver by having the software group sit in with
> 	 the hardware group"

This should be a warning sign to anyone thinking of purchasing their
hardware. If a company cant be bothered to internally document the
hardware, what happens if key engineers leave the company? Oh dear, their
project is *permanently screwed*, which means zero support for end users.
This is no way to run a company.

>       * "we think our hardware's proprietary secrets will be revealed
>          if there is a source code driver"

Uh, isnt this what patents are for? If someone reverse engineers their
card, they are *completely screwed* unless they have patent protection.

-Dan

  parent reply	other threads:[~1999-10-27 20:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 11:40 4D-NXs (was Re: Sync Issues) Billy Biggs
1999-10-27 11:54 ` Jaroslav Kysela
1999-10-27 13:53 ` Paul Barton-Davis
1999-10-27 20:06 ` Dan Hollis [this message]
1999-10-27 22:53 ` David Olofson
1999-10-28  0:04 ` Paul Barton-Davis
1999-10-28  0:23 ` Dan Hollis
1999-10-28  0:38 ` Paul Barton-Davis
1999-10-28  0:50 ` Dan Hollis
1999-10-28  2:46 ` John Littler
1999-10-28 12:39 ` Paul Barton-Davis
1999-10-28 18:33 ` Dan Hollis

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=marc-linux-sound-94105520414258@msgid-missing \
    --to=goemon@sasami.anime.net \
    --cc=linux-sound@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 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.