From: Mark Knecht <markknecht@attbi.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: hdsp 9652
Date: 28 Apr 2003 19:12:38 -0700 [thread overview]
Message-ID: <1051582358.3552.16.camel@localhost.localdomain> (raw)
In-Reply-To: <E197wsM-0002Vn-00@sc8-sf-list1.sourceforge.net>
On Tue, 2003-04-22 at 05:31, Paul Davis wrote:
> > I have written Paul a couple of times asking some questions but have
> >not received a response. Perhaps Paul never actually listened to the
> >card, or perhaps he has different firmware and his works. I cannot tell
> >as of today.
>
> i was in boston for the marathon. i will be looking into this today
> and/or tomorrow.
>
> --p
Hi,
Has anyone heard from Paul on this? Another week's gone by. I checked
the archives, but didn't find any more info.
I'd just like to make use of this card.
Thanks,
Mark
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-04-29 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304051339.h35DdJb02474@linuxaudiosystems.com>
2003-04-17 16:15 ` hdsp 9652 Mark Knecht
2003-04-22 12:31 ` Paul Davis
2003-04-29 2:12 ` Mark Knecht [this message]
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=1051582358.3552.16.camel@localhost.localdomain \
--to=markknecht@attbi.com \
--cc=alsa-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox