From: Corvus Corax <corvus-ml@cybertrench.com>
To: "D. Hugh Redelmeier" <hugh@mimosa.com>
Cc: alsa-devel@lists.sourceforge.net, Peter Zubaj <pzad@pobox.sk>,
Mikael Magnusson <mikaelmagnusson@glocalnet.net>
Subject: Re: lo10K1 not working on x86_64 ?
Date: Wed, 9 Nov 2005 23:49:58 +0100 [thread overview]
Message-ID: <20051109234958.4040a03e@VikingPC.home> (raw)
In-Reply-To: <Pine.LNX.4.61.0511091339240.16661@redshift.mimosa.com>
Am Wed, 9 Nov 2005 13:47:55 -0500 (EST)
schrieb "D. Hugh Redelmeier" <hugh@mimosa.com>:
>
> I know nothing about what ld10k1 does nor have I run it, but I did
> submit some fixes to its code. These fixes correct a bug that would
> manifest itself on x86_64. They are now in CVS (as of today).
>
> See https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1533
>
> Perhaps this fixes the problems you observed. I have no way of
> knowing. You might consider testing HEAD.
>
Confirmed, the problem seems NOT to occur with ld10k1 compiled from the current
CVS HEAD
init_live now produces a working routing.
Thanks all for your help :-))
best regards
Corvus Corax
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-11-09 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 20:20 lo10K1 not working on x86_64 ? Corvus Corax
2005-11-03 12:01 ` Mikael Magnusson
2005-11-09 1:04 ` Corvus Corax
2005-11-09 13:13 ` Corvus Corax
2005-11-09 18:47 ` D. Hugh Redelmeier
2005-11-09 22:18 ` Corvus Corax
2005-11-09 22:36 ` Corvus Corax
2005-11-09 22:49 ` Corvus Corax [this message]
2005-11-10 17:09 ` D. Hugh Redelmeier
2005-11-10 22:24 ` Corvus Corax
2005-11-09 19:02 ` Peter Zubaj
2005-11-09 21:47 ` Corvus Corax
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=20051109234958.4040a03e@VikingPC.home \
--to=corvus-ml@cybertrench.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=hugh@mimosa.com \
--cc=mikaelmagnusson@glocalnet.net \
--cc=pzad@pobox.sk \
/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.