All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zephiris <zephiris@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: ATI IXP hardware mixing
Date: Thu, 14 Sep 2006 08:47:49 -0700	[thread overview]
Message-ID: <eebtj7$qrn$1@sea.gmane.org> (raw)
In-Reply-To: 1158247753.7948.77.camel@mindpipe

Lee Revell wrote:

> On Thu, 2006-09-14 at 08:16 -0700, Zephiris wrote:
>> Lee Revell wrote:
>> 
>> > On Thu, 2006-09-14 at 07:19 -0700, Zephiris wrote:
>> >> Since people in ALSA devel channel won't answer, I'll have to ask on
>> >> mailing-list/newsgroup. I'm trying to get the ATI IXP driver to use
>> >> hardware mixing. The hardware supports it, FreeBSD and Windows support
>> >> it, and all I want is to know is what to change in the source that
>> >> needs to support it, since several glances through the source and
>> >> brief API docs, as well as mailing lists, etc, don't reveal
>> >> effectively nothing supporting hardware mixing at all.
>> > 
>> > How do you know the device is capable of hardware mixing?
>> > 
>> > Lee
>> > 
>> > 
>> Other operating systems support hardware mixing on it. FreeBSD reportedly
>> does, Windows definitely does (yay for hardware acceleration of DS/DS3D,
>> too; up to 26 streams) and I didn't ask 'if' it does, I asked how to try
>> to work with hardware mixing in ALSA. Documentation, general walk-through
>> of the steps required in difference to non-hardware mixed, anything,
>> please?
>> 
>> I've been getting short-changed on answers so far (and was previously
>> stonewalled on AU8830 support, back when people in ALSA channels cheerily
>> claimed you couldn't get hardware mixing on that, either), and it's
>> getting frustrating. I'm not asking for a lecture on "you can't do that
>> because it's not status quo", but merely how to implement such changes in
>> the source code.
> 
> Um... if the device can't do hardware mixing, how can changing the
> driver help?
> 
> Windows and FreeBSD are using software mixing.
> 
> Lee

People associated with ALSA have been daft enough to say that before about
sound cards that had exquisite hardware mixing, is it really too much to
ask for a simple parcel of information that appears to be omitted from the
documentation I can find for ALSA? I swear, if the consistently
condescending/fek-you attitude from ALSA over many years is any indication,
no wonder it moves like slag compared to other sound drivers and almost
never gets reasonably "full" support for any particular chipset. -_-

I already said I wasn't looking for more statements of non-support, but just
how such things have to be done in the source code. People should really
read once and a while.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-09-14 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 14:19 ATI IXP hardware mixing Zephiris
2006-09-14 14:58 ` Lee Revell
2006-09-14 15:16   ` Zephiris
2006-09-14 15:29     ` Lee Revell
2006-09-14 15:47       ` Zephiris [this message]
2006-09-14 15:55         ` Lee Revell
2006-09-15  7:28         ` Clemens Ladisch

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='eebtj7$qrn$1@sea.gmane.org' \
    --to=zephiris@gmail.com \
    --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.