From: Takashi Iwai <tiwai@suse.de>
To: bbennetts@blueyonder.co.uk
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Known PCM bug in ymfpci on Tecra 8100
Date: Tue, 13 Jul 2004 19:27:37 +0200 [thread overview]
Message-ID: <s5hllhnakc6.wl@alsa2.suse.de> (raw)
In-Reply-To: <5B596E67A1B90F48A466D8DF19E1F49703713CEC@ECOWV06M.Telewest.Internal>
At Tue, 13 Jul 2004 18:21:54 +0100,
<bbennetts@blueyonder.co.uk> wrote:
>
> >>
> >> Hi,
> >>
> >> Has anyone had any joy fixing this problem? If not is there anything I can do
> >> to help? I am willing to attempt debugging if someone will point me at a
> >> 'dummy's guide' to attaching a debugger to ALSA.
> >>
> >> Sorry if this was a dumb question, I can see the bug is known but couldn't
> >> find any open bug in the bug tracker.
> >
> >What kind of bug? If you don't find one on BTS, please enter it.
> >
> >
> >thanks,
> >
> >Takashi
>
> Hmm, in the ymfpci description it has :
>
> Known bugs
>
> - pcm playback is not audible on toshiba tecra8100.
Ah, that one...
> I _do_ get sound, unfortunately its just crackly static noise:-(
>
> I shall raise it as a bug.
Yes, please.
It's likely the lack of some register initiailzation, since OSS ymfpci
and the old ALSA 0.5.x ymfpci seem working. The question is which
register affects this.
Takashi
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-07-13 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:21 Known PCM bug in ymfpci on Tecra 8100 bbennetts
2004-07-13 17:27 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 17:39 bbennetts
2004-07-13 7:02 Bryan Bennetts
2004-07-13 16:22 ` 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=s5hllhnakc6.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bbennetts@blueyonder.co.uk \
/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.