All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Williams <raw@qux.com>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: markknecht@attbi.com, Alsa-devel@lists.sourceforge.net
Subject: Re: hdsp multiface pci.
Date: 22 Jan 2003 13:30:50 -0500	[thread overview]
Message-ID: <m3el75ghph.fsf@grouper.coelacanth.com> (raw)
In-Reply-To: <200301221814.h0MIEnx0013504@spider.tela.com>

>>>>> Paul Davis <paul@linuxaudiosystems.com> writes:

  >> This would explain why snd_hdsp works (i.e. you can playback and
  >> record through the default I/O), although amixer doesn't do
  >> anything: the driver doesn't have to set up any default
  >> connections, because those are part of the FPGA reset state...

  > actually, the driver does have to set up default connections,
  > which are zero gain for every possible routing...

Yes, I understand that that's what the driver is _supposed_ to do.
That's how it works on my HDSP PCI and Cardbus systems.  But isn't it
true that the current driver doesn't actually set up any of those
zero-gain connections for the HDSP 9652?

This is the only point that I was trying to make to Mark -- the
default unity-gain connections (i.e. playback -> H/W output) that he
has been using are FPGA configuration defaults, not explicitly set up
by the driver.

-- 
Roger Williams <raw@qux.com>
Qux Tool & Die, Middleborough, Massachusetts
// Omne tulit punctum qui misquit utile dulci //


-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp

  reply	other threads:[~2003-01-22 18:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E18aeXp-00009y-00@sturgeon.coelacanth.com>
2003-01-20 17:01 ` hdsp multiface pci Roger Williams
2003-01-22 18:19   ` Paul Davis
2003-01-22 18:30     ` Roger Williams [this message]
2003-01-22 18:41       ` Paul Davis
2003-01-22 18:54       ` Mark Knecht
2003-01-20 16:12 markknecht
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20 15:57 markknecht
2003-01-19 12:08 Patrick Shirkey
2003-01-19 14:12 ` Thomas Charbonnel
2003-01-19 15:29   ` Patrick Shirkey
2003-01-19 15:55     ` Patrick Shirkey
2003-01-19 16:07     ` Thomas Charbonnel
2003-01-19  8:23       ` Mark Knecht
2003-01-19 17:27         ` Thomas Charbonnel
2003-01-19 16:33       ` Patrick Shirkey
2003-01-19 17:00         ` Roger Williams
2003-01-19 12:21           ` Mark Knecht
2003-01-19 22:24             ` Roger Williams
2003-01-19 16:34               ` Mark Knecht
2003-01-20  2:14                 ` Roger Williams
2003-01-19 19:59                   ` Mark Knecht
2003-01-20  6:25                     ` Roger Williams
2003-01-20  5:06                       ` Mark Knecht
2003-01-20 13:46                         ` Roger Williams
2003-01-20  6:44                     ` Roger Williams
2003-01-20  8:31                       ` Marcus Andersson
2003-01-20 13:35                         ` Roger Williams
2003-01-19 17:01         ` Patrick Shirkey
2003-01-19 17:20         ` Thomas Charbonnel
2003-01-19 23:12           ` Roger Williams

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=m3el75ghph.fsf@grouper.coelacanth.com \
    --to=raw@qux.com \
    --cc=Alsa-devel@lists.sourceforge.net \
    --cc=markknecht@attbi.com \
    --cc=paul@linuxaudiosystems.com \
    /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.