All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: Craig Bourne <craigbourne@gmail.com>
Cc: Fernando Lopez-Lezcano <nando@ccrma.stanford.edu>,
	alsa-devel@alsa-project.org
Subject: Re: hdspmixer segfault (1.0.24+)
Date: Mon, 28 Feb 2011 22:21:56 +0100	[thread overview]
Message-ID: <4D6C11F4.6000408@drcomp.erfurt.thur.de> (raw)
In-Reply-To: <AANLkTikr=sBcis_2V=qm9jgWha3P6QR2-xiY9WpXw+vH@mail.gmail.com>

On 02/28/11 18:23, Craig Bourne wrote:

> PCI Busmaster Digital I/O System
> 2 + 24 Channels SPDIF / ADAT Interface

I've digged into the driver source. Your H9652 is more or less a
Digiface. The channel *count* was never a question, this is defined by
the driver anyway. The remaining question simply was how to label the
output destinations.

>From the manual, the answer is pretty obvious: ADAT-1.1 to ADAT-1.8,
followed by ADAT-2.1 to ADAT-2.8 and ADAT 3.1-to 3.8, last is S/PDIF.

In double-speed mode (everything above 48kHz), the ADAT channels are cut
in half, so ADAT 1.1 to ADAT 1.4, ADAT 2.1 to 2.4 and so on. S/PDIF
remains unchanged as it supports higher sample rates at static channel
counts (like AES/EBU).


> At various times in the past when one was required to specify (e.g.,
> Input/Output) channels to an ALSA tool (or a program that relied on
> the ALSA sound architecture) a mismatch in this number (presumably of
> pcm channels) had less than desirable consequences.

We're not talking driver here, the critical parts remain unchanged in
the kernel.


> All of this leads me to the conjecture that fudging an arbitrary
> number that stands in for "channels" is perhaps not the best course
> (not to forget that, at the end of our testing, I would hope that this
> sound card that costs as much as the computer that houses it will not
> have suffered any damage).

Of course, this is open source. It comes without any warranty and you're
free to avoid it, but to the best of my knowledge, you must not be
afraid.

Firstly, it's userspace, so nothing can really kill your card. Second,
the whole logic is an FPGA, so it can always be flashed to a working
state if something goes wrong (it cannot go wrong, as you cannot
accidentally flash your card). Last but not least: the channel count has
always been correct, 26 all the time, only the name array was missing.

So we have this "read 26 channel names from the naming array", and it's
now a question which names to write in there. I've given the answer
above, but want to stress again that we're talking pure C pure userland
here, so it's close to a hello world program:

   printf("Channel name is %s\n", name_array[channel_number]);

with name_array being something like { "ADAT-1.1", "ADAT-1.2", .. } and
so on. Right now, with the package prepared by Fernando, you'll simply
see "1", "2", .. "26" instead of "ADAT-1.1", but this will change in a
minute.


HTH

  parent reply	other threads:[~2011-02-28 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27  0:55 hdspmixer segfault (1.0.24+) Fernando Lopez-Lezcano
2011-02-27 11:17 ` Adrian Knoth
2011-02-27 19:21   ` Fernando Lopez-Lezcano
2011-02-27 23:54     ` Fernando Lopez-Lezcano
2011-02-28 16:20       ` Adrian Knoth
     [not found]         ` <AANLkTikr=sBcis_2V=qm9jgWha3P6QR2-xiY9WpXw+vH@mail.gmail.com>
2011-02-28 19:34           ` Fernando Lopez-Lezcano
2011-02-28 21:21           ` Adrian Knoth [this message]
     [not found]             ` <AANLkTik8uJT885D0yQd4mbs_ytxYrq2wp6=5hsFvN1V3@mail.gmail.com>
2011-02-28 22:00               ` Adrian Knoth

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=4D6C11F4.6000408@drcomp.erfurt.thur.de \
    --to=adi@drcomp.erfurt.thur.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=craigbourne@gmail.com \
    --cc=nando@ccrma.stanford.edu \
    /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.