All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: "John L. Utz III" <john.utz@dmx.com>
Cc: alsa-devel@alsa-project.org, Andreas Mohr <andi@lisas.de>
Subject: Re: [PATCH] Try to make our poor little ALS4000 driver worthy of its copious public specs (first step)
Date: Wed, 20 Aug 2008 00:24:29 +0200	[thread overview]
Message-ID: <48AB481D.3030506@keyaccess.nl> (raw)
In-Reply-To: <op.uf5mf6ih647oa9@jutz-gnto64>

On 20-08-08 00:08, John L. Utz III wrote:

>> Never omitting any opportunity to complain about missing vendor 
>> cooperation, but what do they do once people actually do publish
>> ample specs? - yeah, you got that right: NOTHING!!
> 
> Congratulations on your patch, but i dont think this comment was 
> particularly helpful.

Oh, come one. He had his tongue quite firmly and definitely in cheek...

> Had the spec been released concurrent with the release of the chip,
> who knows what would have happened?
> 
> The ALS4k is not currently manufactured, so there is not a good
> reason to invest development resources in supporting it.
> 
> Time is better spent supporting new chips so that new distro releases
> can support new computers so that computer vendors and end users will
> feel less put out by having linux as the default OS for their brand
> new computer!

One of the main reasons for wanting specs over vendor supplied drivers 
in fact is to be able to support _old_ hardware -- hardware that the 
manfacturer feels no need to support anymore, but the users still want 
to use. As such, I believe the above is definitely off the mark.

But anyways, he was definitely being "joke-ish". You took it way too 
seriously.

Rene.

  reply	other threads:[~2008-08-19 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 20:34 [PATCH] Try to make our poor little ALS4000 driver worthy of its copious public specs (first step) Andreas Mohr
2008-08-19 22:08 ` John L. Utz III
2008-08-19 22:24   ` Rene Herman [this message]
2008-08-19 22:30     ` John L. Utz III
2008-08-20  8:40 ` Takashi Iwai

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=48AB481D.3030506@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=andi@lisas.de \
    --cc=john.utz@dmx.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 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.