From: Takashi Iwai <tiwai@suse.de>
To: ico@fuse.net
Cc: alsa-devel@lists.sourceforge.net, linux-audio-dev@music.columbia.edu
Subject: Re: Re: [linux-audio-dev] snd-hdsp oddities
Date: Fri, 02 Jul 2004 15:15:46 +0200 [thread overview]
Message-ID: <s5hwu1m8s8t.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040702125607.KKVA3746.smtp1.fuse.net@smtp.fuse.net>
At Fri, 2 Jul 2004 12:56:06 +0000,
<ico@fuse.net> wrote:
>
> > Shouting "DON'T USE 2.6" isn't a good solution. Though, we need to
> > inform to "set LD_ASSUME_KERNEL as a workaround"...
>
> Pardon my ignorance but how does one do this? As a part of the
> config before compiling kernel or?
No, just set the environment variable like
export LD_ASSUME_KERNEL=2.4.19
(better globally) and start jack. That's all.
In this way, glibc chooses LinuxThreads instead of NPTL.
> Also, any ideas on the odd behavior of the hdspmixer? (see my other post)
Not checked yet... Did hdspmixer work on any versions correctly on
your system?
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-02 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 12:56 snd-hdsp oddities ico-rDkNP/OoUoU
2004-07-02 13:15 ` Takashi Iwai [this message]
[not found] ` <s5hwu1m8s8t.wl-UC7Roit8zEholqkO4TVVkw@public.gmane.org>
2004-07-02 13:55 ` [Alsa-devel] " Florian Schmidt
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 0:22 ico-rDkNP/OoUoU
2004-07-02 2:16 ` Paul Davis
2004-07-02 7:32 ` Re: [linux-audio-dev] " Russell King
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=s5hwu1m8s8t.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ico@fuse.net \
--cc=linux-audio-dev@music.columbia.edu \
/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.