Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "István Váradi" <ivaradi@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA on AMD64 with a 32-bit userspace
Date: Fri, 13 May 2005 16:21:44 +0200	[thread overview]
Message-ID: <s5hfywrrytj.wl@alsa2.suse.de> (raw)
In-Reply-To: <dbdd6db90504220204e2f80ac@mail.gmail.com>

Hi,

thanks for the patches.

At Fri, 22 Apr 2005 11:04:53 +0200,
István Váradi wrote:
> 
> Hi,
> 
> I am using ALSA with a 64-bit AMD64 kernel (2.6.11) but with 32-bit
> applications. While trying to use Rosegarden4 (with JACK and
> Fluidsynth), I encountered some problems:
> 
> - some sequencer-related ioctl's did not work correctly because the
> kernel member of seq_port_info structure was not initialized. I
> attached a patch that initializes this to 0.

Note that the 32bit-compat ioctl framework was majorly rewritten in
the recent kernel, but this is still true for the old code remaining
in alsa-driver tree.

> - start the playback with snd_pcm_hw_start failed with -EPIPE, because
> some pointers were not updated. I attached a patch for alsa-lib 1.0.8,
> in which sync_ptr is called before SNDRV_PCM_IOCTL_START. It seems to
> solve the problem, though I don't know alsa-lib enough to be sure that
> this is the right solution...

Your fix should be OK.  It's harmless for non sync-ptr case, anyway.

Both are applied to CVS now.


> With these patches playback works, but JACK always reports xruns,
> whereas there aren't any. I discovered that the xruns are detected in
> the alsa_driver_wait function in alsa_driver.c (in JACK) returns 0,
> because the snd_pcm_avail_update calls in that function return 0.
> Putting sync_ptr into snd_pcm_avail_update does not seem to solve the
> problem.

Hmm, strange.  Anyway, sync_ptr() is already there in
snd_pcm_hw_avail_update() in the alsa-lib CVS version.  So, it should
be sync'ed before calculation of avail size.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id\x16281&op=click

      reply	other threads:[~2005-05-13 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22  9:04 ALSA on AMD64 with a 32-bit userspace István Váradi
2005-05-13 14:21 ` Takashi Iwai [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=s5hfywrrytj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ivaradi@gmail.com \
    /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