From: Denis Vlasenko <vda.linux@googlemail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andi Kleen <ak@suse.de>, PeiSen Hou <pshou@realtek.com.tw>,
linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: Sound problems with snd_hda on x86_64
Date: Fri, 28 Jul 2006 12:47:11 +0200 [thread overview]
Message-ID: <200607281247.11986.vda.linux@googlemail.com> (raw)
In-Reply-To: <s5hr706nhtr.wl%tiwai@suse.de>
On Friday 28 July 2006 12:29, Takashi Iwai wrote:
> > Which is, in turn, is caused by this code:
> >
> > --- linux-2.6.17.6.org/sound/core/pcm_compat.c 2006-07-15 21:00:43.000000000 +0200
> > +++ linux-2.6.17.6.src/sound/core/pcm_compat.c 2006-07-28 00:35:10.000000000 +0200
> > @@ -478,6 +478,8 @@ static long snd_pcm_ioctl_compat(struct
> > * mmap of PCM status/control records because of the size
> > * incompatibility.
> > */
> > +printk("substream->no_mmap_ctrl = 1 in %s:%s line %d\n", __FILE__, __FUNCTION__, __LINE__);
> > +dump_stack();
> > substream->no_mmap_ctrl = 1;
> >
> > switch (cmd) {
> >
> > It's puzzling. Even a 486 processor, can do 64-bit operations (using cmpxchg8)
> > on memory-mapped areas, why does code disallows mmap for 64-bit CPUs but allows
> > for 32-bit ones?
>
> On the contrary, the driver disallows mmap for 32bit task on 64bit
> architecture. This is because the size of the mapped record is
> different between 32bit and 64bit architectures, so it cannot be
> shared.
Why artsd attempts mmap at all then? Why it thinks that
/dev/snd/pcmC0D0p is mmap-able when it is not?
> BTW, with the recent version of alsa-lib, you no longer need artsd
> unless you want a network transparent. Disable it on kde control
> center.
This is good.
--
vda
next prev parent reply other threads:[~2006-07-28 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 10:16 Sound problems with snd_hda on x86_64 Denis Vlasenko
2006-07-28 10:29 ` Takashi Iwai
2006-07-28 10:47 ` Denis Vlasenko [this message]
2006-07-28 11:33 ` Takashi Iwai
2006-07-28 13:14 ` Denis Vlasenko
2006-07-28 14:09 ` 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=200607281247.11986.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=ak@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pshou@realtek.com.tw \
--cc=tiwai@suse.de \
/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