From: Thomas Charbonnel <thomas@undata.org>
To: Winfried Ritsch <ritsch@iem.at>
Cc: alsa list <alsa-devel@lists.sourceforge.net>
Subject: Re: hdsp driver and tools update
Date: Thu, 06 Nov 2003 15:14:01 +0100 [thread overview]
Message-ID: <3FAA5729.9010601@undata.org> (raw)
In-Reply-To: <16295.61169.732364.138708@seneca.iemnet>
Winfried Ritsch wrote :
>
> Hello,
>
> Thanx for the work, just 2 cosmetic questions:
>
> (just testing and comparing HDSP9552 /HDSP9632 and HDSP-MADI on
> function, so I fall over these:)
>
>
>
> I have a questions to the patch:
>
> 1)
> +#define H9632_SS_CHANNELS 12
> +#define H9632_DS_CHANNELS 8
> +#define H9632_QS_CHANNELS 4
>
> I always thought the HDSP96 can use 16 channels in Single speed
> since you can use
> adat (8) + analog (2) + spdif (2) + optional 4 channels expansion
> at the same time.
>
It is the case. You seem to have missed the comment just above those
lines stating that extension boards were checked for at initialization time.
>
> 2) different IOextents on different cards
>
> +#define HDSP_IO_EXTENT 7168
>
> maybe its safer to use
>
> io_extent= pci_resource_len(pci,0);
>
> (in the hdsp_createfunction instead of giving a fix one.)
>
>
This covers only the specific part of the card's memory we need to map.
> 3) should we change the the hw_params so that only needed channels are
> enabled (and change the ruleset to it) ?
>
This is not essential for non-madi cards, but if this results in a
performance enhancement, maybe we should backport your work to the
non-madi driver. On the other hand how would you handle the capture side
of this ? As you mentioned in an earlier post, during playback as few as
one channel can be used and still, thanks to the matrix mixer, any
physical output can send the signal. For recording this is a problem
because capture channels are hardwired to physical inputs. How would you
choose the recording channel ?
Thomas
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-11-06 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 11:19 hdsp driver and tools update Thomas Charbonnel
2003-11-01 14:01 ` Mark Knecht
2003-11-03 9:14 ` Roslyn Hoskin
2003-11-03 13:31 ` Thomas Charbonnel
2003-11-03 12:15 ` Takashi Iwai
2003-11-04 17:25 ` Justin Cormack
2003-11-04 18:24 ` Winfried Ritsch
2003-11-06 14:14 ` Thomas Charbonnel [this message]
2003-11-05 2:38 ` Roslyn Hoskin
-- strict thread matches above, loose matches on Subject: below --
2003-11-03 13:39 Thomas Charbonnel
2003-11-03 19:11 ` 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=3FAA5729.9010601@undata.org \
--to=thomas@undata.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ritsch@iem.at \
/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.