All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	Paul Davis <paul@linuxaudiosystems.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Problem with RME 9632 and Plug
Date: Wed, 04 Aug 2004 11:30:56 +0100	[thread overview]
Message-ID: <4110BAE0.6070309@wildgooses.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408041218030.1857@pnote.perex-int.cz>

Jaroslav Kysela wrote:

>On Wed, 4 Aug 2004, Takashi Iwai wrote:
>
>  
>
>>If we have an intermediate buffer, any number of periods must be able
>>to handle (only when the given period size or size/N is supported by
>>hw)...
>>    
>>
>
>The situation is not quite clear for this hardware like for CS46xx etc., 
>because it has already the big ring buffer with max period size - 8192 
>frames. So only another timing source is enough.
>  
>

Ahh, yes, I see now.  The max period size SHOULD be 8192.  For some 
reason when I request anything larger than 2048, I only get 2048...  I 
have tried asking for exactly 8192, and "_near" 8192 with the same results.

I will try giving the machine a reboot in case something has grabbed the 
card and it's ended up in a funny state which might be causing this.  
However, I can currently happily choose 512, 1024, and 2048 period 
sizes, but nothing larger.

Ed W


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

  parent reply	other threads:[~2004-08-04 10:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 13:46 Problem with RME 9632 and Plug Ed Wildgoose
2004-08-03 14:36 ` Paul Davis
2004-08-03 15:44   ` Ed Wildgoose
2004-08-03 16:21     ` Ed Wildgoose
2004-08-03 17:32       ` Paul Davis
2004-08-03 23:55         ` Ed Wildgoose
2004-08-04  0:18           ` Paul Davis
2004-08-04  7:39             ` Jaroslav Kysela
2004-08-04  9:35               ` Ed Wildgoose
2004-08-04 10:20                 ` Jaroslav Kysela
2004-08-04 11:16                   ` Ed Wildgoose
2004-08-04 12:24                     ` Paul Davis
2004-08-04 12:43                       ` Ed Wildgoose
2004-08-04 13:01                         ` Paul Davis
2004-08-04 13:31                           ` Ed Wildgoose
2004-08-04 15:13                             ` Zsolt Barat
2004-08-04 15:03                           ` Zsolt Barat
2004-08-04 15:24                             ` Paul Davis
2004-08-04 13:35                         ` James Courtier-Dutton
2004-08-04  9:44               ` Takashi Iwai
2004-08-04  9:55                 ` Ed Wildgoose
2004-08-04 10:21                   ` Ed Wildgoose
2004-08-04 10:20                 ` Jaroslav Kysela
2004-08-04 10:27                   ` Takashi Iwai
2004-08-04 10:56                     ` Jaroslav Kysela
2004-08-04 11:15                       ` Takashi Iwai
2004-08-04 10:30                   ` Ed Wildgoose [this message]
2004-08-04 10:53                     ` Jaroslav Kysela
2004-08-04 11:21                       ` Ed Wildgoose
2004-08-04  9:52             ` Ed Wildgoose

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=4110BAE0.6070309@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=paul@linuxaudiosystems.com \
    --cc=perex@suse.cz \
    --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 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.