From: Abramo Bagnara <abramo@alsa-project.org>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: format specification problem
Date: Thu, 25 Apr 2002 11:31:10 +0200 [thread overview]
Message-ID: <3CC7CCDE.33837A2B@alsa-project.org> (raw)
In-Reply-To: 200204250055.g3P0tu908360@op.net
Paul Davis wrote:
>
> [ those of you on jack-dev will have seen this coming ]
>
> ALSA doesn't seem to provide a way for a driver to way "i provide
> samples in the native format of the processor". The specific case in
> point that I'm noticing is the Hammerfall, where we currently say that
> it supports S32_LE. This is not strictly true. It supports S32_LE when
> it has the x86-friendly EPROM, and S32_BE when it has the ppc-friendly
> EPROM. But it can't support them both at the same time. Moreover,
> there isn't any way to find out which EPROM it has - its assumed that
> the user is sufficiently smart not to have installed a PPC version on
> an x86 system (I actually had a user recently who had this problem and
> didn't realize it - they spent days trying to figure why their samples
> were byte-swapped).
>
> If an application wants to ask for S32 in "native" format, it can do
> that, but <alsa/asoundlib.h> will convert that into either S32_LE or
> S32_BE, and when we get down the driver level, it will fail on some
> systems.
>
> How can we address this? I doubt that the Hammerfall is the only card
> with this problem ...
>
Actually they're two different cards, so they need to be treated as
such. I think that a module option is a suitable solution.
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project http://www.alsa-project.org
It sounds good!
next prev parent reply other threads:[~2002-04-25 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 0:55 format specification problem Paul Davis
2002-04-25 9:31 ` Abramo Bagnara [this message]
2002-04-26 17:34 ` 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=3CC7CCDE.33837A2B@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=pbd@op.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.