Skip to contentSkip to conversation

cs46xx: variable period size support, Santa Cruz rear output fixes

PATCH Peter Good 2 participants 2 messages Nov 9, 2002

lore
Share & tools
lore

Peter Good

author
#0 lore raw

So should the drive be able to set period size with this patch?

Reason I ask is this.

spongy@pete:~$ alsaplayer
error on set_period_size (1024)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (181 11610)
PERIOD_SIZE: [8 512]
PERIOD_BYTES: [32 2048]
PERIODS: (0 2048]
BUFFER_TIME: (362 371520)
BUFFER_SIZE: [16 16384]
BUFFER_BYTES: [64 65536]
TICK_TIME: 10000

Pete

Signature · 6 lines
"I am neither especially clever nor especially 
gifted. I am only very, very curious." Einstein.

Peter Good
Pete's Internet Services
GnuPG Public Key: http://www.petesinternet.net/public.gpg
#1 lore raw
Quoted 10 lines

So should the drive be able to set period size with this patch?

Reason I ask is this.

spongy@pete:~$ alsaplayer
error on set_period_size (1024)

Still maximum period size is 512, just as before.
Try start alsaplayer:
alsaplayer -f 2048
alsaplayer -f 1024
alsaplayer -f 512
alsaplayer -f 128
alsaplayer -f 64

And you can try start jackd:
/usr/local/bin/jackd -R -a -d alsa -p 512 -d pcm.cs46xx /usr/local/bin/jackd -R -a -d alsa -p 128 -d pcm.cs46xx /usr/local/bin/jackd -R -a -d alsa -p 64 -d pcm.cs46xx /usr/local/bin/jackd -R -a -d alsa -p 32 -d pcm.cs46xx

Should work OK, however you probably wil have a lot of xruns with low period sizes.
Should be interesting test this with low-latency patch, or preemptive-scheduler.

/Benny

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf