From: Manuel Jander <manuel.jander@mat.utfsm.cl>
To: Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [Alsa-user] shittiness
Date: Tue, 20 Jan 2004 08:19:16 -0400 [thread overview]
Message-ID: <1074601156.21484.5.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0401201006340.1857@pnote.perex-int.cz>
Hi,
On Tue, 2004-01-20 at 05:14, Jaroslav Kysela wrote:
> On Tue, 20 Jan 2004 markc@renta.net wrote:
>
> > So that you and I and the rest of us will test both the kernel and
> > ALSA, and the kernel+ALSA, under various hardware conditions that
> > will never happen until either is declared "stable". Allow about 1/2
> > a year for both, and the combination of both, to truly stablize.
> > It may seem like a non-professional way to go about it but in the
> > larger scheme of things, where some of us have been waiting _years_
> > (let alone those who have been doing the actual work) for a single
> > truly open source audio environment, it's getting very close to being
> > the ultimate system "we" have been waiting for.
>
Just sitting around and waiting a given amount of time will not make any
software more stable. It could even be bad in the sense that people stop
using it due to the lack of new releases. Thats very frustrating.
> Before flames, I would like to notice that we have only limited amount of
> hardware for tests. The current hardware vendors are producing very large
> number of configurations, modifications etc. especially for cheap
> hardware. It's very difficult to support all variations, so please, be
> patient until a developer analyses the given problem and fix it.
>
> If you know the ethernet drivers (eepro100), you might noticed that in
> past, there were / are also some issues, because many transciever
> variations and configurations exists around. It's not about API, but it's
> about particular driver.
>
> Also, we do not have any links with most of hardware vendors, so we very
> depend on free information about their hardware.
>
Personally i have felt this "many variation hardware" by myself. I'm
still unable to reproduce some problems that someone reported to me with
a soundcard which i dont own, even if i bought upto 3 different cards by
my self, and all 3 of them work flawless. But then again i can only test
them on my computer and the PC of my brother.
To do more testing, we need to widespread it. I don't see another way.
I agree 100% with Jaroslav.
Best Regards
Manuel Jander
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-01-20 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401170141.16791.steveconrad@lincsatmail.com>
[not found] ` <400C565D.4050906@reachone.com>
[not found] ` <20040119222121.5540c721.rkimber@ntlworld.com>
[not found] ` <200401200931.10121.markc@renta.net>
2004-01-20 9:14 ` [Alsa-user] shittiness Jaroslav Kysela
2004-01-20 12:19 ` Manuel Jander [this message]
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=1074601156.21484.5.camel@localhost \
--to=manuel.jander@mat.utfsm.cl \
--cc=alsa-devel@lists.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.