From: "Ivica Bukvic" <ico@fuse.net>
To: 'Takashi Iwai' <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: RE: Question regarding current ESS Maestro 3M soundcard support
Date: Sat, 16 Feb 2002 22:46:05 -0500 [thread overview]
Message-ID: <000001c1b765$a0916e70$ac1f830a@ico> (raw)
In-Reply-To: <s5hlmdz54vt.wl@alsa2.suse.de>
Hi, I want to thank you very much for your comprehensive response. I've
written to the ess support e-mail pleading for more Linux support and
got no response (no surprise there). Is there any way that we can start
a petition or somehow force them to release the specs (even if needed
under NDA agreement to a few persons such as yourself who would be
capable of improving the driver)? Also, what are the chances for
reverse-engineering the Windows drivers to build a better Linux driver?
Ivica Ico Bukvic
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Sent: Tuesday, February 12, 2002 6:14 AM
> To: Ivica Bukvic
> Cc: alsa-devel@alsa-project.org; alsa-user@alsa-project.org
> Subject: Re: [Alsa-devel] Question regarding current ESS Maestro 3M
> soundcard support
>
> Hi,
>
> At Mon, 11 Feb 2002 21:28:53 -0500,
> Ivica Bukvic wrote:
> >
> > Hi all!
> >
> > I have an Dell Inspiron 8K and my question is whether the current
> > Maestro M3 chip is fully supported or does it currently only furnish
> > SB16 compatibility mode (I might be talking nonsense here, but this
is
> > what I heard a while ago, or something like it and my understanding
is
> > that the current driver support is only partial due to incomplete
> > disclosure of the hw specs by the ESS, again, please correct me if I
am
> > wrong). Basically, from my understanding it seems that the M3
soundcard
> > is being classified as a "sound accelerator" (whatever that means),
and
> > as such I would expect it to be capable of mixing audio streams in
> > hardware (just as emu10k1 chip does, even though emu10k1 is much
more
> > powerful). So far, I was only able to get one stream out of the card
in
> > the latest ALSA driver, while I got 2 streams with the OSS-Free
drivers
> > (third stream would garble the two existing streams and return an
i/o
> > error).
>
> So it is on ALSA, too.
> Theoretically more could be, but it seems that the (only one) DSP code
> provided from ESS has a bug.
>
>
> > So, is this the default behavior?
>
> Yes.
>
>
> > I would assume that most of the modern-day cards should be capable
of
> > down-mixing at least 16 or 32 streams of sound, since that is what
they
> > are usually capable of reproducing in Windows at any given time
(unless
> > in Windows the down-mixing is done in software, which is certainly a
> > possibility and in many cases a known fact).
> >
> > So, my questions are:
> >
> > Is this a hardware limitation?
>
> No.
>
> > or
> >
> > Is this current driver's limitation?
>
> Yes.
>
> > If the second is the case, then what are the chances of improving
this
> > issue in the nearby future?
>
> Only if we receive detailed information of DSP engine or better DSP
> codes from ESS.
>
>
> > Finally, what are the chances of getting the ESS to talk and give us
the
> > exact specs for this soundcard so that the driver can be finished?
>
> Unfortunately ESS is famous to provide the only minimum information,
> so far. I hope this will change in future..
>
>
> ciao,
>
> Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next parent reply other threads:[~2002-02-17 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5hlmdz54vt.wl@alsa2.suse.de>
2002-02-17 3:46 ` Ivica Bukvic [this message]
2002-02-18 15:40 ` Question regarding current ESS Maestro 3M soundcard support Steve Harris
[not found] <000101c1b36d$036851a0$ac1f830a@ico>
2002-02-12 11:14 ` Takashi Iwai
2002-02-12 12:04 ` Steve Harris
2002-02-12 2:28 Ivica Bukvic
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='000001c1b765$a0916e70$ac1f830a@ico' \
--to=ico@fuse.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.