From: James Courtier-Dutton <James@superbug.co.uk>
To: Dmitry Baryshkov <mitya@school.ioffe.ru>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Audigy2 P16V testing
Date: Fri, 07 Jan 2005 21:11:29 +0000 [thread overview]
Message-ID: <41DEFB01.4080004@superbug.co.uk> (raw)
In-Reply-To: <20050107121731.GA3982@school.ioffe.ru>
Dmitry Baryshkov wrote:
> Hello,
>
> Please correct me if this is wrong place for this post.
>
> I tried testing p16v patch from www.alsa-project.org/~james/p16v
> (the last one, where p16v is merged with emu10k1).
> I applied patch & copied p16v.c to alsa 1.0.8rc2. emu10k1 driver
> compiled & inserted successfully. But when I tried to play self-generated
> SE32_LE@96Khz wav file (aplay -D hw:0,3 test.wav) I got no sound & a
> lot of messages in kernel log (attached).
>
> I'm using kernel 2.6.9.
>
> Just in case here is related part of lspci -v:
>
That driver is not supposed to work yet.
See the readme.txt file.
I previously called it README.txt, but for some reason the web server
decided to hide the README.txt file, and only displays it if I rename it
to readme.txt
Summary:
That file is only there for the purposes of backup, while I work in it.
Cheers
James
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
prev parent reply other threads:[~2005-01-07 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 12:17 Audigy2 P16V testing Dmitry Baryshkov
2005-01-07 21:11 ` James Courtier-Dutton [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=41DEFB01.4080004@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mitya@school.ioffe.ru \
/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